yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] darkchazz:
I just fastboot flashed everything including the userdata image. It was the only way that fixed the issue.

Guess I have to install all those apps again..
[ONE Q&A, Help & Troubleshooting] pankspoo:
I think u accidentally went in to geust mode( it a possibility) . Check it!

Return to owner mode again.

Settings >users> owner mode
[Xperia Z3v General] asd520565:
i had flashed a wrong rom now my z3v is hard bricked cant enter flashmode but i can enter qhsusb dload 9008 but i need mbn and hex file who can help me

i have seen a thread about how to get mbn i just need someone that his z3v is good then use this command

adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=1' to get the partition.bin i hope someone can help i just try to save my phone

this is the thread about how to save the phone use qpst and how to get th hex,mbn,xml files http://blog.csdn.net/ziyouwa/article/details/8620595
[Xperia Z3v General] GigaSPX:
If you flashed something not for the Z3v, it's time to buy a new phone
[Xperia Z3v General] Bäcker:
no, he just wiped everything, the complete EMMC is empty now. No bootloader, nothing - but this is not the end, as he obviously still has the factory flashmode of the EMMC itself - he just needs the right files to flash.
[Xperia Z3v General] PDesire:
A problem could be the TA partition then.... If u have no backup of it then u have a serious problem.

Because just Sony and U with TA Backup have it

Your PDesire
[Xperia Z3v General] GigaSPX:
What brings you around to these parts? Lol
[Xperia Z3v General] PDesire:
Nothing, the S1 Bootloader of sony devices NEED the TA Partition to boot

Your PDesire
[OnePlus 3 Questions & Answers] billamin:
i am facing the weirdest wifi issue with my op3. last night i bought a budget reliance jio lte phone with unlimited data to use as a wifi hotspot device. but when I connect my op3 to it, the connection disconnects and reconnects after every 30 seconds or so. All the other devices connected to the hotspot ( An Le 1s, YU Yuphoria and a windows tablet are working fine without any interruptions.

Now to check whether my device is faulty, I created a hotspot with my Le 1s and connected the op3. it works perfectly fine.:confused:

Now i am at a total loss on what to do. i tried almost all roms , but the problem persists:crying:

any help would be appreciated.
[OnePlus 3 Questions & Answers] billamin:
Solved

:cowboy:

anyway since no one responded, i spent a night trying to be logical and finding where the issue might be. the thing is, lower end Jio handsets have IPv4/IPv6 as protocol selected by default. Most android devices connect flawlessly to hotspots created by these. However for OP3, Iphones etc, we need to select IPv4 only mode. It will work flawlessly then.

Though this post might be useless for most users here, Jio users in India, please take note in case you are facing the issue.
[OnePlus 3 Questions & Answers] Angadadlakha:
Thanks for that. I was going in for a second connection of JIO budget phone for home. This would help if my devices face an issue. I already have a connection from JIO which I am using in the 2nd sim of my OP3
[OnePlus 3 Questions & Answers] champak24:
How to select lpv4 mode in op3.please elaborate. Thanks
[Desire 626 Q&A, Help & Troubleshooting] tilakv95:
Hello! Can anyone please help me find a good method to root my htc desire 626 g+

Thanks in advance :)
[Desire 626 Q&A, Help & Troubleshooting] XDA-00:
Use KingRoot . Always successful. GL:good:

But don't mess with phone just yet! No custom Rom available for now.

KR :- http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
[Desire 626 Q&A, Help & Troubleshooting] tilakv95:
Haha no. I just need to root it to swap my internal memory and external memory :P

i don't plan to flash any custom rom just yet :p
[Desire 626 Q&A, Help & Troubleshooting] XDA-00:
Rooting successful?
[Xiaomi Mi 4i] zerocool420:
MIUI 8 Global Developer ROM 6.7.5 Features and Changelog

New Features

Introducing new design

Introducing Second space

