yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] roirraW "edor" ehT:
Heck, another variable is what people are using to extract the partitions from the zip. For all I know, one or more of the partitions I have people extract end up being zero length, even though again, I provide a screenshot of what the extracted partition image files should look similar to in their preferred file manager.

The only three partitions I had considered leaving out of these instructions are modem, persist and rct. (This is aimed at anyone reading this, not just you) The 35B sbl1 is absolutely necessary since the 12B aboot that's required to to be able to boot into TWRP and in order to run rooted on 46A/47A, in combination with the 46A/47A sbl1 cause a brick (QHSUSB_BULK 9008 mode, I believe), which is why I have the sbl1 flashed first. The 12B aboot need is explained above, and the laf (Download mode) should match the aboot, and also might be part of the combination that allows flashing older KDZs on 35B and higher, because it's good to have options.

I wouldn't feel right suggesting anyone else try this method with only those partitions unless I did it first, and there's that time factor again, and a little bit of a pain for someone who has things running just the way I want and I don't feel like doing an LG Backup and TWRP backup, and move everything I want to keep to external storage, etc, then flash the 47A KDZ or even flash the 10B TOT and then the 47A KDZ to make sure everything's as pure as possible, and then experiment.

If I ever have another reason to flash the TOT, like if I have a problem I can't solve otherwise, I'll try to keep in mind the possibility to experiment with this before I restore my TWRP backup, though.
[Verizon LG G3] ST Dog:
Understood. I can't go experimenting with the wife's phone either ;)

I'm just trying to make sense out of the black screen/rebooting when writing the partitions. Touching them should not cause anything to happen. Certainly didn't in my case.

I'll add, I had no SIM in the device when I did this. I guess messing with the modem could be an issue if it's active on the network.

Come to think of it, isn't modem the only one if them mounted during normal operation?

Perhaps enter airplane mode to take it off the network?
[Verizon LG G3] roirraW "edor" ehT:
? Yes, I'm less aggressive about giving my wife the latest exciting update any more. I wait until she has problems with her phone.

Take what I said about black screen when writing partitions with a grain of salt - I was saying if I remember correctly, and if it did happen I think it was only one or two users so that's not enough to really verify an issue - the more common black screen when rebooting into recovery is the only regular issue.

Your ideas and suggestions are good, though. I'm not knowledgeable enough about the partitions to answer that question. I will say though I never put my phone in airplane mode nor take the SIM out when I tested these steps 2-3 times, I keep my mobile data off except when I need it - so that's a variable to pay attention to in the future.

I meant to mention earlier am example of weird **** that shouldn't have happened is that among all the dozen times I've flashed the TOT and at least another dozen I flashed KDZs on only my G3, about 4-5 or so months ago when I flashed the TOT my Micro SD card was completely wiped and files were unrecoverable.

I didn't do anything weird or unusual, and always left the card in before then with no problems but now try to remember to eject it before flashing TOTs and KDZs. I didn't lose anything I couldn't get back other than LG Backup files and TWRP backups, and therefore my latest app data other than those apps I also use on my LG G Pad 8.3 because I use the cloud and RAID on my PC extensively, but it was shocking and unexplainable.
[Verizon LG G3] :
So I used this method once before when I was on 46a I believe, and it worked perfect. everything just worked. However, I tried it last night on stock 47A and it didnt really work. It rebooted into TWRP just fine, but when I went to flash anything, it would flash just fine but would bootloop endlessly. I even flashed another edition of TWRP (3.0.2), and I got the black screen with the blinking red and blue LED. No matter what I seemed to do it would have this issue. I literally followed every instruction word for word (copied and pasted commands, and made sure they were perfect). The only thing I can think of differently is that I extracted on my PC and then copied to internal storage. Should I just do this on the device directly? Thanks in advance.
[Verizon LG G3] roirraW "edor" ehT:
It shouldn't make any difference where you do the extracting, as long as the files are kept intact, and there's no obious reason they wouldn't be extracting them on a PC and transferring them over. The fact that you were able to both flash the necessary partitions and boot into TWRP tells me there's nothing wrong with what you flashed. Did you wipe Cache, Dalvik/ART and Data before flashing a ROM? Did you flash the necessary entire Bootstack after either flashing a ROM or restoring a TWRP backup?

How's the phone showing up in Device Manager in the Port section now when you have the phone connected? If QHSUSB_BULK 9008 mode, then Google that and you'll find recovery directions. You'll need the 10B TOT file.

