yashsingh1/xdaforums huggingface dataset:
[LG V20 Questions & Answers] andrewjt19:
Well maybe you can offer some insight on how to do that instead of just criticizing. Pardon me if I'm reading that wrong but that's what your reply sounds like. This is the guide I used to go back to stock. Afterwards I tried to flash the stock recovery which failed or so I believe and then relocked the bootloader in fastboot mode. I still had a flag... How did your do it, if you will please.
[LG V20 Questions & Answers] ZDeuce2:
It's not a criticism, I removed root, in adb I did oem bootloader lock. It reset data, which in turn turned off developer options, resetting the oem unlock switch. Rebooted, and no security warning. I didn't bother flashing stock firmware, just unrooted, and relocked the bootloader in adb, That is all

Common sense isn't all that common

---------- Post added at 11:42 PM ---------- Previous post was at 11:35 PM ----------

Sorry you took my post as being critical, that wasn't my intention, I was just simply stating that I was able to remove the secure boot message, although T-Mobile didn't even check, I told them I had so ready backed everything to my SD card and reset. They just pulled the battery, sim, and SD card, stuck them in my new one, made sure my Google account loaded, and I walked out the door.

Common sense isn't all that common
[LG V20 Questions & Answers] andrewjt19:
Good to know. Although I tried those steps it still didn't take away the flag. But I suppose I did something wrong... Thanks for your input.

tApPeD fROM mY nExUs 6
[LG V20 Questions & Answers] dimm0k:
funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.
[LG V20 Questions & Answers] ZDeuce2:
I traded in my v10 still rooted, no question asked... And returned my first v20 for a blown speaker, it was rooted when I took it in, I did restored to to unrooted and looked the bootloader for the return, mainly to see if it fixed the speaker. But in all the years I've had T-Mobile, that is the first time I've returned a phone stock... No one has ever said anything about it.

Common sense isn't all that common
[LG V20 Questions & Answers] Nrod0784:
Yeah with sprint currently and I've returned rooted HTC 10, rooted note 4, rooted htc m8, and no questions ever.

Beastmode on my LG V20
[LG V20 Questions & Answers] Shadow Assassin:
Wow, thats funny. Im glad you had that luck. Idk that id be so lucky, but that made for good story.
[LG V20 Questions & Answers] whitedavidp:
I found a couple posts which were terse but sent me on the right path it seems. For others here is what I did:

1. Removed all of my accounts in the Settings.

2. Made sure USB debugging enabled.