Dual app support for most apps

Long screenshots

New Calculator

Introducing Quick ball

New templates for Notes

Redesigned Gallery

Smart menu for editing text

Highlights

New - App lock: Unlock all apps at once (06-23)

New - Deleting Second space while in First space (06-29)

New - Saved and available Wi-Fi networks appear first in the list (07-05)

New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)

System

Optimization - Loading speed increased twice for the first reboot after OTA (support for 6.0 devices) (06-21)

Lockscreen, Status Bar, Notification Bar

New - Animation for successful Wi-Fi connection (07-07)

Optimization - Floating notification format for incoming calls (06-22)

Optimization - Separeter sound and vibration permissions for notifications (07-07)

Fix - Repetitions in Settings (06-22)

Fix - Errors on Wi-Fi details page (06-22)

Fix - An error whe tapping the white area of the Notification shade (07-07)

Fix - Couldn't enter Mi Home from lock screen with Second space on (07-07)Home screen

Optimization - Hid the switch icon when there are no current tasks (06-27)

Optimization - Fixed sound effect for deleting apps (07-07)

Fix - Wrong app was opened after long-pressing the app in Task manager (07-07)

Fix - The button for switching modes didn't work in Task Manager in some cases (07-07)

Settings

New - Deleting Second space while in First space (06-28)

New - Saved and available Wi-Fi networks appear first in the list (07-05)

File Explorer

Fix - Couldn't see files saved from dual apps (06-28)

Quick Ball

New - Tap gesture for Quick ball (06-30)

AND MUCH MORE!

[IMG="1"]http://en.miui.com/data/attachment/forum/201607/11/115135exx2x8buopx55xc2.jpeg.thumb.jpg[/IMG]

[IMG="2"]http://en.miui.com/data/attachment/forum/201607/11/115138ojh5mnuzr9eeyeyy.jpeg.thumb.jpg[/IMG]

[IMG="3"]http://en.miui.com/data/attachment/forum/201607/11/115141mzahfttt1k1z1d7f.jpeg.thumb.jpg[/IMG]

[IMG="4"]http://en.miui.com/data/attachment/forum/201607/11/115151j780a297hya0saya.jpeg.thumb.jpg[/IMG]

Mi 4i

Fastboot 1161M

http://bigota.d.miui.com/6.7.5/ferrari_global_images_6.7.5_20160523.0000.23_5.0_global_3809247946.tgz

Recovery 961M

http://bigota.d.miui.com/6.7.5/miui_MI4iGlobal_6.7.5_99a85996e5_5.0.zip

