yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] hichs:
I was in twrp recovery because I wanted to wipe my oneplus and start from zero.

I have no idea what I've done, but I can't boot my phone anymore...

All I see is the oneplus logo and I can get in twrp...

It says there is no OS installed, so I started searching for a way to fix this.

I've been trying to go into ADB sideload on the phone and cmd on my windows PC, but no success..

I can't seem to install a factory ROM from here.

I'm not able communicate with your phone through fast boot and ADB

C:Downloads\Compressed\fastboot>adb devices

List of devices attached

* daemon not running. starting it now on port 5037 *

* daemon started successfully *
[Android Q&A, Help & Troubleshooting] victormetal92:
Did you format all partitions?
[Android Q&A, Help & Troubleshooting] hichs:
OnePlus One NO oS

Yes all partitions format.
[Android Q&A, Help & Troubleshooting] victormetal92:
That means that you ereased the OS, so you need to install it, maybe via TWRP, CMW or Fastboot mode.
[Remix OS for PC] StardustGeass:
So, here is my tablet condition:

1. UEFI

2. Windows 10 32 bit

3. 64-bit Processor

4. Secure boot already off

RemixOS version I use : 64bit Beta version (with UEFI compability)

Installed it using "official procedure tool'.

What have I try to do and what happens after it:

1. Installing remix OS via installer provided on Hard Disk (C: drive only available with 7GBs of free space)

a. Rebooting using provided reboot message from installer

Result : rebooting automatically to win 10 without boot option.

b. Rebooting using "shift + restart" (Advanced Startup)

Result : When choosing "boot from a different place", there is "Remix OS" listed alongside with "EFI USB", "USB CD", etc. But, when I choose Remix OS, it runs straight to windows 10 instead (no error or anything else, just boot through it).

2. Installing Remix OS via installer provided on USB drive (32GB)

Same result with point 1a and 1b.

Other options I have "tried":

- I have tried installed using EasyBCD, but turns out it doesn't provide much compability with UEFI boot mode.

- I tried using easyUEFI, but since I don't have any FAT32 drives (my SD Card is exFAT formatted, and C: can't be partitioned using partition manager tool), it doesn't help me.

- I tried using the grub2win option, but since my windows version is a 32bit one, grub2win can't run.

- There is no option to turn the UEFI BIOS mode to legacy.

Question:

- Why the booting runs straight to windows, without even showing any boot options?

- Why the booting still runs straight to windows even after selecting Remix OS from advanced startup boot?

- Any options left for me to try?
[Remix OS for PC] Mr.Lolendo:
You can not run any 64 bit OS on this Tablet. Because UEFI only support 32 bit OS. Many Bay-Trail tablets has this limitation.
[Remix OS for PC] tailslol:
I agree here,baytrail is generally 32 bits
[Verizon LG G3] roirraW "edor" ehT:
Reserved.
[Verizon LG G3] roirraW "edor" ehT:
Reserved 3.
[Verizon LG G3] mopartonyg:
Thanks for this thread, it will help a lot of people if they just follow the instructions. Can this be done from ADB also?
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! I don't see why not. I prefer direct on the device - also makes for simpler instructions and "support", since I don't want to troubleshoot anyone's ADB, USB or USB Debugging problems. :)
[Verizon LG G3] mopartonyg:
Very true, the least amount of instructions the better.
[Verizon LG G3] someguyatx:
This is an interesting method, thanks for sharing.
[Verizon LG G3] andy_zhang:
Why has not kdz.

vs985 China user
[Verizon LG G3] reaper420:
I tried doing this and I guess I rebooted at the worm time because now my phone won't reboot. It says secure boot error in the corner and goes black and the lead is flashing red and blue how can I fix this? Any help would be appreciated
[Verizon LG G3] roirraW "edor" ehT:
You can't get into TWRP, either? As I mentioned in the OP twice, once you do this you can't boot the ROM, you have to get into TWRP and flash another ROM. You could follow the instructions in the stickied return to stock thread in this section, also in my signature (not my thread). Use the 35B KDZ.