3. Booted into download mode (hold volume down whilst inserting USB cable.

4. Fired up uppercut (being sure to disable A/V program first). Sees the device on a com port.

5. Loaded the 10p kdz, checked upgrade, and let her rip.

6. Device rebooted showing my apps and stuff. But no root any longer.

7. Factory reset the device.

8. Went through just enough of the setup to enable developer mode and USB debugging.

9. Note that OEM unlock is still on.

10. Did the following variation on what is shown in the first post of this thread <https://xdaforums.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258>:

* adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB

* adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE

* fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT

* fastboot getvar unlocked ----->THIS CONFIRMS THE BOOTLOADER HAS BEEN LOCKED

* fastboot oem lock---->THIS COMMAND WOULD LOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.

* fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN RE-LOCKED

fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE

11. Device now boots without warnings and into stock Android welcome screen.

BTW - when doing anything like this with a device I always recommend that (a) use USB 2 port, not later, and (b) be sure to use a USB port that is on the computer's motherboard.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gmillynn:
Hi,

I want to update my ROM from a standard WM5 to WM5SE rev 5.0. Following instructions, I downgraded with the button ROM to let me CID unlock my G3 Jammin. The butotn ROM installed, but when it reset it would not boot and both the red and blue lights would flash together, the screen would flash on, and then it would shut off.

This pattern is repeated every couple of second and doesn't stop until I pull the USB cable out, after which it repeats once more then switches off. I can't turn the phone back on with the power button. From here I can get back into the locked cycle by powering on with the USB cable plugged in (back into reset cycle), or into windows with the mains power cable (see below).

I think this means that the problem is related to my USB cable being plugged in. When I put the mains power cable in, the PDA will boot into windows. Related to this is what I think may be the main culprit. In setting, Windows says the battery is on 0%!!! Even the mains power cable doesn't seem to ever charge it, so I think it must be a software problem related to the ROM. Inceidentally, I recall that I had to softreset near the end of Button ROM's install, perhaps this is part of the problem...

Now I can reinsert the USB cable only during the Windows boot process, which as mentioned has to be initiated with the mains power cord, ie. I swap over half way through. If I change from mains power to USB after Windows has fully booted then the phone resets and the above reseting cycle occurs again.

Once Windows is fully booted with the USB cable in everything is stable and Activesync detects the phone. The problem is that when I try to reinstall a stable ROM, the update software throws the following error: Error [220] mains battery power. So the software I believe is reading that the battery is less than 50% (ie. probabaly thinks there is 0 charge left) and I can't reinstall a new ROM!!

The other thing to note is that I can get into bootloader mode with the mains power cable, but as soon as I try to switch over to the USB cable, the phone resets and it again gets locked into the perpetual reset cycle.

Please help me!! Any ideas are appreciated.

Gavin.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gmillynn:
Hi,

Found this: http://xdaforums.com/showpost.php?p=1216580&postcount=23

Seems like a similar problem. He solved it by replacing the battery. Is it possbile to destroy a battery while flashing a ROM?

G
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gmillynn:
Same problem again:

http://xdaforums.com/showthread.php?t=329953&highlight=battery+during+flash
[8125, K-JAM, P4300, MDA Vario Software Upgrading] gmillynn:
Wow 40 views, and not a single idea?

Well I think I'm going to invest in a cradle, so that I can have both mains power and a usb connection, hopefully I'll be able to reflash with this. Anyone have expereince with this method? What is a good cradle?
[LeEco Le 1S Questions & Answers] Shailesh1711:
Does LeEco Le 1s (x507) supports Magisk Root Method?
[LeEco Le 1S Questions & Answers] reversegear:
Not tried but it should support.
[LeEco Le 1S Questions & Answers] Shailesh1711:
I tried Magisk rooting on my device but it was showing as not rooted.
[Android] Bl4ck0verlord:
Universal Tool

Features:

Universal tool - tool for android ROM and kernel developers. It's like a android kitchen;

This tool written on C programming language

Work on dedicated working folder, that allows feel comfortable, when you working.

Unzipping ROM's (everyone. CyanogenMod based, AOSP Based, MiUI and etc...)

Deodexing apk's, if you have .odex, you can quickly get rid of it.

Decompiling and compiling apk's. This step very important, if you want add own features (some animation, colors etc.)

Unpacking boot.img and ramdisk. If you want look at "insides" of boot.img and edit some parameters, you need it.

Unpacking system.new.dat and system.img. When you meet ROM's with system.new.dat, you understand me ;) ROM Porters need it too.

Edit build.prop, updater-script.

Add apk of Kernel control.

Debloat ROM. If you have low RAM on device, you need delete some apps. Tool do it for you.

Installing apktool, adb, fastboot. You don't need use google, tool make it for you. Quickly.

Installing SuperSU.

Porting ROM's based on API 5.0 and higher.

Scrennies

Installing and run

For Linux

You must have installed libncurses5, python (2.7 or newer), JDK 1.7 or newer for working tool.

Press "Download", then extract .zip in your home folder;

Rename to Universal_Tool(if you download from GitHub)

Enter to Terminal and enter "cd Universal_Tool/", then "./tool". It's all.

Enjoy!

For Windows

You must have installed 7zip, JDK 1.7 or newer, Python 3.0, notepad++.

Download .zip

Extract to C:\ drive (IMPORTANT);

Rename to Universal_Tool(if you download from GitHub);

Run from tool.exe

Downloads: View attachment 3999885, View attachment 3999887

Sources: https://github.com/AL3X1/Universal_Tool​

Changelog

11.01.17 - v.1.1

Added Fastboot Menu

Added Porting tools

Fixed apktool problem on linux version

Fixed some error's.

Added information about using tool (manual).

* Tool Written by 4L3X (Bl4ck0verlord on xda, Grand_leMon on 4pda)

* Thanks to:

* iBotPeaches - for ApkTool

* JesusFreke - for smali/baksmali

* xpirt - for sdat2img

* osm0sis - for mkbootimg

* Willi Ye - for Kernel Adiutor

* Chainfire - for SuperSU

* Neko.cpp and lolmaxlik - for helping with some questions

* You

* and...

* I am a modest man, but if you want, you can say 'thank you' to me too. :p
[Android] xtremelora:
It seems awesome, I will give ot a spin later.

Thank you man for this tool, you make our developers/designers life easier.
[Android] Bimalhort:
How to extract rom.zip
[Android] Hamidreza2010:
[MENTION=6605620]Bl4ck0verlord[/MENTION] ahhaaa its great bro

its very nice we see a kitchen which work on windows.

hope this kitchen supported sony devices and we can make rom ( 6.0.1 or 7.0 ) for our device

thanks bro
[Android] Bl4ck0verlord:
First: create workspace

Second: place archive with your ROM to workspace folder.

Done ;)
[Android] Zorbeyd:
[IMG="error"]http://i.hizliresim.com/VP1b9P.jpg[/IMG]