If you've seen in the thread, there's been plenty of people who get the blue/red flashing LED when doing this, but I haven't in the 2-3 tests (at least once each on 46A and 47A), so I have no idea what's going wrong for some. There hasn't been any evidence pointing at any particular reason it's happened sometimes, hasn't happened others, and why I and some others have been lucky and haven't had it happen at all.
[Verizon LG G3] :
welp, didnt flash the bootstack. Stupid me. Thanks man
[Verizon LG G3] roirraW "edor" ehT:
Ah, cool (kinda). That would do it. Glad that was an easy solution. :)

Edit: I added "(and appropriate full Bootstack zip)" to the instructions/notices/warnings I give twice in the OP where I say that you have to flash a ROM after doing this method.
[Verizon LG G3] alich3451:
downgrade to 10b from 35b please help

I have tot 10b dll from 35b ... How to use them to downgrade ...
[Verizon LG G3] roirraW "edor" ehT:
I answered you in the other thread you just asked in. Please don't post the same question in multiple threads.
[Verizon LG G3] alich3451:
Ok got it. Now if you can tell me or refer to the post to use instructions on how to downgrade to 10b. Please?
[Verizon LG G3] roirraW "edor" ehT:
I told you where in the other thread.
[Verizon LG G3] soulfulb:
I just received a replacement G3 from Verizon with 48A, but it's not a K at the end of the model number. I received the KS error when attempting the TOT method. I'm assuming this method workaround wouldn't work due to not being able to root with Kingroot? I've used the flash tool as recently as 2 days ago successfully so I know it's working properly, but I can't seem to get it to work on this replacement. Any suggestions?

Thanks.
[Verizon LG G3] roirraW "edor" ehT:
That's correct, if you can't root the phone then you can't follow this method. Note that KingRoot might be able to root it now - I haven't tried in the few weeks since when 48A first came out.

If you can at least get LG Flash Tool 2014 to work for the KDZ method instead of the tool you used to try the TOT method, you might be able to downgrade to 35B using the KDZ, and then use this method. Or for that matter, once you downgrade to 35B, try the TOT method again just in case.

Matter of fact, this just gave me a simple but brilliant solution to the brick problem that happens to some people using this method. *IF* people are at least able to flash the 35B KDZ, then that would prevent the brick - but I don't recall at this point if those who had the KS Error weren't able to flash KDZs, either. From stock 35B through 47A, most users are able to flash any KDZ from and including 35B upwards. You definitely won't be able to flash older than that. Let me know if you can flash the 35B KDZ and if so, I'll add that to the instructions.

If all that doesn't work, I only have the usual suggestions. Different high-quality (preferably the original though) USB cable, different PC, updated drivers...
[Verizon LG G3] soulfulb:
Thanks for your help. I only tried the TOT method once yesterday. The phone actually booted back up after the error so i'm going to try one more time when I get home today. If not, then i'll definitely try to downgrade to 35B using the KDZ. Are the steps for the KDZ in this section or is it in the Return to Stock thread? I can use the flash tool to flash the 35B KDZ correct?

Thanks again for your help. If it works, i'm going to go with XDABBEB's new VS985. Excited to give it a run. I was running his stock 47A with your debloat script on the phone I returned.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! Good luck. Both. [MENTION=4795150]annoyingduck[/MENTION] 's stickied Return to Stock thread is in this section (and I link to in my signature below). :)

You use a different flash tool for KDZs. LG Flash Tool 2014, as the return to stock thread describes and I presume links to. You can also Google for it and find it's thread(s) on XDA. TOT is still preferable and more complete than KDZs - TOTs flash more partitions and can fix problems that flashing KDZs and ROMs can't. We've never come up with a definite answer as to what causes the KS Error for some, unless it's when the PCB is v2, although the model # isn't a "K" variant. You'd have to take the phone more apart to find out if the PCB is v2, but I wouldn't bother.

His VS985 v2 and v3 ROMs run the best! I think his kernel and other modifications really help with battery. FYI my debloat ALL zip will still debloat some things from his ROM, although its possible his "debloat" file switch debloat the same things, and in some ways, I know it debloats more. But you can use both, too. But if you want to debloat all without using the switch - or if you still want to use LG Backup, LG Home and/or LG Keyboard, just use my zips, that's all I'm saying. I plan on also using his debloat switch once I have everything setup the way I like.
[Verizon LG G3] soulfulb:
Thanks again. I found the flash tool. I also saw your file host link for the 35B. This is the correct one? 04._VS98535B_00_ARB00.KDZ-35B_00-5.1.1_Lollipop_10-3-2015-MD5_hash_inside.7z

