yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] scryan:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)

2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)

3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)

4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)

If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.

On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
[Nexus 6 Q&A, Help & Troubleshooting] 31ken31:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)

It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)

Anyways, got my answer... thx
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.

A restore would have been efficient, but I have found that I really have nothing to back up.. yet.

I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
[Nexus 6 Q&A, Help & Troubleshooting] 31ken31:
Backing up system is what saves your a**
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?

Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:

example:

A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.

I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:

- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.

- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.

Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)

off topic: If one has nothing to backup, what is there to restore?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
its all a matter of choice, period.

flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
Thank you for answering the question.

I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me :)
[Nexus 6 Q&A, Help & Troubleshooting] RLBL:
Update: test passed (I knew it would)

With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.
[One (M8) Q&A, Help & Troubleshooting] arrayy:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.

So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.

When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.

How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.
[One (M8) Q&A, Help & Troubleshooting] risyasin:
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.

Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.

Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.
[One (M8) Q&A, Help & Troubleshooting] arrayy:
Thanks for replying, risyasin.

Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.

Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIMG_M8_QL_UL_M60_SENSE70_HTC_Europe_2.10.401.1_Radio_1.0.U20410.1@60201_20.05_018_F_release_479349_combined_signed

I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.

If anyone can help me figure this out, I'd be forever grateful.
[One (M8) Q&A, Help & Troubleshooting] risyasin:
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.

Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.

I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.

We need to confirm that here. if anyone else tried and brick their phone with that.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] magusberlin:
dear community

my neighbour gave me his Z1 compact because it did not work anymore.

It was stuck on loginscreen, when i touched the unlock button it vibrated, but nothing else happened.

I could however download all his photos on my Win7PC by just plugging it on USB

but it kept staying unresponsive, no way to get beyond lockscreen

So I used SonyMobileFlasher and unlocked the bootloader without any issues - no errors.

Then I flashed a new firmware obtained through XperiFirm without errors

Now, when I boot, I can hear the boot-melody (??)

but the screen stays dark.

I can connect the phone via flash mode and fastboot mode

I can switch it off by pressing volUp+Power (three vibrates)

from Off i press power, it plays the melody, but the screen stays dark

Is it a hardware damage?

Is there anything I can do for the phone?

thx for ur input
[Xperia Z1 Compact Q&A, Help & Troubleshooting] levone1:
Seems like busted display to me. Flash recovery and see if touch screen works in recovery. If not, definitely hw.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] magusberlin:
thx for ur reply, i flashed TWRP- several trys, now I can see the TWRP lock screen, but when I swipe to log in it vibrates, soon after the screen scrambles away, vertical lines just fade and then crash-off.

seems very much like the screen is defect? not worth replacing, seems like a whole huzzle to replace that screen

pitty, one more device to trash.

i am seriously looking into fairphone2, would be nice to replace the screen so easy.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] levone1:
Maybe not extremely easy, but there are guides in the forum here for screen replacement, if your feel up to it.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
I am not sure how long this has been going on but my WiFi does not find ANY networks. It just keeps scanning. I have tried not only a reboot but cleared Cache and Dalvik with no help.

If it helps, I am running Pure Nexus, I have some mods like Xposed installed and I am running ElementalX kernel.

I have not made any changes to my phone ins weeks and this problem has to be within the last day or 2.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
sounds like you are using an older kernel. you need tyo use one that was put out after the last june security update, as the developer has stated this when he released the last pure nexus update, that wifi will be broken unless..
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
Come to think of it, I did update my kernel yesterday morning.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
when was that kernel made? i updated as well, but to a kernel from february, but im on an older pure android build. anyways, the developer posted that if you update the rom, to use a kernel built after the last security update or wifi will be broken.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
It was a auto update from ElementalX.

I'm not sure of the version, I have it set to delete it after update.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
its from july 8th, it should be good, if Flar used the latest source that is..
[Nexus 6 Q&A, Help & Troubleshooting] droid fetish:
Pleases read elemental X.-Before you flash anything, even if it is something that you have been using for a while, READ THE CHANGELOG! A few minutes of reading can save hours of headaches! I say this not because I am smarter, but because I to learned the hard way. Good luck.
[Nexus 6 Q&A, Help & Troubleshooting] tjlmbklr:
Will read the change logs from now on. Thanks. I am always so quick to update when it's available, I guess I need to pay more attention.

