yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Questions & Answers] molletit:
hehe, iam going to get it exchanged in an T-Mobile Store today, also have an extra insurance for stupidness if they wont do it ;)

But its legit, the Phone is done, its the first time i bricked something ... i see it as an archivement :)

ill doing tech "things" like 25 years now, ive modded Playstations, Mobilephones, TVs, everything, so the Pixel is the first device that i could not repair by my own... so its ok.

Thanks all for the Reply.

It would be nice if someone could explain what should be done before switching to the second slot (b), because i was thinking of having one Slot as a rooted one (A) and one Slot normal, unrooted (B).

in Q/A, maybe it is helpful to advice people not to switch Slots in TWRP if they arent sure what they are doing and theyre sure the flashed a bootloader on it..
[Google Pixel XL Questions & Answers] bahehs:
This happend to me. I switched over to slot b, thinking it would give me accsess to the same rom with diffrent data partition. Ended up bricking the device. When I connect it it says Qualcomm HS-USB Diagnostics 900E (COM3). Moral of story don't switch slots on pixel or you will brick unless you know what you are doing.
[Google Pixel XL Questions & Answers] jjayzx:
You brick it and want warranty to cover?
[Google Pixel XL Questions & Answers] superchilpil:
In his defense anyone here could make that mistake. Honestly that's a pretty big oversight on Google's part, why wouldn't they program a fail-safe that would realize that there's no bootloader and switch to the previous boot slot.
[Google Pixel XL Questions & Answers] toknitup420:
Well not for nothing. You mess with unlocking and playing with something you don't know about is not Google's fault. Having said that. Google can afford it. And they don't care. You don't think they find out who bricked their device when you send them in. They just fix them and resell. They could care less.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
I could have sworn lots of people did this and there was a fix??
[Google Pixel XL Questions & Answers] Yamalito:
So do we flash a bootloader image to slot a and slot b to prevent this?
[Google Pixel XL Questions & Answers] blueyes:
I don't think it was an oversight on Google. They play pretty nice with open sourcing and providing developers support. Links to OTAs, factory images, and the devices full source code. We take risks and do things that Google is certainly aware of, although they may not condone it. They provide the info we need to modify it but can't be expected to predict or bail us out when things go south. Switching from A to B and vice versa is designed to make the OTAs a more efficient transition. Taking an OTA will switch and have all necessary partitions. As Android progresses we need to know what we are doing, look at it well beforehand.

Just playing devil's advocate, hopefully we will all learn from these instances.
[Google Pixel XL Questions & Answers] khaytsus:
I'm 99% sure there IS a bootloader on both A and B. I suspect the problem is different. What it is I obviously do not know but if you've taken ANY OTAs, you would have used A and B. Or if someone is willing to risk it, flash a bootloader to both and switch.

Some people are blaming twrp here, but unless the recovery has some responsibility in booting the bootloader (it would not) I doubt it has anything to do with it.
[Google Pixel XL Questions & Answers] milan187:
I wonder if people somehow wiped boot then switched partition and tried to boot. Though you would think bootloader would still be there.
[Google Pixel XL Questions & Answers] Healite:
So rather than make another thread I'll just post here. Long story short I have deleted my OS. I'm still in TWRP RC1 and it's notifying me that I have no OS when I try and reboot, reboot to bootloader, etc. Any advice on what I should do so that I don't have a very nice looking paperweight? ADB recognizes sideload and recovery.
[Google Pixel XL Questions & Answers] blueyes:
Run fastboot getvar all and it'll show you what each slot contains. You can change the slots with fastboot, probably your best bet if you really wish to switch them.
[Google Pixel XL Questions & Answers] toknitup420:
This doesn't belong in this thread but,. Just flash a factory image and you're phone will be fine again.

And I'm not trying to be mean about this. But you're problem is very basic and easy to recover. You should take the time to learn how to fix a soft brick before you start playing with you're very expensive phone.
[Google Pixel XL Questions & Answers] hutzdani:
if an OTA screws a bootloader the system will switch back to the previous state when it can't reboot and try from another slot so logic would think that when a bootloader is written to one it also ends up on the other untill you get an update and it gets over written.

I can't believe for one second that the guys device had nothing on the other bootloader slot unless he manually typed in the commands to wipe them, this sounds like something else has caused this and frankly I'd think this is TWRP related TWRP is still in testing RC1/Alpha and something funky could have happened and TWRP is stopping some built in protection happening.