download use and share your reviews...thanks
[Xiaomi Mi 4i] bagindov:
Need screenshot :(
[Xiaomi Mi 4i] sharan.nyn:
Screenshots

An album of 5 screenshots.

http://imgur.com/a/ANAXw
[Xiaomi Mi 4i] Ishrak:
Here's a whole video I uploaded

https://www.youtube.com/watch?v=zEJVD_6yDFY
[Xiaomi Mi 4i] davazlan:
* How does it perform?

* Does it support other launchers? (I remember that was a hassle with Miui 7)

* Other keyboards? (With Miui 7, other keyboards used to be very slow)
[Xiaomi Mi 4i] Nihhaar:
Everything same as MIUI 7 but the animation of folder opening is very buggy. Ofcourse, the heating problem still persists!!!
[Xiaomi Mi 4i] bagindov:
Also the spotify player on notification control is not visible.
[Xiaomi Mi 4i] davazlan:
Thanks guys for testing! I'll stick to AOSPA then :)
[Xiaomi Mi 4i] arunsebstn:
MIUI 8 Dev ver. 6.7.21 released. Anybody tested it. Is there any hope we will get MM? Any news.
[Xiaomi Mi 4i] uchihaobito:
Any review about battery backup (that's ACC. To me is the most important update in Miui 8)
[Xiaomi Mi 4i] Nihhaar:
Yeah, Great! But that lag though drives me nuts. (Even the folder opening animation is buggy!)
[Xiaomi Mi 4i] Dishan Chutani:
Planning to switch to miui again. Just waiting for some more info and bugs. BTW Android version?
[Xiaomi Mi 4i] Nihhaar:
5.0
[Xiaomi Mi 4i] DroidVin:
I have resurrection remix 5.7.2 with TWRP on my phone. I had taken a back up of MIUI 6.x before switching to resurrection remix. If I install MIUI 8 now, will TWRP go away?
[Xiaomi Mi 4i] Nihhaar:
Nope if u install it as recovery ROM. But if u install it as fastboot, u are out of luck. TWRP will be gone for hell.

:)
[Xiaomi Mi 4i] DroidVin:
In that case, can you please share the link for recovery ROM for MIUI 8, if you have?
[Xiaomi Mi 4i] Nihhaar:
Hey, It will be there in the MIUI forum and will be updated week to week. For time being this is the latest one:

http://bigota.d.miui.com/6.8.4/miui_MI4iGlobal_6.8.4_f47442f1f3_5.0.zip

I'm an MIUI insider but as I am using custom roms I can't receive insider updates. Don't forget to check MIUI forum once.
[Xiaomi Mi 4i] DroidVin:
Sorry to bug you, but I had tried to flash a MIUI 8 zip file (cant recall from where I got the link). But I couldn't flash it from recovery. It just didn't proceed, nothing happened from almost 10 minutes. Do you think this has to do something with the ROM (RR-5.7.2 (Android - 6.0.1)) installed on my phone?
[Xiaomi Mi 4i] Nihhaar:
No problem. But first look at this :

For installing MiUi follow these steps :

1) Go to twrp, wipe cache, data, dalvik cache, system. And again reboot to recovery. It asks No OS installed, just reboot to recovery.

2)flash Rom.

3)wipe cache, dalvik cache, data.

4)Reboot to system. You are good to go.

MIUI is very different from other Roms. While other Roms take 2-3minutes of flashing , MIUI can take abt 15min I remember. So, just wait until it flashes.

It has nothing to do about your previous installed ROM. All the best :good:

---------- Post added at 05:35 AM ---------- Previous post was at 05:04 AM ----------

Sorry my bad. Don't wipe data at end after installing MIUI. Just confused with other Roms. Wiping data deletes all preinstalled themes and you will be left only with the default one.
[Xiaomi Mi 4i] DroidVin:
It worked. Took almost 15 minutes :)
[Galaxy S 5 Q&A, Help & Troubleshooting] Anonumous21:
Hi everyone, I've got a Galaxy S5 on Fido Canada which recently got the marshmallow update, and I want to get the OTA update. I'm on stock ROM but rooted with busybox, xposed, link2sd, UPSM manager, MW manager and build.prop mods all without a custom recovery and I want to return my system status to official so I can get the OTA update. I know I can use Wanam xposed to set the status to official but I'm wondering if the update would screw up my phone due to my xposed version's incompatibility with marshmallow. Is it safe to use Wanam to get the update, will the new ROM remove xposed from my phone or will it brick my phone? I don't know how to remove link2sd's mountscripts, will they cause a problem in the update or will they automatically get deleted? my phone works good now but I want to know how to do it right before I touch anything. What is the best way to go about this? BTW I'm currently on kitkat
[8525, TyTN, MDA Vario II, JasJam General] slowndes:
I roam a lot and I find it very frustrating Activesync does not stay connected for push mail.

It requires me to start Activesync, start synchronisation, then confirm the potential additional costs.

I'm sure they've done this to minimize the data costs but I'd like to turn this off and stay connected while roaming. Anyone know how this is done? It doesn't seem to be an option in any of the menus.
[8525, TyTN, MDA Vario II, JasJam General] MetroKnight:
You can do this from the activesync screen, in the menu under schedule.