So i'll try the TOT method one more time and if another error,

Flash tool the 35B KDZ from your file host above and then try the TOT method again?

Appreciate your help. I''ll report back later today.
[Verizon LG G3] roirraW "edor" ehT:
Yes to all. And finally if you can flash the 35B KDZ and the TOT still fails after, then you should be able to use the method in the OP since KingRoot worked on 35B last time I tried. You're welcome, looking forward to hearing how it goes.
[Verizon LG G3] soulfulb:
No luck. Tried the TOT method first. Same KS error.

Then I kept getting a connection error when trying to flash the 35b KDZ. I was able to flash the 47a KDZ but I was still unable to do the TOT method.

Any other suggestions?
[Verizon LG G3] roirraW "edor" ehT:
Since you flashed the 47A KDZ, you can follow this method. The only other suggestions I had, I had mentioned. Just don't be surprised if you brick following this method, although some people or maybe most or even nearly all were able to then flash the 10B KDZ or the 10B TOT after this method if they bricked, which is what this method aims to provide anyway.
[Verizon LG G3] soulfulb:
I'll report back when I have an opportunity to try this.

Thanks again.
[Verizon LG G3] roirraW "edor" ehT:
Had you read the second post of the return to stock thread, by the way? It tells about some "errors" that commonly pop up in LG Flash Tool 2014 that aren't really errors.
[Verizon LG G3] soulfulb:
I did. When the connection to server error came up, I ignored it. I waited about 10 min and nothing happened. Just stuck at 0% on the phone.
[Verizon LG G3] soulfulb:
Did every step in the OP and after I did the "reboot recovery", the phone cut off and never cut back on. I was able to see it on COM41 when trying to put it in download mode but i'm unable to flash any KDZ using the flash tool and I get a download fail when trying the TOT method. It also shows my PID and IMEI as all zeros when the TOT method first starts and then it fails shortly after that. Just a black screen when trying to cut it on.. Think i may have bricked it.

Getting a "USB port open" fail message using the TOT method
[Verizon LG G3] roirraW "edor" ehT:
Have you tried a different high quality USB cable or a different PC yet? Also if all else fails [MENTION=2250889]R-T-B[/MENTION] might be able to help you.
[Verizon LG G3] soulfulb:
Tried another cable. No luck. Don't have another PC to try at the moment. I'll try that and RTB tomorrow and hopefully it comes back on.

I appreciate your help.
[Verizon LG G3] roirraW "edor" ehT:
Hang in there, you'll get it fixed. You're welcome!
[Verizon LG G3] soulfulb:
Quick question if you know the answer. I'm going to try the unbrick method later today but just wanted to confirm if that is really the next thing I should try. When I hold the volume button up and plug in the USB cable, it vibrates like it's entering download mode but nothing on the screen shows up. I also see the phone in device manager(COM41). I have tried the TOT method and tried the KDZ method last night to no avail. Is the debrick method the method I should try now at this point or is there anything else before that?
[Verizon LG G3] roirraW "edor" ehT:
If you read through this thread you'll see that's the kind of brick that happens to everyone. It more than likely is going into Download mode, you just can't see it. If you're referring to the unbrick method having to do with shorting pins in order to force it into QHSUSB_BULK 9008 mode, I can't advise. I tried doing that several times one night and the next morning with no luck, and it turned out I didn't have to anyway and was able to recover just fine using both a different PC and different cable. So if there's any way you can use another PC, I'd try that.

I've had PCs that I was able to flash just fine from for months and months and then all of the sudden things stopped working right, and then switch to another PC and I was able to flash from it the first time.
[Verizon LG G3] soulfulb:
Okay thanks. Only other PC I have is a chromebook. I'll see if I can borrow one from someone.
[Verizon LG G3] roirraW "edor" ehT:
I have no idea if modern Libraries, which at least in my city automatically restore their PCs to exactly how they were before a user signed into it, would let you install and use the necessary drivers. They might since there'd be no permanent "damage" from anything anyone could have access to do on the PC, I just don't know if they limit you from doing certain admin-required things. Just an idea to keep in mind. If you were around Columbus, Ohio, I'd offer to do it for you.
[Verizon LG G3] b00ster23:
[MENTION=3761335]Soulfl[/MENTION]b How's it going? I can tell you from my personal experience I had the same nothing on the screen issue. I kept trying over and over and over....finally it went through for whatever reason. Just keep trying and stay persistent with the LG Flash took. :)
[Verizon LG G3] soulfulb:
Thanks for checking on me. I tried unsuccessfully pretty much this whole weekend with the phone. Left it on the flash tool overnight on Friday to see if it would flash. Then I also was able to try on my brother's PC to no avail. I decided to shoot RTB a message and I will send my phone to him so he can possibly get me back to 46A/47A. He has a high success rate so at least I will be able to have a stock phone again. It's my back-up G3 so I don't mind the wait. A stock phone is better than no phone. I didn't have time this weekend to try his method for the black screen and I'm going out of town in a couple days so won't have time to try anytime soon.