With that said, I dirty flashed my Pure Nexus ROM and all is good now. Unfortunately I haven't updated to the latest Pure Nexus (2 since the one I am on now) because they no longer support CMTE builds and I run a lot of Cyanogenmod themes.
[Nexus 6 Q&A, Help & Troubleshooting] droid fetish:
I am also on Pure Nexus with The elemental X Kernel, make a back up then flash the latest Pure Nexus and give "layers" a try . IMHO you should always be running the latest security patch there's just too much at stake with all our personal information these days, if you make a back up you can always go back if you do not like what you find. Have fun keep flashing!
[Samsung Galaxy S7 Edge Questions and Answers] teoboy:
I wanted to use CF AUTO ROOT and I cant find G935FD only the G935F. I dont know if i can use that. Can anybody please confirm this?
[Samsung Galaxy S7 Edge Questions and Answers] chihchun:
I verified SM-G935F (NRD90M.G935FXXU1DQD3, 7.0, 62a903c04886dfa3d26e04e07f3e72a3) woks on SM-G935FD.
[Samsung Galaxy S7 Edge Questions and Answers] asadnow2k:
will it trip the knox or knox safe it is?
[Samsung Galaxy S7 Edge Questions and Answers] mashardpro:
Root will trigger knox
[Samsung Galaxy S7 Edge Questions and Answers] Mr.Ash.Man:
basically the same phone just the FD has an extra sim slot

thats all

you can flash anything F related on FD, even the stock firmware
[Samsung Galaxy S7 Edge Questions and Answers] mizuki2o17:
the following steps i do to root my SM-G935F and i don't will miss it.

the first method (TWRP with supersu-zip file and dm-verity disabler install was failed, bootloop)

The second try with CF-Autoroot have rooted it.

Bevore rooting with CF auto-root it's needed that you activate the developer options with oem-unlock and usb-debugging.

Than you make a factory reset about the android-own system recovery (home, vol+ and power)

at next you must change in the download mode without boot the "fresh" system and then flash the CF-Autoroot with odin.

Than you can start the fresh system without any first changes bevore rooting process have starts. The securityLogAgent warns you about unauthorized changes. you can disable this notice. And you must disable samsung knox too because it can behinds supersu. a example s-health will not work with rooted devices. one file edited and it works again.

see here. https://xdaforums.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306

In the system app menu you can only stop it. Than you go fast to supersu, this app disable it.
[HTC Excalibur] lukybandit:
Hello,

The reason why anyone would do this is for example - I installed the Rogers WM6 but preferred the HTC BOOTSCREEN Image - hence why i personally did it. I did not like Rogers BootScreen Images as they take too long to boot as well as the bootscreen image in the Rogers WM6 used to load after the Green Windows Mobile Screen and on power-up, it used to have a black screen instead of the bootscreen image which to me did not seem practical as I rather see that the phones turned on right away than wait till the Windows Mobile screen loads. I've successfully flashed HTC Bootscreen image using the following steps. I had a member ask me how to flash .nbh files to phone. I'm talking specifically about the bootscreen .nbh images. In order to flash .nbh boot screen images - you have to flash through USPL. Here's how to do it -

1) Firstly, Download all required files that is

a) USPL CID -BYPASS

b) RUU

c) SDA APPLICATION UNLOCK

d) BOOTSCREEN IMAGES(IT CONTAINS HTC, ROGERS AND TMO BOOTSCREEN IMAGES)

2) Copy/Paste RUU File that is ExcaIMG_USPL_1110000unsigned.nbh to the desktop.

3) Copy/Paste ANY of the preferred BOOTSCREEN IMAGE (i.e. for example HTC.nbh) to RUU directory

4) Right Click ExcaIMG_USPL_1110000unsigned.nbh and Select Rename - Press Ctrl + C to copy file name