I'm not using that tool on Windows 10 x64

Error says : System can not find specified path
[Android] Bl4ck0verlord:
Replace tool in C drive. Then rename to Universal_Tool and launch.
[Android] pendor24:
Hello

We can not extract the img system.

Ca plant every time (android7)
[Android] omnikam:
Really nice tool :) just needs to be able to recompile system.img. keep up the good work
[Android] Hamidreza2010:
+ 1
[Android] gaurmega:
Hi, thanks for the tool. I want add spanish language to miui 8 china developer rom but i don't know how. Is possible with this tool?
[Android] Crachketo:
Hi
[Android] tftech:
Good Tool

Really good Tool but can u give me little bit guide for using it:)

Thank you
[Android] Kaiyum:
Not on my pc for a while but next weekend... Are binaries updated? Smali, su, oat2odex etc? Or can we update them?
[Android] Rubancv:
Rcv

Good work....
[Android] mchlbenner:
?

I keep getting this- the directory name invalid.
[Android] dvdaio:
i got this error while trying extract boot.img

What you want?: 3

1 file(s) copied.

The directory name is invalid.

boot.img ready. Press 'Enter'to continue.
[Samsung Galaxy Star] LehKeda:
WARNING : MESSING WITH KERNEL AND RECOVERY PARTITIONS IS VERY DANGEROUS FOLLOW THIS GUIDE AT YOUR OWN RISK

​

In this guide you will learn how to increase the size of kernel and recovery partitions. the method should work for other samsung devices.

So it will be something like that .....

Before

After

​

The way we are going to increase the size of the partitions is to repartition the partition so first you must read this guide here and understand it well as we will need it .

Steps to do this are :

Repartition device memory.

Edit pit file for the device.

BEFORE DOING ANYTHING YOU SHOULD TAKE BACKUP OF THE PARTITION WE WILL WORK ON

​

First we will start with kernel partition and please don't touch recovery partition until you make sure that you have done all the steps correctly and your system is working then go for recovery partition

​

Tools will be used :

Parted : Here .

PIT editor : Here .

This method can work if you want to repartition any other partitions like data or whatever you want .

If you find anything wrong, typo, broken links or even flying elephant please let me know. :D

One last thing if you did like this guide or you didn't you can push that thanks button :D
[Samsung Galaxy Star] LehKeda:
Edit PIT file .

Edit PIT

​

After you repartition kernel/recovery partition you will have to edit pit file to finish up working and make new partitions useable and make your phone work .

There is some points I should clear out first .

What is PIT file ?

It is a file contains a lot of informations about all partitions in your phone .

What is PIT used for ?

This file is used by device bootloader to know where is kernel/recovery partition to load it .

Heimdall and ODIN , they use this file to know what goes where so they know where to put kernel,recovery,system,modem and everything else .

What I'll edit in PIT file ?

You will have to edit all information for partitions you have changed them .

Let's get started :

Get pit file for your device . How ?

from parted type print and look for the partition with contains pit file . for me the file is in partition number 26 .

​

Copy that pit file to your sdcard or external card .

open another terminal/console then type "adb shell" then the copy command "dd if=/dev/block/block_that_contains_pit of=where_ever_you_want_to_put_pit_in/any_name.pit"

