yashsingh1/xdaforums huggingface dataset:
[One (M8) General] sterphles:
The phone was stock when I made the TWRP backup - I haven't had any luck restoring from that. I've mostly found a bunch of dead links (Not surprised since it's from like 2014) and I was only able to find a zip under "ATT_1.58_STOCK_ROOTED_DEODEXED.zip" which did not work when I tried to install.

Some other info I've found out trying to mess with this recently - I do have adb access to the phone when I get it to the HBOOT screen but I'm not sure what to do with that. When I go into TWRP I keep getting an error unable to mount /carrier, but when I try to install Lineage or do my backup it skips over the error and seems to complete without an issue, so I kept disregarding that. I found something suggesting a fix by switching to ext2 and back to ext4 but I can't find any way at all to get /carrier to mount and TWRP doesn't seem to be able to access it at all. Does that mean I haven't finished rooting the phone? I was able to follow the first 95% of this guide pretty flawlessly so I believe I'm in the right spot but I just can't figure it out.
[One (M8) General] murphylim:
I did upgrade lineage to version 19, thank you. I had encountered window does't recognise my phone initially,then I change the cable, pc find the device and install driver immediately.
[One (M8) General] djibe89:
Hi.

I'm afraid I can't help you for that weird problem.
[One (M8) General] sterphles:
I appreciate all the help so far, leave it to me to have a unique issue here. I was able to finally get it back to stock with my backup by dropping down to an old version of TWRP Recovery (2.8.1.0) but that errored out trying to install Lineage. Was able to get back to stock, start over and I actually was able to go back to TWRP 3.6 or something (the one you have in this guide) and Lineage 19.1 finally booted after around 5-6 hours on the boot screen! Everything worked as I can tell except for WiFi, any network I try shows it can't connect to the internet but it shows as a connected device on my router. Figured maybe a reboot would clear things up and now I'm stuck on the boot screen again going on about 12 hours.

So basically even if I do get this working it's probably not a permanent solution if my reboots take hours to days. I'm definitely learning a lot more about what I'm doing here beyond just following the instructions that you wrote so I think I have enough now to play around with some older versions of Lineage and see if that might help. It was a tick slow when I had it up and running but it seemed about what I'd expect for older hardware running Android 12 - the hours and hours for reboots on the other hand, not what I'd expect.
[One (M8) General] djibe89:
Hi, can you try Android 10 or 11 instead ?
[One (M8) General] sterphles:
Finally figured it out! Tried dropping to Android 11 like you suggested and it errored out saying it needed the 3.19 bootloader and I was on 3.16. Took me a few hours to figure out how to upgrade the firmware (had to re-lock and then unlock again) but everything finally works, I was actually able to get Lineage 19.1 + Magisk + Mind the GApps to work on the first try. A little nervous since the first boot took 5+ hours but I'm just so happy to have sorted this, and I feel like I learned quite a bit in the process.
[One (M8) General] Cedar Mill:
I get error 255 when ever attempting to back up the stock system ROM to the SD card. What am I doing wrong?
[One (M8) General] djibe89:
Hi, no idea. Try https://xdarom.com/twrp-error-255/
[One (M8) General] sHaDi3sT:
How can I flash twrp on a bricked HTC one m8?
[One (M8) General] Cedar Mill:
I found a solution, back up to /sdcard (the emulated SD card), then copy to the real SD card. For some reason, TWRP will always get error 255 when backing up directly to the real SD card.
[One (M8) General] djibe89:
Tutorial updated for Android 13
[One (M8) General] willoski:
i have an issue it also applied to stock, the phone will time out and when you turn it back on to lock screen it is just a black screen everything works and the screen lights up black. the screen is broken and i am ordering a new one but what exactly is the issue?
[AT&T Galaxy Note 3 General] mezacorleehone:
Hello colleagues

a couple of hours ago I got my N900a

A while ago I got an N900v (which was a blast)

this N900a is a headache,

when they gave it to me (N900a), the touch buttons didn't work or they worked erratically.

I decided to downgrade it to 4.4.2 but surprise, here the buttons are recognized normally, the problem is when I go back to lollipop
[OnePlus 3 Questions & Answers] philipemad:
I'm running a completely stock OP3T with stock recovery and locked bootloader and latest OOS 9.0.6 installed.

Lately the phone has been unbearable to me and keeps hanging a lot with random crashes so im thinking about downgrading to OOS 4.1.7 as it is more stable. (I prefer OOS over custom roms to maintain stability and keep all the phone features intact).

I've downloaded OOS 4.1.7 from [oneplusupdates dot com] (cant post links cause im still new)

My question is : can I use the built in software update to locally select this file and preform the downgrade directly from pie to nougat?

I read somewhere that this could brick the device so i wanted to make sure.
[OnePlus 3 Questions & Answers] TNSMANI:
Yes, that would surely brick the device. There are other steps involved before and while downgrading. Search on XDA for the steps.

The simplest solution to your problem is to download the current (9.06) OOS ROM and clean install/sideloading it. Your problem is most likely because of OTAs and not because of 9.06
[OnePlus 3 Questions & Answers] henk717:
The phone has replaced your bootloader to the point old roms are no longer compatible. Finding the correct zips and flashing order to downgrade the bootloader is a route i would not advise either. The easiest way to downgrade is find the msmdownloadtool unbrick thread of your specific model and download the version you desire or lower. Use this tool to flash the included files in upgrade mode and you will be on a stock, locked bootloader with the version you chose to download. Flashing always carries a risk, but i had no issues downgrading this way while i did run into issues flashing old zips. I switch between 5.0.8 based roms and the latest roms and its never let me down.
[LG V20 Questions & Answers] X_BlackBurn_X:
UPDATE:

I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.

xposed framework take you in bootloop for this device.

now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.

if in future anyone feels any problem i am always here.

remember: linus is your friend for this device, and windows 10 suck.

and

sudo $(which fastboot) did miracles for me....

old post:

Hello everyone.

i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.

model number:

LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.

we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "

cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.

THE ERROR:

<WAITING FOR DEVICE> till eternity.

what i have done till now ?

1. lg drivers installed.

2. adb drivers installed with adb fastboot files.

3. updating legacy android adb interface driver, done.

4. went in to boot loader then connected the data cable and updated driver, done.

5. usb debugging oem unlock options activated, done.

6. restarted pc multiple times to update drivers, done.

we all know all it takes is 3 easy commands to unlock bootlaoder

adb reboot bootloader

fastboot oem unlock

fastboot reboot

but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.

then i ran command, adb devices>> it shows

List of devices attached

adb server is out of date. killing...

* daemon started successfully *

LGH9182bfc6bdc device

next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>

so this is for sure that my device is not connected to the fastboot.

now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.

any help will be appreciated.

regards.
[LG V20 Questions & Answers] clsA:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app

[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
[LG V20 Questions & Answers] X_BlackBurn_X:
Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you
[LG V20 Questions & Answers] X_BlackBurn_X:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
[LG V20 Questions & Answers] C D:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
[LG V20 Questions & Answers] X_BlackBurn_X:
Thanks for the reply.

Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.

Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.

I hope you understand my pain.

I just want to unlock my bootloader thats it.

It used only 3 commands.

1. Adb devices - shows my device.

2. Fastboot devices - no fastboot device found.

This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.

I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
[LG V20 Questions & Answers] clsA:
fastboot doesn't work when the phone is booted up

adb reboot bootloader

followed by fastboot devices

Note: flashing the 10p kdz does not require the bootloader be unlocked

it requires you have patched LGUP

Example:
[LG V20 Questions & Answers] C D:
As clsA said, flashing firmware does not require an unlocked bootloader.

Look at parts 1 and 2 of the other step by step guide here:

https://xdaforums.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
[LG V20 Questions & Answers] X_BlackBurn_X:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.

Solution : flashing the 10p kdz does not require the bootloader be unlocked

it requires you have patched LGUP.

I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
[LG V20 Questions & Answers] clsA:
No problem the link [MENTION=7601382]C D[/MENTION] posted above seems to have all the working links for you
[LG V20 Questions & Answers] X_BlackBurn_X:
well we have a new problem now.

lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.

did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.

used the provided kdz file flashing as an upgrade.
[LG V20 Questions & Answers] X_BlackBurn_X:
ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h

and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....

i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.
[LG V20 Questions & Answers] X_BlackBurn_X:
UPDATE:

i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.

now i am on h91810p software version andriod 7.

problem UPDATE:

i still cant unlock bootloader. same problem as before downgrading from h91820h.

adb devices shows device.

adb reboot bootloader

fastboot devices gives no result.

phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.

kindly help guys :)
[LG V20 Questions & Answers] X_BlackBurn_X:
hello clsA

"

D:\fastboot>adb devices

List of devices attached

LGUS99740047103 device

D:\fastboot>adb reboot bootloader

D:\fastboot>fastboot oem device-id

after this it only says waitng for device"

now i am on h91810p as i was instructed. can you please help.

its all happening the same way it was happening when was on h91820h.

fastboot devices cannot be found.

once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.

kindly help.
[LG V20 Questions & Answers] X_BlackBurn_X:
NEW UPDATE:

my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.

possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
[LG V20 Questions & Answers] C D:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
[LG V20 Questions & Answers] X_BlackBurn_X:
hello

thanks for the reply.

i know we cannot flash any other phones firmware on to this model.

i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.

cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.

i have seen people doing on t mobile on youtube videos i dont know how they are doing it.

my problem is :

" as in message sent to various senior on this topic"

LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED

HELLO

can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,

adb devices shows my device

|but fastboot devices in bootloader mode doesnot show my device at all.

updated all the drivers used multiple pcs usb ports but no luck at all.,

what am i possibly doing wrong can you please help me out? i will be thankful to you.

on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,

regards
[LG V20 Questions & Answers] clsA:
Did you make the Linux USB boot stick

Are you following the guide at all?

PART 3: CREATING A BOOTABLE LINUX USB USING FWUL

DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.

https://androidfilehost.com/?w=files&flid=214529

DOWNLOAD RUFUS FROM BELOW AND INSTALL

https://rufus.akeo.ie/

INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.

INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)

NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED

THIS WOULD MAKE YOUR PC RUN LINUX OS

TYPE PASSWORD AS linux AND ENTER
[LG V20 Questions & Answers] X_BlackBurn_X:
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.

i will go through your links and try to study this.

just one more question.

does this method unlocks the bootloader ?

if yes please reply yes i will be thankful to you.

i will follow this step now.

regards
[LG V20 Questions & Answers] cnjax:
Why does adb show your device as a 997 which is the Sprint variant
[LG V20 Questions & Answers] X_BlackBurn_X:
to be precise i am still stuck on

PART 2: UNLOCKING BOOTLOADER

my bootloader is not getting unlocked for some reason.
[LG V20 Questions & Answers] X_BlackBurn_X:
hi

dont bother about 997 it was just an exmaple to show on which command i am atill stuck

its lg h91810p and let me just put what it shows exactly.

this is what i see:

C:\adb>adb devices

List of devices attached

LGH9182bfc6bdc device

and this happens in bootloader mode:

C:\adb>fastboot devices

C:\adb>

that means fastboot device not found.

to my surprise i am not only alone in this, i have been going through many threads some 2 to 3 years back and there are many like me who are facing the same problem.,

some of them tried multiple PC and usb ports like me and stilll no luck. one of them even tried MAC and still the same result.