5) Head over to RUU and Right-Click HTC.nbh, Select Rename - Press Ctrl + V to copy over existing file name.

6) Once you're done this, REMOVE SD CARD AND REBOOT PHONE

7) Once done, APPLICATION UNLOCK YOUR PHONE IF IT HASN'T ALREADY BEEN APPLICATION UNLOCKED - YOU HAVE TO RUN SDA APPLICATION UNLOCK.

8) Now, Run USPL, Make sure you follow proper instructions as this is the main thing - if everything done right, you'll see screen goes into dim black with penguin and green messages, wait until you see the screen turns white then go to active sync and disable usb connections.

9) After this, run RUU and it'll use the re-named file which is the boot screen image to update the boot screen image. It will take max. a minute or two.

10) Once done, I think you see the tri-color screen but there won't be a cold boot - It'll reboot i think and go directly to the main screen.

11) Reboot and see if you see the preferred boot screen image.

For now, I'll post HTC, TMO and Rogers Boot Screen Images. We should still try as a group to create Custom Boot Screen .nbh files. If someone who know's how to make it, please share in this discussion.

Also, Does anyone know how to bring back the "Vibrate" mode during startup and shutdown?

Good Luck ! Post any concerns or any questions :)

NOTE: Please follow proper instructions, otherwise it won't work. If i'm missing anything, please let me know as I did this flash yesterday and I'm writing the guide today. Also, YOU HAVE TO FLASH THROUGH USPL - IT DOESN'T MATTER IF YOUR PHONES CID UNLOCKED OR NOT.

Credits go to da_mayhem for uploading the images.
[HTC Excalibur] travisc:
sweet, thanks... I'll try this later tonight after i get home from work... or tomorrow :)
[HTC Excalibur] travisc:
woohoo, sweet... thanks for the guide lukybandit. :)

On step #2, you'll want to "Cut/Paste" if you copy, it leaves the original file in the folder, so renaming the HTC.nbh isn't possible unless you delete the original file.

also, step #8... DEFINATELY make sure you disable USB connections, i tried without and it didn't work...

However you're supposed to do that for WM6 rom updates also, but i never have, and haven't had a problem... until now that is. :)
[HTC Excalibur] StefanSki:
Change HTC Splash Screen

Hello,

How to change the HTC splach screen which appears just after powering on the device?

I tried a lot of tools but I did'nt found one which works. Is it because the Excalibur screen is 320x240 instead of 240x320?

Does someone knows how to do?

StefanSki
[HTC Excalibur] kavana:
replace Shutdown.png in windows folder,with 320x240 :)
[HTC Excalibur] blahzay_blah:
i tried this i created a .png file but when i try to place it there access denied lol it wont let me touch anything in the windows folder
[HTC Excalibur] StefanSki:
This is not this splash screen I mean.

I am talking about the first one, which is in the NBH file as a NB file. I don't manage to make a good NB file in the right format to flash it using RUU.
[HTC Excalibur] blahzay_blah:
nbh file wat folder wuld that b in because i jus changed my shutdown screen and i want my turn on screen to b da same as that one
[HTC Excalibur] lllboredlll:
you need total commander to overwrite
[HTC Excalibur] StefanSki:
No one knows how to make a NB file that contains the splash screen? The default HTC NB file begins with "this is smartphone signature".
[HTC Excalibur] blahzay_blah:
i changed my shutdown screed with resci explorer but to change the start up screen the htc screen and the freen windows mobile screen i want to get rid of those ugly screens
[HTC Excalibur] blahzay_blah:
any1? a little help lol just want to change the start up splash screen any1 know how
[HTC Excalibur] pof:
You can use nbimg, to convert from NB to BMP.

For excalibur you'll need to use the following syntax:

nbimg.exe -F MainSplash.[nb|.bmp] -w 320 -h 240 -n

Also you'll need to add the "this is smartphone signature" manually to the generated NB file (using an hex editor). Maybe I'll add support for doing this automatically if there's a need. PM me as I'm not following the thread.