yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
Good advice...I'm a bit old school and normally advise using the Run command...I forget Windows after 7 implemented that way of doing it...

And then sometimes in certain cases using the Run command doesn't give the option to run as administrator...

But I've not found many cases (if any) that things went badly because it wasn't an elevated command prompt, but I just think it's good practice just to eliminate a possible hitch right off the bat before working on numerous solutions only to find out it was something like that...

And it's always surprising how many novice users are able to achieve advance goals without knowing the basics -- for better or worse, it probably just compels and instills confidence to be messing with their phones/devices more...
[Google Pixel 7 Pro] EtherealRemnant:
I used to work tech support so I got in the habit of finding the absolute easiest way to tell people to do things. Windows key shortcuts are a godsend for tech calls. They're obscure enough that if you get a techie on the line who would normally be offended by you holding their hand through things they might actually thank you for learning something new but easy enough that someone who can barely turn on a computer can key peck their way through it lol.

I also specifically like using this shortcut because it's so easy to run in admin mode. It's how I personally launch basically everything on my computer that I haven't pinned to the taskbar.
[Google Pixel 7 Pro] Lughnasadh:
Yeah, I've never had to use elevated command prompt when flashing.

I just put whatever I'm flashing in the Platform Tools folder, type "cmd" in the address bar of the Platform Tools folder to open command prompt from that folder and away I go.
[Google Pixel 7 Pro] NippleSauce:
You can also just copy and paste the path - which is presumably what OP was doing.
[Google Pixel 7 Pro] Curiousn00b:
That too. I'm so use to installing ADB/fastboot into my system's path that I forgot if you have it in one location, you need to do paths.

I be having one open in my downloads, the desktop, and a folder where I keep stuff when I mess with my phone's, lol. 😂
[Google Pixel 7 Pro] Linxy420:
i wrote this post because when i did not specify a partition it failed. its literally in my post that the normal way to do it failed for me. I used cmd to not powereshell.
[Google Pixel 7 Pro] Linxy420:
i used cmd and not specifying a partition made it fail.
[Google Pixel 7 Pro] Linxy420:
What are you talking bout? I did exactly that and it FAILED for me unless i specified a partition. The only thing i did a lil funky is i didnt open cmd in the folder the patched image was in so i had to drag and drop file to add path.
[Google Pixel 7 Pro] Linxy420:
novice? yes. and this post is for other novices who want full control of their phones. im a specialized mechanic that rebuilds transmissions for a living, not a techie but i love to dabble. i dont put others down because they cant install an overdrive sprag or a rear case bearing with race, or intermediate and overdrive servos cause im not fffing 12 years old. and please explain what im doing wrong then cause everything you guys say is basic i did. I installed adb and fastboot drivers i patched the init image, opened admin cmd and tryed to flash and it didnt work until i specified a partition. the only thing i did a lil diff is i didnt open cmd in the folder the patched img was in i had to drag and drop,,, its jus sad how ppl can type like there some tough sh*t but if this was face to face youd have nothing to say, in prison we called you guys window warriors lol.
[Google Pixel 7 Pro] simplepinoi177:
whoa whoa whoa... someone's pretty touchy...

how was I putting others down? I said I found it surprising that some "novice" users skip some steps to achieve more advanced stuff without understanding basics and can get themselves into trouble and/or not be able to properly backtrack because they skipped through the basics -- it was simply based off of a ironic situation of how if someone couldn't even run an elevated cmd yet they are trying to mod their device. Never did I say you, or anyone specifically, were these novice users. It was a general comment on that type of situation.

How am I typing "like they're some tough sh*t"? And I find it hypocritical that you make assumptions about me "talking down" and generalizing you as a novice, when you make assumptions of me that I just "type like they're some tough sh*t" but face to face I'd have nothing to say and generalizing me as "window warriors". Interesting that you're so insulted, yet sling the same type of remarks...

and in an attempt to posit an idea that might've been wrong, I did mention that, in many cases I found, a lot of people were required to do what you did because they were using powershell instead of cmd and powershell is iffy in its execution, so it might've been that...

I know in the end you clarified that you use an elevated cmd, not powershell, and still had to specify what slot to apply it to. Sometimes it just goes that way, I guess. None of us are Google software engineers, so we can only guess and probably can't give you a complete straight answer. Most of us don't need to specify the slot; applying it to the active slot usually is enough.