You can flash one kernel both slots and switch between them freely untill your fingers become bloody stumps but I'm pretty sure where your bootloader/kernel is different this would screw your device up because of the boot table.
[Google Pixel XL Questions & Answers] aholeinthewor1d:
I was doing a lot of research and talking with people in another thread and jcase also chimed in. From everything I read there is only one bootloader which is shared by both slots. The bootloader is the very first thing to load and tells the phone which slot to boot. So there is no way you erased the bootloader from anywhere. Also for the people saying Google should have a fail-safe.. they do. According to all the detailed articles I've read it's designed so that if it can't boot one slot because of issues with the boot img (not bootloader) it will reboot a few times eventually booting to the other slot.

So seeing as how there is only one bootloader myself and a few others in another thread were trying to figure out what people did internally that caused this brick where nothing resolves it. I've seen some people mention they were able to fix by using "fastboot continue" but others had no luck. Surprised with all these people that bricked there is no definite explanation on what really caused it.
[Google Pixel XL Questions & Answers] droidan:
Yes that is true.

We need emmc_firehose_8996.elf, rawprogram0.xml. Patch0.xml and maybe msm8996.mbn?
[Google Pixel XL Questions & Answers] wingman021280:
I need these files too please for a 128gb Pixel.
[T-Mobile LG G5 Questions & Answers] roosxter:
I have a h830 and used autoprimes 20a flashable and it worked. But I was having some issues with apps force closing. So without researching like an idiot I tried to flash the 10d root tot. Now it goes directly to the firmware update screen and I tried every kdz I could find. Am I screwed ? Please help
[T-Mobile LG G5 Questions & Answers] autoprime:
LGUP 1.14 + UPPERCUT 1.0.0.0 + H830 20A KDZ should get you out of download mode/fw update.

Then boot into recovery and wipe data. you should end up with a fresh/working 20A.
[T-Mobile LG G5 Questions & Answers] roosxter:
Thanks that worked you are awesome Ill be donating on payday
[G4 Q&A, Help & Troubleshooting] scandiun:
Can I charge another devices using my LG G4 as a power bank? That means if it support inverse / reverse charging, which I presume doesn't support.
[G4 Q&A, Help & Troubleshooting] onotor:
I used OTG cable for connect LG G4 to a tablet. and one of them was charging.. I don't know which one. You can find it out by using OTG cable and usb a cable..
[Moto G4 Questions & Answers] 123jhoww:
Someone has captured the zip of OTA update for XT1626 to Nougat?
[One (M8) Q&A, Help & Troubleshooting] hegtam:
Hey Guys,

Maybe somebody has a solution to my problem.

I was trying to gain root access, but when I was flashing custom recovery I’ve got into a bootloop. I managed to solve the problem by dissembling the phone and removing the battery. Since then, it works, but I am unable to perform factory reset, because it just freezes on the HTC logo screen. Tried “—wipe_data” from adb.

[IMG="--wipe_data"]https://s20.postimg.org/vjoni3025/capture_12112016_170557.jpg[/IMG]

I can’t flash or boot custom or stock recovery from fastboot either. This way I can’t wipe the system from there. And I haven’t found a way to install supersu without custom recovery. I’m in pretty much a catch-22.

If I try to boot twrp and also with stock recovery, but it freezes on the HTC logo screen.

Anybody some ideas, because I'm running out of them.

Any help is appreciated! ;)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Not enough info. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Also, what version TWRP?

It sounds like you've taken the nuclear approach (taking the phone apart) when there are easier options. The power and vol buttons are hard coded such that:

1) If in a bootloop, simply hold vol down to enter bootloader the next time it reboots.

2) If the phone is simply "stuck" such as on the HTC logo screen, hold vol up and power for a minute or so, and this will force a reboot. Once the screen goes dark to reboot, let go of the buttons, and only hold vol down to get into bootloader. If the phone gets "stuck" on the logo screen again, you simply got the timing wrong (either started pressing vol down too late, or let go too early) and just repeat the process until you get it right.
[One (M8) Q&A, Help & Troubleshooting] hegtam:
I appreciate the help! ;)

The getvar all is the following:

version: 0.5