Select for it to download mail even when roaming.

"use above settings when roaming"

make sure that both dropdowns have "as items arrive" selected.
[Android Q&A, Help & Troubleshooting] Sudarshankakoty:
It's been around a year, and I am not getting any custom recovery update or custom ROM for my device Micromax Bolt Q370, which has 1GB RAM, 8GB internal storage, 1.2Ghz processor, 5MP camera with Android 5.1 lollipop, having Firstouch OS. (Rooted)

I made a nandroid backup with TWRP using Live Backup option, and I often brick my phone doing some stupid modifications. I hope and request to all the XDA developers to make a custom recovery and ROM to this device soon.
[Verizon LG G3] R-T-B:
I have a new LG G3 from Verizon I bought to replace my aging Motorola Droid RAZR M. It seems this one is a model "vs985K" which I have never seen mentioned before. It shipped with 47A Marshmellow, and conventional tot flash methods (using 35B dll and such) do not work. States "no ks version."

So I dd'd in the relevant partitions from the 35B bootstack, and TWRP as needed. It bricked the phone. Black screen. Nothing.

Fortunately, I am not a noob at this. I shorted the testpoints to get into qualcomm 9008 mode, and to my absolute horror, even BoardDiag 3.99 would not talk to the board. It seems this may be a new part number. Swapping some files from a another tool got it to finally flash, and I'm still trying to recreate what I did, but however I did it now I know I have a tool that can debrick it via qualcomm 9008 mode and so I'm ready to try again.