So, I hope you consider all this and re-evaluate some things....
[Google Pixel 7 Pro] EtherealRemnant:
If you go back and re-read what I wrote, I wasn't talking about you, just giving @simplepinoi177 an easy way to tell people how to run command prompt and other things in administrator mode...
[Google Pixel 7 Pro] s3axel:
Strange, I've never had to specify the partition....

Two thoughts: first make sure you use the latest platform tools as available from Google and second it may be an idea to use --slot=all as parameter for flashing, this way you can make sure all slots are flashed......
[Google Pixel 7 Pro] Linxy420:
I posted of what i had to do to get my pixel to gain root access. your answer made it sound like only advanced users should ever have root access to their phones and a "novice" shouldn't even try, you might not have meant it but you made it sound like that and yea it ticked me off a lil but i do apologize, I might have taken it a lil far rereading my post. I try to help when I can even with my meager tech savvy and if i can help a couple people having the same issue as me im quite happy. and im sry but saying being a novice and getting it done jus instills confidence for them to mess up later is a put down, i dont know bout others but i do know my limits i toyed with many phones in my past and even bricked a couple and through a bunch of trial and error got em unbricked.
[Google Pixel 7 Pro] simplepinoi177:
I was going to leave this all well enough alone, but I wanted to give some clarification and leave a word of warning/caution for any novice users (*not anyone in particular*) that just might be perusing this, and since this is a thread about "root issues" I hope its considered still be on topic -- although being an I.T. tech I have numerous other examples, the particular situation that came to mind in my original quoted remark is on novice users who nonchalantly attempt to manually relock their bootloader on Pixels (I'm sure experts here who have assisted others in the subject are already groaning and can sense where I'm going with this...). It's pretty much always the case where there are seemingly countless users who have found themselves in this situation where they skipped through past the basics (merely unticking the OEM unlock button, unlocking the bootloader), modified partitions (whether just to root or to apply custom ROM), and because they achieved this they had become overconfident without understanding how running the unlock bootloader command is severely a lot less riskier than the locking bootloader command (without proper preparations and considerations), how to flash a Full Factory image, or why it's important to keep (or even just have remain) the OEM unlock button unticked until the end; and ultimately, hard-brick their device where no amount of trial and error will get it unbricked in the end.

As in this case, speaking on novice users who were successfully able to go straight to modifying partitions and/or applying a custom ROM (advanced goals) and had become overconfident that they didn't properly research the basics (flashing Full Factory images) or heed warnings of re-locking bootloaders and ended up hard-bricking their devices -- basically "being a novice and getting it done jus instills confidence for them to mess up later" -- is not, and was not meant to be, a "put down", but merely stating what happens from time to time. And, I did state that it is "for better or worse" that it "compels and instills confidence to be messing with their phones/devices more" -- "better" if it leads to careful experience, "worse" if it leads to overconfidence and brazen irreparable but

avoidable

damage. But, I'm sure, that all experienced users, both experts and not, had been led to their success due to them messing with their devices, so it's not to say one shouldn't do it and me trying to gatekeep, it's more me saying; sometimes you have to crawl before you walk before you run, it always surprises me when some people run after just learning to crawl (let alone walk), and people who do that should brace themselves for faceplanting -- but it should not be considered putting them down saying this.

In the end, don't skip the basics, thoroughly research, it is not a put down when speaking on those who do not do these things but attempt advanced scenarios anyways, and do not relock the bootloader on Pixels (unless very particular, exceptional circumstances).
[LG V20 Questions & Answers] f2ranco:
:(I'm currently using stock rom. I'm playing only one game: Mobile legends. Can you recommend a rom where I can get the best performance?
[LG V20 Questions & Answers] the_arxyn:
You can use an overclocked kernel for performance
[LG V20 Questions & Answers] xxseva44:
Arrow, however that does not have functioning cellular atm.
[LG V20 Questions & Answers] xxseva44:
Why waste power and generate extra heat? We already have 4.4 which outperforms all the 3.18 kernels:)
[Touch GSM General] koolsurdie:
Hello,

I have an unusual problem. I'm using elf with following confirguration

Touch version : Elf

Device ID : ELF010000

CID : DOPOD001

IPL : 1.11.0002

SPL : 1.11.0000

ROM Version : 2.20.710.2

ExtROM Version : Blue Elves v5.0

Operator Version: None

AKU Version : 1.1.0

Page Pool : 8 MB

RAM Size : 64 MB

ROM Size : 128 MB