Or you can use the 10B TOT method along with the 35B .DLL and root with the Stump app and put TWRP on with TWRP Manager.
[Verizon LG G3] reaper420:
Thanks for the link I got it downgraded to 10b now I just need to get it rooted and twirl on it
[Verizon LG G3] roirraW "edor" ehT:
Good! Glad you got that solved reasonably easy. It's twerp, not twirl! ;)
[Verizon LG G3] reaper420:
I should have just downgraded to 10b to start with. Root and trwp installation is so much easier, now I just need a good aosp rom it
[Verizon LG G3] Juhful:
Once I have Twerp installed do I have to flash a custom ROM or can I flash xdabbeb's VS985 46A - Stock Flashable Firmware? Which is what I want to end up with. I am currently running on 35B. Thanks for your work!
[Verizon LG G3] roirraW "edor" ehT:
You can flash whatever you want. I'm using that 46A. You're welcome!
[Verizon LG G3] Juhful:
Awesome, will try this in the next few days and will post my results!
[Verizon LG G3] relagent:
Wouldn't it be easier to use flashify?
[Verizon LG G3] roirraW "edor" ehT:
Installing TWRP on anything past 12B isn't as easy as just flashing TWRP, no matter what you flash it with.
[Verizon LG G3] Juhful:
Ok, hopefully this will help anyone trying this method. First of all it worked, I went from 35B stock recovery and now I'm running xdabbeb's vs98546A, but it was touch n go lol. Followed the procedure to the letter after posting the script in terminal emulator my phone rebooted into stock recovery, I have no idea why, I picked the power down option and attempted to reboot into recovery and was getting the red, blue blinking light that just hang there with a black screen, I tried again to boot into recovery, still the same black screen with the flashing light. I must have tried 5 or 6 times to reboot into recovery and on my last attempt it booted into Twerp! I proceeded to install xdabbeb's 46A stock firmware with total success, now running Marshmallow 6.0, rooted with Twerp! Thanks again to @ roirraW "edor" ehT for this!!!
[Verizon LG G3] :
Oh OK. I've never rooted past 12b. I've always downgraded to 10b. Good to know.
[Verizon LG G3] toy028:
After the last commands are typed in and ran you can then just type reboot recovery. That will reboot you right into recovery so you can flash a rom.
[Verizon LG G3] JayDream:
same here, were u able to fix it?
[Verizon LG G3] roirraW "edor" ehT:
Post # 12 and 14.

Without seeing exactly what happened in terminal emulator when you pasted the commands, there's no way I could guess what happened. I did this myself and it worked the first time without a hitch.