so for me I'll type "dd if=/dev/block/mmcblk0p26 of=/sdcard/mint.pit"

Pull pit file from the phone through this command . "adb pull /sdcard/mint.pit"

Open pit editor and choose "PIT file analysis" then open your pit file .

​

Click on "Copy to clipboard" and paste in any new text file as you will need some of those information later in case you messed anything up .

Now go to "PIT file editor tab" and open your PIT file.

PIT entry list choose the entries you will edit .

if you have edited system and kernel partitions so you will need to modify 2 entries ,but which two ?

let's say that system partition number is 15 and kernel is 9 so you will edit entries number 15 & 9 .

For my I'll edit entries number 5 and 21 .

You only will edit two values "Block size " and "Block Count" .

​

In "Block size" you will enter start sector of your block . and in "Block count" you will enter the size of your partition in sectors .

To get those values open new terminal/console then type "adb shell" then "/sdcard/parted /dev/block/mmcblk0" or "/sdcard/parted /dev/mmcblk0" then "unit s" then "print"

So for my system partition : block size = 1,252,864 and block count = 1,781,760

and for my kernel partition : block size = 3,034,624 and block count = 53,248

Then hit save and go to "PIT file analysis" then open your pit file . and make sure that your changes have been saved .

Now push that PIT file to your device storage and copy it back to it's own partition "adb push pit_name.pit /sdcard/mint.pit" but for you should copy it back with it's original name. to find it go to "PIT file editor " and select the entry number for pit partition . it will be the same as your pit partition number so for me my partition number is 26 so I'll select entry number 26 . then look at "Flash file name" . so for me my pit file name is mint.pit

​

Now copy pit file back to its partition "dd if=/sdcard/mint.pit of=/dev/block/mmcblk0p26"