I appreciate "the road warriors" help. The G3 has a great community and I'll be sad when everyone moves on to their next phone.
[Verizon LG G3] roirraW "edor" ehT:
FYI, KingRoot still won't root 48A. I haven't tried on 49A but I doubt it.
[Verizon LG G3] iBolski:
And I can confirm you can still TOT flash back to 10b if you take the 49A OTA, as long as you don't have the K model of the phone.
[Verizon LG G3] roirraW "edor" ehT:
For anyone who didn't notice me say in the JasmineROM thread, just wanted to say I'm moving on to the unlocked HTC 10 and the Verizon Pixel 32GB in the next day or two. I've already got our HTCs and I love the 10. Will still be using it on Verizon for now, but no contract so that could change.

The Pixel will be mostly to just play with, and I might sell one.

Files I uploaded on Android File Host will remain there.

Thanks everyone for the help and teaching me so much!

I will likely sell the G3 while it's still worth a little something.
[Verizon LG G3] iBolski:
Going to miss you here! Your assistance these past couple of years has been awesome. Glad to hear the files will still be available.

I'll be sticking with this phone for awhile, even with the broken SD card slot. :crying:
[Verizon LG G3] roirraW "edor" ehT:
Thank you, you too and hopefully I see some of you around on my new devices or a different one later on! It's been my pleasure to do what I can to help a little bit here and there. I hope you can find a solution!
[Galaxy Note 3 Q&A, Help & Troubleshooting] amin12345:
Hi, Can anyone tell me how I could make the phone more responsive to the touch? Any files I could mod? I use to have galaxy s1 long time ago which I was able to do so by an application someone made. But I cant find this app. Is there any other way to make it more responsive?
[Galaxy Note 3 Q&A, Help & Troubleshooting] nijom:
Settings -> Controls -> Increase Touch Sensitivity
[Galaxy Note 3 Q&A, Help & Troubleshooting] amin12345:
Thats already ticked in my settings but im looking to make it more responsive by tweaking the system files. Anyone know how?
[Droid Turbo 2 Q&A, Help & Troubleshooting] Yshf9:
Has any one gotten the update? I'm still waiting on it.
[Droid Turbo 2 Q&A, Help & Troubleshooting] williamweaver:
Nope.
[Droid Turbo 2 Q&A, Help & Troubleshooting] gfrrt:
Nope
[Droid Turbo 2 Q&A, Help & Troubleshooting] imnuts:
Why couldn't this be posted in the update thread in general?

Sent from my DROID Turbo 2
[Droid Turbo 2 Q&A, Help & Troubleshooting] mjones73:
Check this thread for updates... http://xdaforums.com/droid-turbo-2/general/marshmallow-1-2-t3268958
[Droid Turbo 2 Q&A, Help & Troubleshooting] xbxjunkie:
better lock this thread down quick, some people panties get all bunched up
[Redmi Note 2 Q&A, Help & Troubleshooting] Acoca:
Hello everyone! I was wondering which rom is best for performance? If possible tell me the scores on AnTuTu and Geekbench, I know it doesn't mean anything, but it's nice to see big numbers :P

Thanks in advance!
[Xperia Z5 Accessories] nam2611:
Well I have a bit of trouble searching for a new case for my Z5, currently I using the Love MEI case but that thing too big for me so i need a new once.

I've read pretty much all the threads here but couldn't find any good case so i would like to ask which case suit for my need.

- Front & back protection again small drop(a bit buk is ok but not too much)

- I never use the finger print so I am not really care about it been cover or not

- If best can I ask is any case have mental back, I afraid that I will bend my phone even in my front pocket. ( again i dont use NFC much so i dont really care)