You might be able to flash a KDZ for 10B (@annoyingduck 's stickied return to stock thread in the General section) now since you downgraded the laf.img and some other partitions using this method, but only trying would tell for sure. Again, I can't know what's going on without seeing what happened in terminal emulator.

If flashing a KDZ won't work then you'd still have to resort to the 10B TOT method.
[Verizon LG G3] Juhful:
Same happened to me, I just kept pressing the volume down and power buttons to boot into recovery, it rebooted with that same error and the black screen and flashing light several times, but I kept trying to boot into recovery and it eventually worked. I didn't want to have to go through the downgrading to 10B scenario, that's why I kept trying to boot into recovery, why it finally worked I have no idea, but it has been running great and can get into Twerp anytime now. Good luck.
[Verizon LG G3] toy028:
I tested this on 35B and it works 100%
[Verizon LG G3] JayDream:
Ok I got it to work after reading through this thread. I used terminal emulator app while still on stock 35b, I copy and pasted your commands onto Terminal emulator then attempted to boot into recovery thru adb after it was finished. It took me to the boot secure error page instead. I did a battery pull, held down power and volume down buttons until it booted into stock recovery. It wasn't until after I pushed clear cache in stock recovery, that it finally booted into twrp..

Everything seems to be working now, except every time I boot into recovery it takes me into stock recovery until I hit clear cache or factory reset, and then twrp boots up..
[Verizon LG G3] roirraW "edor" ehT:
Glad you got it working. That's the way custom recovery is for all G3s. You can press Clear Cache or Factory Reset, either one to get into TWRP.
[Verizon LG G3] roirraW "edor" ehT:
Added information in OP (after testing) that this allows downgrading to any stock release via the KDZ method with LG Flash Tool 2014.

Added a couple of screenshots to help those inexperienced with what the command's output in Terminal Emulator should be if they work correctly.

Hopefully that helps keep any others from experiencing the issue some others have had where it took several or many more attempts to get into TWRP the first time after this; after which they were able to get into it just fine on any further attempts.
[Verizon LG G3] undeadking:
Am I reading this wrong or does this allow those on stock 35b to flash TWRP without the use of a computer? I'm currently without a computer or TWRP so I hope its not my desperation making me read the OP incorrectly.
[Verizon LG G3] Juhful:
No need for a pc, just follow the instructions and you're good to go.
[Verizon LG G3] Snuzzo:
First, thank you [MENTION=2560614]roirraW "edor" ehT[/MENTION]

Second, everyone BE CAREFUL using this method. One small typo using a dd command has the potential to brick. I know it was mentioned in the OP but just clarifying for everyone here coming from another android avid and semi-dev.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome!

Absolutely true. I always copy/paste when I can, but mainly just because it's so much easier! :D
[Verizon LG G3] Snuzzo:
Typed in commands to the T. Not getting anything after invoking reboot recovery. No power, no LED light on charge. Its a doorstop. Was on stock 35B.
[Verizon LG G3] roirraW "edor" ehT:
For some reason, some people have had it where after this they had to manually go into recovery from the phone being off a bunch of times, and eventually it would go into TWRP and after that they didn't have any trouble getting into TWRP at all. Their posts are in this thread.

Have you tried going into Download mode?

I've done this twice without one problem. I don't know what's going on for some others. I don't know if there's a chance that what I choose to normally do - shut down the phone and then manually go into TWRP the first time, would make any difference.

Here I had hoped by your earlier post that you had successfully done this and hadn't had the issue some others had.

I had contemplated switching the instructions to instead use the app GScript (assuming it's still available) and run it through there with logging to the Micro SD card so that at least once people got their phone up again (as far as I know everyone has) I could at least have something to look at to see if there's any hint there what's going on.
[Verizon LG G3] Snuzzo:
Not even reacting to download mode for me. I was using copy/paste from ES Note editor. It's acting like its on a completely dead battery that won't even charge. Half bummed half not, it was a CLNR and I'm on Tmobile prepaid with a Nexus 6 now, was only going to cook up a few mods and a rom for it.
[Verizon LG G3] roirraW "edor" ehT:
Have you actually checked in Windows' Device Manager to see if it shows up in the Modem section? There's been times when on this phone things have happened (usually a mismatch of partitions from different LG releases) that cause the phone to look like it's not doing anything, including black screen, but you could see it was in Download mode when you went through the motions by looking in Device Manager, and flash it via KDZ or TOT method.

So you can't get into the stock-looking recovery either? Even if it "looks" off have you tried to go through the motions of force turning it off, and then the same to go to recovery?

Or if it's not showing up in the modem section, last ditch effort would be if it shows up as QSHUSB_BULK (I forget if it shows up as that in Modem or Ports or where), which has a different recovery process.
[Verizon LG G3] Snuzzo:
Yup got QSH Bulk. Got the needed drivers. Just looking at the unbrick guide now.
[Verizon LG G3] roirraW "edor" ehT:
Cool (kinda). Glad it should be recoverable at least. I've recovered from that twice when doing some experimenting (not for this, something else).

I'm thinking of expanding the directions to instead flash every single partition given in the 35B bootstack, even though I did what I describe from both completely stock 46A and 35B without a problem. I wish I could know for sure what's going on but without more information or even being able to reproduce the problem that's my best guess for a possible solution in the future. Sigh.
[Verizon LG G3] Snuzzo:
Something that might help, try doing a cp to /data/local/tmp of a bash script from storage to there with 777 perms. Then invoke the script from terminal emulator with su permissions. That way it will cut down on any typos made, I have a feeling i have fuct something with my cp pasta. Now to find a kdz of 10b to use with flashtool. I am currently downloading 10b's tot.

POSSIBLE to go in to more detail with an MD5/SHA checksum verification too.
[Verizon LG G3] roirraW "edor" ehT:
If you didn't already find it, all the available KDZs (and the TOT you're already downloading) are linked to at the bottom of the first post of [MENTION=4795150]annoyingduck[/MENTION] 's stickied thread in General, also the first link in my signature below.

I'm normally a strong advocate of checking MD5s and in some other guides of mine I've given all the directions on how to do that but there's several reasons I don't think that's practical for this:

1. Despite instructions saying to check MD5s, it's my observation very few people do so.

2. All hash checking apps I can find in the Play Store will only get the hash for one file at a time. I normally use [MENTION=2693923]scary alien[/MENTION] 's Android File Verifier (AFV) and it too only checks one file at a time. That would be tedious to do all the partitions on while the phone and I'd rather not involve having to use a PC, and even more reason to doubt people would actually perform this step on all the files.

About the only file I would consider giving instructions to check it's hash (for those not familiar with hash checking) is for the recovery itself, since it's being downloaded direct, and not extracted from an archive.

3. In my experience, if an archive extracts without an error message then it's rare that a file is corrupted when extracted, and if an archive is damaged enough it won't extract at all.

I'll think about the script idea. If I were to go that direction I probably would instead go the GScript direction instead so it would have a user-friendly interface in addition to logging (which I'm sure, could be scripted too).