so my problem is i cant unlock the bootlaoder.,
[LG V20 Questions & Answers] clsA:
The point to using the USB stick is it doesn't rely on windows drivers for fastboot to see your device.

Use the USB method to boot your PC

Then the fastboot commands will work

Your problem actually is your PC is not loading the fastboot driver. It's easy to solve with the Linux boot stick.
[LG V20 Questions & Answers] X_BlackBurn_X:
finally bootloader unlocked

hello clsA

thanks for all the efforts people has done for this. finally i have unlocked the bootloader. yes it was windows 10 which has this problem. i made a usb unbuntu drive and typed commands over there but it was behaving same.

1. i installed the drivers

2. same commands of fastboot devices still no response.

3. the solution: then i typed

sudo $(which fastboot) devices

and it showed my device in fastboot mode for the first time since 3 days.

then i typed

sudo $(which fastboot) oem unlock

gave an error that it failed but it actually unlocked

then i typed

sudo $(which fastboot) getvar unlocked

and their it was unlocked: yes

then rebooted and everything seems fine now, so finally i am done with the 1st step unlokcing the bootloader.

next steps: twrc, supersu rooting, mk2000 kernel, superv20 rom.
[LG V20 Questions & Answers] dikkbutt:
EDIT:

everything done/works allright. see the complete guide:

https://xdaforums.com/v20/how-to/lg-v20-h918-t-mobile-guide-box-20h-twrp-t4193991

_____________________________________________________________________________

hey there, yes, you have not been the only one with EXACT the same problem. like you, i did everything my humble android knowledge gave away. no success. i reinstalled win10, newer version, tried all usb-ports, different usb-c cables, netbook, laptop, different versions of adb and lgup and lg usb drivers. no chance. h918 t-mobile branded was always recognized correctly in win-10 system, no probs whatsoever, but: when i adb reboot bootloader, no chance, phone got stuck, no command worked, always: waiting for any device forever. im stuck on this for days, many hours looking around, reading reading reading. i hope with this thread i found a solution. i will get back later and post a detailed manual in case i can solve this problem and unlock the bootloader on my v20 h918 20H.

thx to everyone for helping guys like me, without you, i would be using an unrooted phone :(

u helped me out bigtime 4y ago with my V10 !
[LG V20 Questions & Answers] VelosterM14:
This kind of thing is why the people who wrote those guides for the H918 years ago were very specific that they would not help if you weren't explicitly following their directions, including using FWUL.

So you can avoid wasting time.
[Magisk] Velocity_9:
My phone is a Redmi 6a, Android version 9, MIUI 10.4.4

I have rooted my phone with Twrp and have the latest version of Magisk, and bootloader in unlocked.

Whenever i try to run smali patcher this error occurs.

fOmey @ XDA

Patcher version: 0.0.6.7

==> Detected java: 1.8.0_251

==> Dumped framework

==> Processing framework

[INFO] Processing 1 file(s) from bin\services.vdex

[INFO] 1 out of 1 Vdex files have been processed

==> Extracting classes.cdex

!!! ERROR: Failed extracting classes.cdex

I have-

1) Run smali patcher as administrator

2)Installed latest java update and net framework

3)have the latest drivers for my phone

Things i have also tried which don't work

run smali patcher with my phone in recovery mode where it shows error "no ADB devices found"

so /system mounted doesn't really do anything if my PC can't recognize my phone

i have turned on file transfer which works normally

i just don't know what to do. :(
[Magisk] Bagusherma:
maybe change ur rom/cusrom, cmiiw
[Samsung Galaxy Note 9 Questions & Answers] haircut123:
I noticed my theme store is a service version what does that mean is this normal as I've never seen it say service version before
[Samsung Galaxy Note 9 Questions & Answers] koragg97:
This is mine so i guess it's normal, never really checked before.
[Samsung Galaxy Note 9 Questions & Answers] haircut123:
Thanks dude I guess it is :)