In addition to this I'm using S2U2 utility with fullscreen caller picture indicator, battery status plugin as well

When my phone battery is 50%, the phone reboots on its own. Then at about 30% it reboots again.

I've also started noticing battery drain while I don't use the phone too much except for making some calls and using a bit of Wifi.

Please advise.
[Touch GSM General] ahmedsalembadr:
the same thing with my elf.

my elf restart with incoming call if the battery less than 50% :o
[Touch GSM General] strobs:
Same to me

Happens the same to me. i bought a new battery. Flashed with 10 different roms. Put the original Rom and activated warranty.
[Samsung Galaxy S21 Questions] romanspqr:
Hi everyone, i'm new here

I've just rooted my s21 sm-g991b/ds

But i cannot enter the engineer mode i really go krazy

Cannot find a way to get in there

O forgot i literally don't know anything about theese thing i'm a pro noob

First time ever !

Thank you to everyone that will help me
[Samsung Galaxy S21 Questions] JonasHS:
Use adb to open i the package.
[Samsung Galaxy S21 Questions] romanspqr:
Sorry but i dont know how

Open adb with prompt? And then give order to open?
[Xiaomi 11T Pro] mimi2277:
Hello, i just woke up and noticed that the bottom speaker in my phone doesn't work. Yesterday everything was fine. Phone has not been dropped or spilled, stayed on the desk all night. I try "restart" and "clean speaker" option but only the top one works. what could have happened?
[Xiaomi 11T Pro] mimi2277:
The speaker was damaged. The phone was returned under warranty. They replaced the motherboard (don't know why). Now works fine.

Topic for close.
[Xiaomi 11T Pro] Aramantir:
Hello everyone, im flashing my bricked 11T pro.

Im using latest QPST with QFIL, I have installed correct drivers for pc and my phone enters edl mode.

However when I try to flash Im getting this error

View attachment 5794699

File super.img is in bin folder of qfil , View attachment 5794701

I also tried launching program with administrator rights.

I get another error -_-

Right now I will be trying to do the same on different PC.
[Xiaomi 11T Pro] Renate:
Sahara is a brittle protocol. If anything goes wrong or you disconnect the cable you have to start all over with a reset and go to EDL mode.

Edit: Oh, and it looks like your super.img is a corrupt sparse file (or too advanced for this tool?)
[Xiaomi 11T Pro] JonasHS:
Try to flash partition one at a time with cmd fhloader, you can see the commands or fhloader --help in cmd
[Xiaomi 11T Pro] Aramantir:
I download rom from official xiaomi site , it was in zip archive. I downloaded it again on different laptop with different system and getting the same problem.

Thing is phone is hardly bricked, my friend wanted to flash it to EliteRom but he flashed different model over my xiaomi so boot logo changed to redmi etc, I cant enter fastboot or recovery only EDL mode. I use stock cable
[Xiaomi 11T Pro] Aramantir:
I dont know how to use commands in EDL mode, as I know its only possible to flash roms in EDL
[Xiaomi 11T Pro] Renate:
You can see other folks on xda who ran into cac2 as sparse chunk.

I've not had a lot to do with sparse files.

I'd try to inflate the sparse file to non-sparse on your desktop and then you can do a normal write using whatever EDL tool you like.
[Xiaomi 11T Pro] Aramantir:
Ok, where can I find instruction about inflating sparse file to non-sparse ones?
[Xiaomi 11T Pro] Renate:
This should work in Linux land:

cp file.img copy.img --sparse=never
[Xiaomi 11T Pro] Aramantir:
so i need to install linux on virtual machine and do this command on super.img?
[Xiaomi 11T Pro] Renate:
Dunno. Maybe try:

C:\>fsutil sparse setFlag super.img 0
[Xiaomi 11T Pro] Aramantir:
View attachment 5794769I dont know what Im doing wrong, I tried cmd and powershell
[Xiaomi 11T Pro] Aramantir:
QFIL also makes a cmd but it gets stuck on this View attachment 5794771
[Xiaomi 11T Pro] Renate:
Microsoft Windows [Version 10.0.19045.2364]
(c) Microsoft Corporation. All rights reserved.

C:\>fsutil sparse
---- SPARSE Commands Supported ----

queryFlag Query sparse
queryRange Query range
setFlag Set sparse
setRange Set sparse range
[Xiaomi 11T Pro] Aramantir:
Ok I put all files to C and run command View attachment 5794781

I guess its best to run it in different folder
[Xiaomi 11T Pro] Renate:
Are you as Admin?

The file could be in use too.
[Xiaomi 11T Pro] Aramantir:
View attachment 5794791

Ok so its done, now I can flash?
[Xiaomi 11T Pro] Aramantir:
View attachment 5794803

Same error...That sparse thing didn`t worked at all :C
[Xiaomi 11T Pro] Aramantir:
View attachment 5794811

Right now trying different software. I also had 2 programmers in folder of fastboot rom. I choose different one. In some time it failed to connect

View attachment 5794815
[Xiaomi 11T Pro] Renate:
I have no experience on the sparse file, so I can't say.

Does dir look any different after the fsutil commands?

Does the File Explorer show you anything different?

Those QFIL utilities are designed to fresh flash something coming off the factory floor.

Most people have not trashed every byte of their device and need to flash everything.

This "rawprogram0.xml" is also a bit overblown. Most of it could just be done with a batch/script file.

And the serial port drivers are straight from hell.

In any case, that's my opinion.

You can try EDL clients that don't need COM port drivers.

https://github.com/bkerler/edl

http://www.temblast.com/edl.htm

The last is mine. I like it. You don't have to. It doesn't do sparse files (yet).

What exactly do you have to flash and how did it get wrecked?

Even without super you should be able to get back to fastboot and have that deal with sparse files.
[Xiaomi 11T Pro] Aramantir:
So as I said before it got flashed different model of phone.

Like my phone model is Mi11T pro, but someone flashed REDMI K40 ROM ... (because they had super similar name)

So all boot/recovery partitions got overwritten and its impossible for me to enter fastboot and flash stock rom.

Thing I got from Xiaomi site is flashboot rom which contains all that data I need to flash , but having 2 programmer file and a lot of xml files kinda scares me, tomorrow I will be learning how to use your program :)

From using command you gave before - I didnt saw any changes. There was 86 files in folder and there is 86 files in folder after using it, maybe I did something wrong? About script, xiaomi gives ready scripts for flashing but I guess they are for fastboot flashingView attachment 5794951 View attachment 5794955

There is also premade python script but I have no idea how to use it

View attachment 5794957
[Xiaomi 11T Pro] Renate:
Ok, but fastboot (in abl) shouldn't take that much to get it working. It definitely needs xbl, abl, probably rpm, who knows what else, but definitely not super.

The other thing that is so stupid about rawprogram0.xml:

It says, "write misc.img to block 123456, 7890 blocks."

That's so stupid. Write your GPT, write your GPT backup (that doesn't need any of the stupid math in an XML).

Now, where do you write misc.img? To the misc partition, end of discussion.

Yeah, but how much? As much as in misc.img, end of discussion.
[Xiaomi 11T Pro] Aramantir:
Yeah this doesn`t looks clever... Im also confused about that in Android u need to enter all these EDL modes and reflash everything , in PC u just boot from usb and install everything with 0% problems but here I had and have lots of troubles with installation/drivers/connection and entering these modes... I really hope your program will help , I will try tomorrow because too tired ..
[Xiaomi 11T Pro] Renate:
Ok, my bad. A clarification.

Sparse files are implemented on OS filesystems. It's a storage technique.

In Windows (or any OS) I can say, "Give me a 10 Meg file", then write my shopping list in the middle somewhere.

The structure in this case is internal to Windows.

If I copy that file I get 10 Megs of mostly zeroes with "zucchini" in the middle.

Android "sparse files" are not this.

They are undocumented suitcases of stuff that is not OS specific.

It was created for fastboot.

https://android.googlesource.com/platform/system/core/+/master/libsparse/

Your utility must be ancient/incompetent if it doesn't understand 0xcac2 (CHUNK_TYPE_FILL).

How big is your super.img sparse file?
[Xiaomi 11T Pro] Aramantir:
super.img is 8gb

I just tried to flash abl to recover fastboot but couldn`t open device. Is it because I have Qualcomn driver`s installed? I need to delete them? If I do so - my device will be called "Unknown device" .

Rn I have windows drivers installed
[Xiaomi 11T Pro] Aramantir:
here what it says if i will try to open it basically
[Xiaomi 11T Pro] Renate:
Sheesh, I'm not going to download 8 GB just to check it out.

Are you sure that it hasn't been expanded already somehow? 8 GB is kind of big.

Can you see the first 4 bytes? What are they?

You need to install Zadig drivers (generic WinUSB) as it shows on the web page.

If you get bored you can always reload the Qualcomm virtual com port ones. (Barf!)
[Xiaomi 11T Pro] Aramantir:
Thats how super.img looks in 7-zip

About installing drivers,

Did I select it right? I dont want my other devices to break,
[Xiaomi 11T Pro] Renate:
Yes, that's the right device: 05c6/9008 is standard EDL.

I am confused by your super.img, it has filenames in it. It can't be a "sparse image".

The rescue.img you showed me looks more like a Android "sparse image".
[Xiaomi 11T Pro] Aramantir:
Yes super.img is quite weird.. yesterday I asked Xiaomi support about this, they asked about my IMEI number and started talks about garranty and then dialogue went weird and I didnt get any information except "XIaomi doesnt recommends flashing to their customers"

Thing I will try now is to

Install drivers

Do everything to recover fastboot

Then boot to twrp using fastboot boot

Then flash stock rom, I hope this will work
[Xiaomi 11T Pro] Aramantir:
I have driver issues now..

I hate my antivirus... all i can do now is just to wait. I ALREADY DISABLED AVAST PERMANENTLY 1 hour ago .. I dont know why they are so sneaky
[Xiaomi 11T Pro] Aramantir:
Also I just decided to try MiFlash, since Xiaomi likes to do their own weird files and all other stuff, it says this. I guess there is a different problem which I will be looking now
[Xiaomi 11T Pro] Renate:
The background behind "Driver installation failed" is all 100% correct.

I've never seen that fail. It might take 2 minutes.

Oh! Did you have anything running that might be using that Com port?

Do a clean restart and try the install again.
[Xiaomi 11T Pro] Aramantir:
For now I decided to wait from Xiaomi support`s respond, I asked about why do I need to pay money to some weird guys just to get autorized account. Maybe they specially made their super.img weird just so only their service can repair their phones. Because only MiFlash is working normally with my phone, other programs show weird errors
[Xiaomi 11T Pro] Renate:
Aw you should try to get *normal* device drivers working.

You can play around and download backups.

Edit: Oh, and I put up a new edl.exe

It's more responsive in giving feedback when you're doing erasing.
[Xiaomi 11T Pro] Aramantir:
I will try your edl.exe when I will get respond from Xiaomi Support, thx for help
[Xiaomi 11T Pro] Aramantir:
I guess since they recomend me official service, I should go to it and just give them my phone.. Capital is in 2 hours away from me, im sure they have this autorized miFlash account
[XPERIA X1 General] sum-xda:
Hope someone can help....

In Settings -> Sounds and Notifications, I have set the sound for Screen taps to loud and the volume of ringing tone is set to full and on....

After couple of hours, I lost any sound while tapping the screen and can't hear if some one rings me....

It happened yesterday, all worked when I rebooted the mobile.

Today it happened again, but when I rebooted the mobile, the sound came back and now after few hours it is same situation....

I even check the Setting -> Sounds and Notificatons -> Notifications -> Ring type -> Ring

Does anybody know why it is happening..
[XPERIA X1 General] olympuso:
Ringer problem

I have the same problem too, when I set to ring and vibrate the ringer cuts off. I have now disabled the vibration function but the ringer volume still fluctuates between high and low, or even disappears completely. Any ideas? Apart from this (major) issue, I love the phone...
[XPERIA X1 General] anothal3v3l:
Just came abouit tis same issue. My ringer seems to fuctuate from low to high and high to low
[XPERIA X1 General] ddevilx:
I've had the complete loss of sound once, reboot helped.
[XPERIA X1 General] alalala:
i'm having the same issue!

after going in standby, the phone wakes up but does not ring or play sound anymore (even if you receive a call or a text message).

if you answer to a call, you cannot hear anything in the earpiece and also the microphone doesn't work.

if you soft or hard reset the device, it will work again at the beginning, but the issue will be back in a few minutes.

i verified that if you launch windows media player (or other app that plays audio) when the device has become "silent", will initially result in no sound, then - after few seconds - will make the phone restart (just the phone component, not the xperia) and the sound starts working again.

some times i got also a gwes error, which has made the xperia unresponsive to the touch screen.

btw, i'm very displeased since this device is brand new and was given me by the repair center to replace my xperia (I left it charging battery all night and on the morning was dead...)

I think I'll take it back to the repair center and ask for another replacement...