Thanks!
[Verizon LG G3] Snuzzo:
Recovery from QSH Loader to Download mode went without a hitch. Awaiting the kdz to finish downloading.

Here's a link on a guide for those of you who get QSH_BULK issue that I used:

http://xdaforums.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928

Follow [MENTION=4795150]annoyingduck[/MENTION] 's method for restoring from download mode from there:

http://goo.gl/8Jm8mb
[Verizon LG G3] roirraW "edor" ehT:
Awesome! It's always a relief when *some* things go as planned.
[Verizon LG G3] Snuzzo:
Yup! should be back on 10b here within the next 30mins. Lucky I have a G2 and know most parts of the software (not all).

EDIT:

http://xdaforums.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

Will this work on 4.2.2?

---------- Post added at 03:52 PM ---------- Previous post was at 03:08 PM ----------

Re-did your method on a 10b kdz. Went without a hitch over adb shell instead of terminal emulator.
[Verizon LG G3] b00ster23:
Thank you sir. Worked like a champ! For whatever reason, I was running into the same "LAF" error message saying something about a "KS" issue. This was a new phone shipped directly from VZW. I'm thinking something was slightly modified since the last LG FLASH TOOL was released. Either way this method worked without a hitch into TWRP 3.0 Dropped down my custom ROM and Boom goes the dynamite, I'm in business.

THANKS AGAIN!
[Verizon LG G3] roirraW "edor" ehT:
Awesome! Glad to hear it. Might add the "solve KS issue" to the thread name since you've confirmed this solves the problem for those. You're welcome!
[Verizon LG G3] b00ster23:
One thing that I should mention, because I'm cautious like that, I dropped down the 35B stock image prior to KingRoot and the manual push of the selected partitions. Its possible that the KDZ image may differ from the shipped 35b. Pure speculation on my behalf and probably nothing like that going on. I would just hate to have someone go thru the process afore mentioned and find out there are slight differences. Once again...probably completely without merrit, but wanted to mention my process of success. :) happy rom'ing
[Verizon LG G3] roirraW "edor" ehT:
Yep, we've speculated that there might've been something different either about the hardware or the 35B that came on more recently shipped phones. If anyone with this same situation would root with Kingroot and then pull the partition images off, we could compare and find out if this is the case.

[MENTION=2941286]xdabbeb[/MENTION] and I did this for 46A since we had people who had received the OTA weeks before everyone else started getting it, and I wanted to make sure that their OTA was the same as the one we got after it became "official". They were the same, by the way.
[Verizon LG G3] b00ster23:
Also worthy to be noted... I did see where the software was listed as "modified" after I used KingRoot on the shipped config. When I dropped down the 35B KZD image and KingRoot was applied, I got "official" With Azadi on afterwards, I still have official in the newly shipped phone.

My other G3 says modified, which doesn't surprise...I've dropped all kinds of stuff down on it....it runs Azadi as well. :)
[Verizon LG G3] roirraW "edor" ehT:
I'm pretty sure there's something ROM developers can do, which is what "forces" an official status, at least until something else make it read modified again. [MENTION=2941286]xdabbeb[/MENTION] 's ROMs say "Official" too. My phone still says Official on [MENTION=2941286]xdabbeb[/MENTION] 's stock 46A too, with Xposed and even further debloating than I provide via the debloat zips in his thread.