version-bootloader: 3.19.0.0000

version-baseband: 1.0.U20410.1@60201

version-cpld: None

version-microp: None

version-main: 2.12.111.1

version-misc: PVT SHIP S-ON

serialno:

imei:

imei2: Not Support

meid: 00000000000000

product: m8ql_ul

platform: hTCBmsm8939

modelid: 0PKV10000

cidnum: T-MOB101

battery-status: good

battery-voltage: 0mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

commitno-bootloader: 0b9a12e3

hbootpreupdate: 11

gencheckpt: 0

mfg-name: 0001

These are the twrp versions I tried:

twrp-2.8.7.0-m8s-qlul.img

And this is the result I get. Maybe I'm doing something wrong.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8

.7.0-m8s-qlul.img

target reported max download size of 16777216 bytes

Invalid sparse file format at header magi

sending sparse 'recovery' 1/2 (15368 KB)...

OKAY [ 1.595s]

writing 'recovery' 1/2...

(bootloader) signature checking...

FAILED (remote: signature verify fail)

finished. total time: 2.625s

I had an earlier problem, what is worth mentioning. When I first tried to flash custom recovery, after unlocking the bootloader. The phone went completely black, the only thing it did was if I put it on charger the charging screen came up. I tried the volume up + power button combination, but the only thing it did after 10 seconds was it went black and returned to the turned of charging screen. I had to dissemble and disconnect the battery. After that turned back on with no problem, except if I try to do factory reset or get into recovery it just stays on the HTC logo screen.

I hope, I give you sufficient info. :)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Are you sure the bootloader is unlocked, that it says UNLOCKED on the bootloader screen?

The error quoted above usually only appears when trying to flash recovery with the bootloader locked.
[One (M8) Q&A, Help & Troubleshooting] hegtam:
I relocked it when I was trying to install RUU. I tried it now with an unlocked bootloader. Now the result is the following:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8

.7.0-m8s-qlul.img

target reported max download size of 16777216 bytes

Invalid sparse file format at header magi

sending sparse 'recovery' 1/2 (15368 KB)...

OKAY [ 1.593s]

writing 'recovery' 1/2...

FAILED (remote: image error! (BootMagic check fail))

finished. total time: 1.620s

Any idea what can cause it?
[One (M8) Q&A, Help & Troubleshooting] jeroen_13:
Because you need the HTC Fastboot tools, and not the universal ADB tools.

https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/

If you use the HTC ADB Tools it will work!
[One (M8) Q&A, Help & Troubleshooting] hegtam:
Thanks both of you! The help is much appreciated! This was the solution. Two days of forum reading and trying ended! :D

I'm pretty new to this stuff, but this is how we learn, don't we?

All the best!
[One (M8) Q&A, Help & Troubleshooting] flipper325:
I just came across this thread, as my M8 seems to have been bricked -- all I get is this screen, and none of the options I select do anything, they all lead back to same screen, and the phone doesn't reset or recover.

*** Software Status Official ***

*** LOCKED ***

M8_UL PVT SHIP S-ON

HBOOT-3.190.0000

RADION-INVALID_VER_INFO

OpenDSP-INVALID_VER_INFO

0S-6.20.531.5

eMMC- boot 2048MB

Mar 1 2016,00:59:13.0

FASTBOOT

<VOL UP> to previous item

<VOL DOWN. to next item

<POWER> to select item

HBOOT

RAMDUMP

REBOOT

REBOOT FASTBOOT

POWER DOWN

I'm a newbee at this, so I apologize in advance if some of the advise from the experts is over my head, but I'm more than willing to learn, and try new things.

Any suggestions on how to proceed? Or is this terminal?

TIA,

Alex
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Be careful what thread you post in. There are a lot of important differences between your situation, and the top post. Not the least of which, is that the top post is about the M8s, which is a different phone from the M8.

Try the ROM Update Utility (RUU) which can be downloaded at the bottom of the following webpage. The instructions to install it, are also near the bottom ("Manual update instructions"): http://www.htc.com/us/support/htc-one-m8-t-mobile/news/