The best I've seen so far is the TUDIA Dual Layer Protective Case but it is for the Z5 Premium :(
[Xperia Z5 Accessories] tadei81:
You also have TUDIA Ultra slim Z5, but it is not dual layer. Check their website.

I have bought 5 cases so far for my Z5 (video review of them coming soon) and I must say I like two of them.

Custodia Cover RINGKE FUSION Case Trasparent - if you have black version I recommend smoked black edition or

Orzly® FlexiSlim Case cover 0.6 mm Super Slim for Sony Xperia Z5 - this one is really very slim and it really gives you the feel of the phone, but I think it is not very protective if you drop the phone. I am not going to test it ;)
[Xperia Z5 Accessories] Kirkland301:
Have a flick through Roxfit, they've got some decent cases and screen protectors (including tempered glass).

I've got the Ultra Slim Book Case for mine. it's a really nice case and I've had the same case on several Xperia's before. All of which survived drops, crushing and other general abuse.

https://www.roxfit.mobi/collections/xperia-z5
[Xperia Z5 Accessories] charlatan01:
Indeed, it looks like cases are kind of hard to find. Going to give one of these recommendations a shot and I'll throw up some impressions once I've used it for a few days. Loving the phone overall.
[Xperia Z5 Accessories] maxip:
After spending time looking for a case, I went for the Roxfit as it met my requirements (folio style, slim, credit card slot). It's been pretty good and has protected against a couple of 'small' falls onto floor / ground - unusually for me, I did use the provided screen protector which is starting to show some wear but hasn't affected the use of the screen in any way so it must be doing a good job.
[Xperia Z5 Accessories] chero90:
I use http://www.amazon.de/Spigen-SGP1180...&redirect=true&ref_=oh_aui_detailpage_o01_s00

&

a gorilla glas.

And im happy with it.
[Xperia Z5 Accessories] misbehave:
I bought RINGKE FUSION Case Trasparent.

Love it!
[Xperia Z5 Accessories] alexericl:
just choose a transparent soft case, simple but elegant.
[Xperia Z5 Accessories] CaeLum764:
I think you can get Case-mate tough case. I am using it myself.

Link to site here
[T-Mobile Samsung Galaxy Note II] mojorisin7178:
Hey I have my sim unlocked I did it using the hidden menu method I have used it on simple and more recently metro. I got a new Nexus so this is now my backup. The other day I put my girls tmo sim in and it worked fine but today I put my mother's metro sim in and it wouldn't get a signal. But it didn't say insert sim. So did I inadvertently relock my phone to tmo by putting a tmo sim in it?

Also I am on cm 12.1 and I don't have a PC to Odin back to stock so is there a way to unlock the sim without having to go back to stock?
[T-Mobile Samsung Galaxy Note II] mram11:
No re lock is possible.

There's no way you can relock your phone , it doesn't work that way, once is unlocked stays forever.
[Galaxy S 4 Q&A, Help & Troubleshooting] Halomaster2552:
Hello everybody, I need help with unlocking this phone. I've unlocked the hidden menu but there is no option called Perso Sha256 OFF. I dont know where this is located on the phone but if I knew, i could probably change it.

Any suggestions on unlocking this phone or locating perso would be nice.

Thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] davis the droid:
USC's bootloaders are already unlocked
[Galaxy S 4 Q&A, Help & Troubleshooting] Rhoban:
[MENTION=5111479]davis the droid[/MENTION], I think he is talking about carrier unlock.
[Samsung Galaxy Core Prime Questions & Answers] Amr okdeh:
Hello !

I can't move obb files to SDcard

I want Custom Recovery for Samsung galaxy core prime SM-361H

I need it because it very important to install apps

I want to install Xposed farmwork but it need Custom Recovery

And I want to move obb files to SDcard

If anybady can help me to move obb files please help me
[Samsung Galaxy Core Prime Questions & Answers] crazyraiga:
wrong forum. try here http://xdaforums.com/t/galaxy-core-prime
[Note Edge Q&A, Help & Troubleshooting] nsh121193:
Hello everyone. I just recently got a note edge, it's the verizon version but I have it on straight talk, the software that I'm running right now is 5.0.1, I want to update to the 5.1.1 version but when I try and do the update from settings everytime it tells me that software update is temporarly unavailable, any idea on how to fix that or if I can update via computer?
[Note Edge Q&A, Help & Troubleshooting] DudePharaoh:
if i am not mistaken, just download the latest firmware for your phone on your computer

use ODIN to flash the new firmware