After some messing, it seems the exploitable aboot is what makes it brick. Unless I am missing something. Anyhow that's not the point of this post. The point of this post is to discuss this potential new variant, and how the heck to get this on 10B. Any ideas? It really seems tough if I can't use the exploitable aboot. :(

PS: I would post how to debrick a vs985K, but because it uses tools and software that is of questionable copyright status, I can't. PM me if you are desperate and maybe I can help you, though. ;)
[Verizon LG G3] roirraW "edor" ehT:
The K is probably just referring to the color. Is it black?

Some people get bricked doing what you did, others it works fine including me when I tested that method several times. I have a thread in the General section about that method. The title includes "KS Error".

When some people do something that causes the black screen, they're still able to go through the motions of putting it in Download mode and you can see its in that mode in Device Manager, and then able to flash either the 10B TOT (with downgraded partitions, there's a chance you wouldn't get the KS Error any more) or the 10B KDZ, since the downgraded partitions would now let you flash any KDZ you want.

As far as I know, everyone who tried that method - those who didn't brick and those who did, were able to downgrade to 10B via TOT or KDZ after. Read the thread for more details.
[Verizon LG G3] R-T-B:
Yeah, I was following your post. It led to a black screen. I know I got all the partitions but I had to short the test pins and use qualcomm 9008 mode to get back.

I'll try again and report back. Don't see what I could've possibly missed though. I'm trying to get back to 10B in the end.
[Verizon LG G3] R-T-B:
Back at the black screen. LG FlashTool for TOT method seems to not want to flash it even though I can "kinda" get it into download mode (it just doesn't show anything on screen, but registers in device manager)

See attachment.

KDZ Methods similarly fail with "upgrade stopped due to an error"

Currently sitting at qualcomm 9008 mode with boarddiag, so if you have any ideas of what to flash, I can do basically anything, lol.
[Verizon LG G3] R-T-B:
It seems flashing aboot is the culprit. I can flash just about any other part of the bootstack without issue. Is it possible 47A is blowing a qfuse or something to prevent aboot downgrades?
[Verizon LG G3] roirraW "edor" ehT:
I really couldn't speculate, I refrain from guessing. There's guesses out there covering at least a few possibilities, but the only circumstancial evidence is the "KS error" and the fact that some get the black screen, but it's weak evidence since I'm pretty sure that some who got the KS error were successful downgrading without a hitch, and I know for sure others who bricked were definitely able to recover.

I'd try a different PC. Using the original USB cable? Using a USB 2.0 port that comes directly off your PC's motherboard, and not a USB 3.0 port or a USB hub?

Do you have the right special drivers to use with BoardDiag?

As far as I know, I've never come across anyone who couldn't downgrade eventually, and all our VS985s have a letter after the model number signifying the color.
[Verizon LG G3] R-T-B:
Thanks. I didn't know about the extra letter, and mine is indeed black.

You've given me some leads to chase, if nothing else. :)

I'm not afraid to mess as I can debrick just about anything. First up on my list of things to try is a different USB port (I was using a USB 3.0 port).
[Verizon LG G3] R-T-B:
Weird, after experimenting a lot, I find that the KDZ tool (from a fresh 47A install) let's me downgrade to 35B, but it ALSO gives me a black screen with similar behavior.

No idea what that means, but for whatever reason, it seems this device will not accept pre-marshmellow boot loaders.
[Verizon LG G3] R-T-B:
http://xdaforums.com/showpost.php?p=66096623&postcount=965

This does suggest a qfuse is blown by 47A. Unfortunately, it seems newer production phones like mine DO obey the qfuse, and I would furthermore speculate that LG/Verizon did this intentionally to cover these new phones.

The fact that mine can't flash (or rather can, but dies) a 35B KDZ, and was purchased fairly recently directly from Verizon (preflashed with 47A) all support this.

It looks like we may need to find an exploit for the marshmellow bootstack (or an outright bootloader unlock) if we want to unlock newer production phones. Unfortunately, I doubt this platform is new enough to attract devs with that kind of skill. However, I'm still here and willing to test any and all exploits, being if there's one thing I CAN do, it is unbrick a phone. :)
[Verizon LG G3] b00ster23:
[MENTION=2250889]R-T-B[/MENTION] For the sake of discussion and trying to add more content I will add to this post. What you experienced was similar to what I had...well sorta. I have 4 LG G3's in my family. The first of which was mine from over a year ago. I was able to use KDZ and TOT methods to do what was necessary in rooting and then taking advantage of the aboot exploit for the first 2. However, I want to say that the 3rd and 4th version of the VS985 gave me a few fits. It was the 3rd handset that I had received that my wheels were spinning with trying to downgrade using the TOT and KDZ methods. Eventually, TOT worked for me, but similar to you I had gotten into an issue where the black screen of death was upon me. It felt like the grim reaper had come to take my new handset... :( I swapped USB ports, cables, DLL's and through much hair pulling finally was able to recognize the phone properly with the TOT method and downgraded. I never really got the phone display to work... I went into download mode blind by using another phone as a guide. Regardless of all the trouble I finally achieved success. By the time my fourth handset came from VZW, VS985K, I was running into the LAF/KS ERROR. Used the same cables, ports, dll's, etc etc. NEVER was able to downgrade... The only method that worked as a last ditch effort was the afore mentioned. Speculation is certainly dangerous, but I would surmise that VZW maybe made some slight hardware changes. Perhaps a slight change in manufacturing of the IC of the motherboard...who knows. But certainly everything done here is at our own risk. I was willing to flash mine immediately, as falling back on the 30 day satisfaction guarantee was there from me.
[Verizon LG G3] R-T-B:
Yeah, examination of my PCB shows it is version "2" as well, suggesting maybe this isn't the first revision. Maybe they are getting smarter.

I tried to go through the prcoess of accessing download mode with the black screen but the phone was completely dead to all input and would not respond to LG flash commands anymore.

Don't get me wrong, I am not complaining I still have a phone afterall and I know this is all at my own risk. :) This may be speculation but I'd like to think it is educated speculation that a new hardware revision exists.

Is anyone else willing to open their phone to see if the top of their PCB (The part near the camera) has similar markings to mine? It is inscribed (in gold) "VS985 HW V1.0 (2)". Note the "(2)" that makes me think they revised it a second time.
[Verizon LG G3] R-T-B:
I'm going to try to use boarddiag to flash the entirety of the TOT. Any reason why this would be a bad idea? Seems as good as any at this point to see if it truly can't run 10B.

This may take a very long time, but heck, why not try?
[Verizon LG G3] R-T-B:
Did not work. I think we can safely say whatever variant I have, a pre marshmellow bootloader will never load.
[Verizon LG G3] SofaSpud:
Is it necessary to disassemble the phone to expose that part of the pcb? Received my factory refurb vs985 two days ago, and am interested in rooting it. Just removed the back and don't see any part of the pcb.

---------- Post added at 01:01 PM ---------- Previous post was at 12:57 PM ----------

My device shows a mfr date of 10/26/15. Settings/about identifies as Rev 1.0, don't see any model reference numbers with "ks" suffix.
[Verizon LG G3] R-T-B:
I wouldn't advise disassembly to check for the markings unless you've already voided your warranty for some reason, but thank you for thinking of me and looking around your phone. :)