Keep in mind, that the RUU will wipe all personal data on the device. But given your current condition, there really isn't any way around this. And you may have already wiped your data (factory reset) in the bootloader options, anyway.
[One (M8) Q&A, Help & Troubleshooting] flipper325:
Noted, thanks. and thank you for the suggestion. I downloaded the RUU and per it's instructions, HTC Sync Manager, but I now have another issue -- I can't even get into the bootloader, the phone is totally dead. Previously, when I plugged it in, there was a battery charging icon, and then the phone would boot into the bootloader. Now, pressing Power and Volume Down buttons doesn't do anything, and plugging the phone in doesn't do anything either. Could it be that the battery wasn't really charging when plugged in, and once it's fully discharged I'm hosed?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Try charging for several hours (wall charger, not connected to PC) and then try holding power+vol up for a minute or so. Or just power button for a minute or so. Let us know, if there is any change.

If the battery icon was showing, you should be okay. Was this charging by wall charger, or connected to PC? You might try another cable and charger, just to be safe.
[One (M8) Q&A, Help & Troubleshooting] flipper325:
That did it, thanks! I must've been letting go of the buttons too soon. Left the phone on the wall charger overnight, and can get into the bootloader again by holding the buttons for a while. BTW, the charging LED is now solid orange, I think it was blinking orange before. Does that mean the battery is fully charged?

So I just tried running the RUU, but unsuccessfully. It sees the phone over the USB and correctly displays the current version, but I when I press to update the ROM, it tries to restart/reboot the phone, and comes back with a connection error after a while. I tried it twice, with the same result. FASTBOOT USB was highlighted, when I ran the RUU. According to the RUU Manual Install Instructions, that's where the phone should be... am I doing something wrong?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You're not doing anything "wrong" really, the RUU can just be really finicky. Try another USB port or another cable, even another PC if possible.
[One (M8) Q&A, Help & Troubleshooting] flipper325:
I tried different USB cables and a different USB port, with the same result. It looks like the bootloader doesn't restart after the PUU reboot command, regardless of how much time I give, I always have to start the bootloader 'manually,' with the Power and Volume Down buttons. Even when I do that, it seems to take longer than what the PUU allows, but it's a moot point that it never restarts from the PUU command. Anything else I could try?

BTW, what's the proper timing sequence for Power and Volume Down bootloader start sequence, in terms pressing and releasing these buttons? It always takes me a few tries.

Thanks again for all your help!
[JiaYu S3 Questions & Answers] achilipu05:
Hello,

I tried to install the new Nougat rom for jiayu S3, but it was unsuccessful. Phone got soft bricked, but I recovered it with a twrp backup.

My OS is android 4.4.4, and TRWP is 2.8. After installing the new rom , an installation error appeared and phone did not work.

I wonder it it's due to twrp 2.8, but I can't install twrp 3 (S3_h560_TWRP_3.0.2-0). There was an installation error with flashify...

The question is: can I install 7.0 from 4.4? Is it an Android problem, a TWRP issue, or just my clumsiness?

Thank you!
[JiaYu S3 Questions & Answers] Dior DNA:
in short:

To go from 4.4.4 to Nougat you need to go via LP RC5 via flashify using firmware upgrade.

This is because the partition layout is different from KK to LP onwards.

Then you can flash Nougat using TWRP (which will be version 3)
[JiaYu S3 Questions & Answers] achilipu05:
Thank you very much for your answer.

Please forgive me for my ignorance but, which LP ROM should I download? Can I install it via flashify, via TWRP 2.8, o flash?

Thank you again!
[JiaYu S3 Questions & Answers] fusant:
You can not use Flashify, you have to do it using Flashtools (with a PC) to go from KK to LP. Download LP 5.1.1 RC 5 from MAD.
[JiaYu S3 Questions & Answers] Dior DNA:
thanks to correct me, I thought Flashtools was meant
[JiaYu S3 Questions & Answers] achilipu05:
Well, I'm in trouble now... I installed successfully 5.1 in my S3, but when updated twrp 2.8 to 3.0, it did not work, so I can't install Nougat...

Now I have no twrp, and no root. How can I root to install twrp? I can't install superSU neither....

I'm sorry if it has been already answered but I can't find it.

Thanks a lot
[JiaYu S3 Questions & Answers] achilipu05:
I re-installed LP with Flash tools and everything worked right. (In twrp , it says 2.8 version, instead of 3.0, though).

Now I installed Nougat, and everything is ok.