Finally I'll restore kernel and system and reboot and see if the system boots or not .
[Samsung Galaxy Star] LehKeda:
For devs:If you've changed partitions sizes (cut space of them) and you're going to port a ROM or build on from source, make sure to change partitions size in BoardConfing.mk or them ROM won't boot and you'll need to reformat the partitions again. After you finished working and the ROM is stable enough to release or you just want to publish it for testing purpose make sure that you rebuild ROM with the original partitions sizes again.
[Samsung Galaxy Star] LehKeda:
Oh He left me :(
[Samsung Galaxy Star] LehKeda:
Cool I'll ask for divorce :cool: :cool: :cool:
[Samsung Galaxy Star] LehKeda:
one more for the future (Maybe)
[Oppo F1s Questions & Answers] zidanovic:
i have a broblem with oppo f1s

while running vr apps or videos , the screen keep shaking without any move from me

I think gyro sensor need to calibration but I don't know how

my phone with the latest update

please help me
[Oppo F1s Questions & Answers] Ananaqil12:
I have same problem too
[Oppo F1s Questions & Answers] zidanovic:
I found a solution on oppo forums

downgrade ur version to A1601EX_11_A.19_161011. Here u can found that version ~> www.oppo.com/my/downloads/ download ur firmware and flash it on recovery or you can just open it from files app on your phone and select update .

Latest version will make ur gyroscope/vr super shaky.
[Oppo F1s Questions & Answers] Ananaqil12:
Thanks a lot
[Oppo F1s Questions & Answers] dharmam715@gmail.com:
How can go to my previous version in oppo f1s
[XDA Assist] Duke55555:
So i wanted to unbrick some old i9300 but odin recognize him and doesnt want to install ROM on it.I even tried different version,new drivers,different roms,everything.It just says failure.

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PDA_XWJSD_Sbl.tar.md5 is valid.

<OSM> PHONE_XXJPY.tar.md5 is valid.

<OSM> CSC_OXXJS6.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> All threads completed. (succeed 0 / failed 0)

It doesnt want to work,can someone help me?
[XDA Assist] sawdoctor:
Greetings and welcome to assit. Have you tried a different version of odin and does kies recognise your phone ? Other than that all i can suggest is asking your question here

http://xdaforums.com/galaxy-s-i9000/help

Good Luck

Sawdoctor
[XDA Assist] Duke55555:
Yes i did,sorry for delay
[Nexus 6P Q&A, Help & Troubleshooting] GatorsUF:
What is the easiest way to get the official 7.1.1 release? I'm bootloader locked so not sure how to sideload IMG files without fastboot etc...

Why isn't there just an update from beta to stock?
[Nexus 6P Q&A, Help & Troubleshooting] x99percent:
Download the 7.1.1 OTA .zip to your computer, and adb sideload it through the stock recovery menu.
[Nexus 6P Q&A, Help & Troubleshooting] tzmueller:
I tired this and get the error "can't install package over newer package". I verified I downloaded the correct OTA for the 6p but it says the build date is earlier than the beta install of 7.1.1

thoughts?

---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------

update seems you can not update from beta 7.1.1 to release 7.1.1 using OTA yet. :(

I think I am going to wipe and start over.

This Android 7.1.1 release includes the December security fixes. The new build number is NMF26O for the Pixel and Pixel XL, NMF26H for the Pixel C, NMF26F for the Nexus 6P, Nexus 5X, and Nexus 9, and NMF26J for the Nexus Player. Oddly, this build is an older version than what rolled out as the final Android 7.1.1 Developer Preview last month, so if you're running that you won't be able to upgrade just yet. We assume Google will release different builds for those who are enrolled in the Android Beta program. When they're coming is anyone's guess, though.
[Nexus 6P Q&A, Help & Troubleshooting] mojorisin7178:
Oh that is why. I ran into the same problem. I thought I might be doing something wrong. So has anyone in the dp program gotten the update yet? I usually get the update immediately. But not this time
[Nexus 6P Q&A, Help & Troubleshooting] tzmueller:
Google has not released the OTA update from beta 7.1.1 to stock 7.1.1 yet and nobody knows when and if this might happen.
[Nexus 6P Q&A, Help & Troubleshooting] boxguy1:
Nexus Toolkit

Use this will guide you it does everything like bootloader unlock this will update to 7.1.1 stock

https://www.androidfilehost.com/?fid=24728673521238129
[Nexus 6P Q&A, Help & Troubleshooting] irononreverse:
I updated to nmf26f and now my Nexus 6p says it's a pixel XL. What's going on?
[Nexus 6P Q&A, Help & Troubleshooting] tzmueller:
wrong update?
[Nexus 6P Q&A, Help & Troubleshooting] mojorisin7178:
It wouldn't be wrong date it would be wrong device build. But it shouldn't work if that were the case.

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

As far as I know the only way to get stable 7.1.1 is to unenrolled in the dp program. Then sideload the OTA. But if you unenroll I think you should get an OTA that downgrades you to 7.0 stable first then another for 7.11 stable.
[Nexus 6P Q&A, Help & Troubleshooting] boxguy1:
You probably installed the pixel mod
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] ssconceptz:
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?

I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.

I also don't want to pay an arm and a leg for the firmware.

Any help is appreciated!
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] ssconceptz:
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?

View attachment 3969966

Any help would be great.
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] ozyk100:
Did you try emergency recovery with smart switch?
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] Лithium-Фusion:
What's the version that you've got by ota? Just flash that version(must be latest in case), try to boot if it doesnt; boot into stock recovery; wipe cache/dalvik, factory reset(I dont remember which options were there). The fact is; bootloaders of latest firmwares are lock up which means you can't downgrade even previous one you've been using. Custom roms would helpful to get rid of that bootloop but don't know if its available for Verizon devices. Good luck.
[Xposed General] aycl64:
Hİ!

I creating android 7.1 my s3 i9300.

You are read xposed for android 7.1 (i9300) link please

Edit: I'm not English or American.

Edit2: I'm don't speak english.

Edit3: Okulda bu kadar İngilizce öğrettiler bana.

EDİT4: PLEASE HELP ME
[Xposed General] Deleted member 5226518:
wow
[Xposed General] Didgeridoohan:
I'm sorry, but the required language on xda is English. Also, there's no Xposed for Android 7 yet. Keep an eye on this forum and you'll know when it's released.
[Xposed General] aycl64:
I low understand you and thank you!

I undrestanded "Xposed for Android 7 yet." :))
[Xposed General] kyle4269:
http://xdaforums.com/showthread.php?p=69488059
[Xposed General] Dirk64:
Write in English!