Attempts to root a stock ROM, even if unsuccessful, tend to make it read "Modified".

I wonder what, in particular, caused your other G3 running Azadi to read "Modified"?
[Verizon LG G3] hochoch:
So, I had my G3 repaired by LG after it just stopped working one day. It came back with 46a already installed. I rooted with kingroot, verified the root using root checker then ran the scripts. And then my phone stopped working. Just black screen, no recovery, no download mode, nothing. it showed up in my device manager so i tried the kdz and tot method and just attempted the hardbrick guide. nothing has worked. So, since it's still under my 90 day warranty, i'm sending it back to lg to fix again. had to say i didn't do anything and it just died on my again (even though they replaced the motherboard). hopefully they'll just fix it without question.

if/when i get my working phone back i'd really like to root/twrp it, but i'm totally afraid of this method now. Is there an alternative to this or am i stuck on 46a w/ temp root? Is there a reason i can't just root w/ kingroot then install twrp using autorec? then install a new rom? why do i have to downgrade the partitions?

just don't want to screw this up again - so any help is appreciated!
[Verizon LG G3] roirraW "edor" ehT:
If you look through the thread, some people had the same experience. I've done this method twice, once each under 46A and 35B and it worked fine, so I could only speculate as to the cause of the issue, and not really willing to speculate. :)

Did you look at the screenshot of what the terminal emulator output should look like and compare before trying to boot into TWRP?

The #1 way I always recommend is the TOT method to flash 10B, using the .DLL from the 35B KDZ, then root using the Stump app and put TWRP on with TWRP Manager from the Play Store. Rooting after 10B and putting TWRP on after 12B is more difficult.

Getting into TWRP on any stock ROM past 12B on the VS985 requires downgrading your bootloader (aboot) to 12B (or 10B would work too). The 10B and 12B bootloader had a vulnerability allowing this, which 23C and higher don't have.

If you can see the phone in the Modem section of Device Manager, I'm sure you could use LG Flash Tool 2014 to flash a KDZ, or the TOT method I described above if somehow the Download partition (laf) didn't actually get downgraded. The black screen issue is common when for some partition mismatch issues which have happened to users. Even though the screen doesn't work, users are still able to access Download mode.

At worst, if the phone is listed as QHSUSB_BULK 9008 mode (either under Modem or Ports - I forget which section), then there's a different recovery method - I've done that too. If you have that, just Google for it to get the recovery directions.
[Verizon LG G3] hochoch:
thanks for the quick reply. i did not compare the terminal output, but it appeared that everything completed successfully. i read through all the forums about downgrading and this was the only one that specifically mentioned 46a, so i assumed it was the only option. i tried KDZ and tot several times and nothing worked. my screen did not turn on during download mode, it remained black, even though it showed up in device manager and vibrated when plugged in, so something definitely went wrong.

just so i'm 100% clear, when i get my phone back in 2-3 weeks.....i can just perform the standard 10B tot method? and use the dll labeled LGUP_8974.dll correct? i did try this and got errors. basically failed after 4%.
[Verizon LG G3] roirraW "edor" ehT:
The only option that will work on stock unrooted 35B and 46A is the TOT method with a newer .DLL which we extracted from the 35B KDZ. That's probably the right .DLL, but I don't know the filename off the top of my head, and the one from 35B could be the same filename as the old .DLL - I don't recall.

Basically there was a .DLL that we used to use with the TOT method but starting with stock 35B, we had to start using the .DLL that came inside the 35B KDZ in order to downgrade via TOT method to anything older than 35B. I have a copy of the .DLL in the same place as the KDZs and TOT in my section on Android File Host.

The 35B .DLL is also in the first post of [MENTION=4936949]hokiealumnus[/MENTION] ' thread that's about caution - warning don't take the 35B OTA. Originally he wrote it before a user in that thread discovered we could download using the newer .DLL.

Getting it to work correctly might require trying it on a different PC, different USB port, new Windows installation...who knows. It's worked for me on Windows 7, 8.x and 10.
[Verizon LG G3] hochoch:
cool - thanks very much for your help. i'll give this a go when the phone gets sent back to me, figure i better just start from scratch since it's free and i'm in no rush. Maybe you want to add a notice or warning to the top of the thread though? Or at maybe mention that this is an alternative to using the tot method?