Thank you for your excellent job!
[G3 Q&A, Help & Troubleshooting] AlexanderTbull:
Does anyone have the download link for the stock firmware for the d722? (LG G3s/beat) as kingroot turned off my phone while rooting and it's stuck at the "Life's Good" screen

I have tried all links given but non seem to work for me, thanks
[G3 Q&A, Help & Troubleshooting] killerro_lab:
lg-firmwares com <--- add dot before com ;)

cheers mate!
[G3 Q&A, Help & Troubleshooting] AlexanderTbull:
Thankyou so much man finally able to fix it! :D
[Samsung Gear S3] se47:
https://1drv.ms/u/s!AiN2zfzVljOknl_oTO6UBKPmdrgf

Enjoy :)

For flashing need NetOdin: https://1drv.ms/u/s!AiN2zfzVljOkgfNqAmRV7_n54YOdgQ

Instruction:

Step 1: On your S3 press then hold the Home/Power button until you see the S3 screen shows up "Rebooting..."

Step 2: Release the Home/Power button then quick Press it again 03 times.

Next step, you need to be a bit quicker.

Step 3: Use the Home/Power button to navigate to "Download (wireless)" option, then Press & Hold the Home/Power button to select. You have to be real quick otherwise your S3 will reboot.

Step 4: Press the Home/Power button twice, you will see the "[WPS Mode]" change to "[AP Mode]"

Step 5: Choose the Access point with the same name appears on your S3.

Step 6: Your S3 will show that it's been connected to the IP of your computer.

Step 7: Open the Odin, your S3 will show up.

Step 8: Choose the right file for each Option BL, AP and CSC from the files you extract after downloading. Then press Start and wait the PASS (15-20 minutes)
[Samsung Gear S3] venki5star:
How do we flash it? As far as I know, it doesn't have USB port
[Samsung Gear S3] marcushesketh1991:
Yeh how do we install this?
[Samsung Gear S3] Gio999:
Probably by wifi Odin.
[LeEco Le 1S Questions & Answers] nitindevss:
How to root le1s (5.8.019s eui ) marshmallow without bricking or loosing data
[LeEco Le 1S Questions & Answers] deinetod:
Flash custom recovery and flash supersu for TWRP recovery/
[LeEco Le 1S Questions & Answers] Shailesh1711:
http://forum.le.com/in/index.php?threads/easiest-way-to-root-le-1s.792/
[Motorola Droid RAZR] NAYN9:
HI am new in the forum so thank you and sorry for my bad English is not my main launguage.

Now my problem is a list of many problem.

all star wen i flash my razr XT910 verizone whit safestrap on a cm12rom but the problem is i use the xt912rom after instaling the rom the system crach on lunch and my safestrap hase ben delete i try to run the hard reset (i manage to enter the first menu but when i chose the recovry line and sect is reboting and show me the firs menu again i try to use the "batman Tools" but after i used and my phone lunch is switch to fastboot menu but in a failure mod whit somm line

-"invalid CG OTV (CG: system): invalid SP Data"

-"invalid CG version (CG: system)

-"invalid CG OTV (CG: system)"

but when i use the volum+&- and power bottum i can always chose the correct fastboot menu

i try the RSD lite Tools but is always show me "error (a file name) phone returne failur i try to delete this file instalation step on the XML file but is show me the same error in a other file i try allllllllllot of other roms but the same error (roms are not corumpted and no problem in download)

ihope somone can help me

[is not a battry problem i charge it by opening the phone and pute the +&- on the battry for charging]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mikeycollins13:
The t Mobile rom, while missing many useless gadgets like touch flo, at least worked with Tomtom without a hitch & Google Maps??

ANY idea how I can go back???

None of the posts on to get tt6 going worked for me.

TT works, but never ever finds a satelite, let alone a lock....

Thx!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] spaanplaat:
Had the same problem here. What I did to get it working is the following:

Firts go to External GPS settings then uncheck the manage GPS automatically box and start any gps software. You will notice nothing happens. Then turn your phone off and on. not soft-reset.

Then when your phone is running start any GPS software. Still nothing happens. Go back to the manage GPS automatically box and check it.

Now runs any GPS software and it will start as it should. Don't know what this is but I also have a vario III and I have to do this every time a flash a non t-mobile rom. But now my tomtom works. Oh and be sure you have a tomtom which supports built in GPS.