My advice to you would be to start by poking around the forums and looking up how to do a 10B TOT revert. You'll need the TOT file, and a .dll to go with it most likely. This is the safest way (if it works) to revert to firmware where you can get (and keep) root.
[Verizon LG G3] roirraW "edor" ehT:
Could you clarify something? Have you been able to recover from the black screen issue? I was under the impression you have but now I'm not sure.
[Verizon LG G3] R-T-B:
Yes, I recovered, but it was complicated.

First off, I had to use a modified version of BoardDiag (I can upload this if anyone needs it, but I'm unsure as to it's legal status) with the qualcomm drivers and testpoint shorted. Second, I had to reflash the 47A files via that method, anything lower than 46A will brick it again.

All in all, it's pretty messy to recover from what I did, but I was confident enough that I've probably done it 4 times now... unfortunately all without success reaching anything below 46A. Even a 35B flash bricks it. :(
[Verizon LG G3] SofaSpud:
I have a vs985wk, just recently purchased. I believe that the 'W' is for the color, which is white.
[Verizon LG G3] R-T-B:
Interesting. What's the "K" mean then?
[Verizon LG G3] SofaSpud:
Good question! After reading your posts I looked around a bit for info re the 'k' but didn't find much.

I have yet to root (or even carrier activate) mine. I just received the Totalwireless similar today, but am thinking that perhaps I shouldn't activate until after rooting and disabling OTA, in hopes of avoiding further lock down against rollback. Device is rollback level 2, FW 47A.
[Verizon LG G3] R-T-B:
Where did you find it's rollback level? I'm just curious.
[Verizon LG G3] SofaSpud:
It was via a hidden menu dial code. Have been looking to find it, but can't seem to. It brought up a screen that had several entries, similar to Settings / About phone

---------- Post added at 08:54 AM ---------- Previous post was at 08:51 AM ----------

I'm thinking that the 'k' might designate LCD or chassis style.

---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------

I'm thinking that it might be tied to the LCD assembly or chassis style.
[Verizon LG G3] SofaSpud:
Two days ago, as I was reading discussion threads on xda and various other sites, I came across information giving a dial code to access a screen showing several items, one of which was the current device rollback level. My VS985wk came up ad level 2. Have you seen that dial code published anywhere? I carelessly failed to make a note of it, and I can't seem to find it again.
[Verizon LG G3] R-T-B:
No, I have not heard of that dialcode or used it unfortunately, but I will share it if I happen across it!
[Verizon LG G3] samisertiwutia:
google says, this is color of device
[Verizon LG G3] R-T-B:
Still not entirely convinced that's the case, but it's quite possible that letter has nothing to do with this new revision and is color code. But I've seen "VS985B's" which are black, which confuses me further.