yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] stealtheye:
Yip very odd. But it continued to vaguely work. I just couldn't deal with the ROM overall. WiFi bugs, YouTube bugs, worse battery life... So I chucked the shocking attempt of an update lenovo have us and went back to good old trusty cm12.1. I mean CM12.1 is technically beta software but runs rings around the official stock 5.1. I say lenovo because it's not moto anymore. Lenovo have ruined moto. They want to limit moto software testing budget and restrain them and control them, I'm gonna say cheers. Can't believe the shocking quality from a former brilliant company. They were on their way up with Google. Now I'm never buying a moto or lenovo again. Nexus or iPhone.
[ONE Q&A, Help & Troubleshooting] Bobbi lim:
Are you able to enter fastboot mode now?
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
[ONE Q&A, Help & Troubleshooting] Bobbi lim:
Have you tried "fastboot oem unlock" in fastboot mode?
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.

When i try to flash twrp it just fails because my bootloader is locked.
[ONE Q&A, Help & Troubleshooting] Bobbi lim:
Which stock recovery is it? ColorOS? CM? Or OxygenOS?

I had a similar issue when I tried to unlock mine when I first got my OPO
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Can you tell us the exact copy/paste and output of below command :

fastboot oem device-info

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
I've got the following:

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.

C:\Windows\System32>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ -0.000s]

finished. total time: -0.000s

C:\Windows\System32>
[ONE Q&A, Help & Troubleshooting] GirishSharma:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
Then i've got the following:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices

866878f3 fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock

...

OKAY [ 10.112s]

finished. total time: 10.114s

C:\Program Files (x86)\Minimal ADB and Fastboot>

And when i do the command: "fastboot oem device-info" again.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.010s]

finished. total time: 0.011s

C:\Program Files (x86)\Minimal ADB and Fastboot>
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.

Anyway, thanks for the help and all the effort you did!
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.

So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).

And there are two tools (which have both the same base) here and here .

Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.

And yes, I gave it administrator rights and the drivers are properly installed.

I tried it also on windows xp (completly clean test computer, yes I have a lot of them :) )

Now I saw on the oneplus forum a post .

And when I tried the command "fastboot erase bootloader" it gave me the following output:

C:\Windows\System32>fastboot erase bootloader

erasing 'bootloader'...

FAILED (remote: Partition table doesn't exist

)

finished. total time: 0.006s

Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.

Well might this then work, so that the device after flashing the first file doesn't shutdown?

Again I just want to mention it here before I make the situation more worse then it already is.
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).

After waiting very unpationtly -+ 24 hours I tried it.

Sadly enough again without success.

CMD copy:

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.

C:\Windows\System32>fastboot devices

866878f3 fastboot

C:\Windows\System32>fastboot erase boot

erasing 'boot'...

FAILED (remote: failed to erase partition

)

finished. total time: 5.057s

C:\Windows\System32>
[ONE Q&A, Help & Troubleshooting] ambervals6:
Fried emmc. Sell it for junk.

Sent from my SM-G920T
[ONE Q&A, Help & Troubleshooting] Deep.G:
Hi,

I am stuck with a similar issue. Only the way I landed in this situation is slightly different.

Without unlocking the bootloader (I just forgot to do that!), I ran the below command.

fastboot format cache

It erased the cache but failed to write to it because the device is still locked.

On rebooting, the device was stuck overnight on the "Cyanogen" display screen.

I forcibly powered it off using the power button.

Then I fastbooted it.

Then from the command prompt I tried to run a few commands - see output below

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s

And then this -

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.

default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

and this -

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...

That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.

Any way out?

Thanks,

Deepak Gupta
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".

Also sometimes when you type a commando that isn't recognised by the phone it can take forever.

So, I think that the commando "fastboot flashing unlock" doesn't exist.

Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.
[ONE Q&A, Help & Troubleshooting] Deep.G:
Well, just before you replied, I accidentally figured out the command typing mistake from one of the google search results. Nevertheless thanks for the help! I know how harrowing the past 3 hours have been for me (Was scared of irrevocably bricking my OPO!!)

"fastboot oem unlock" worked.

Also, the reason I tried "fastboot flashing unlock" was because "fastboot help" told me that such a command exists and does exactly what you would expect it to do - unlock all partitions except bootloader related. Nonetheless, I have no idea why it did not work. But I got my OPO back :)
[ONE Q&A, Help & Troubleshooting] ninjawulf98:
I didn't look the last time to this thread, so sorry for that.

But it seems that you were right. I just wanted to make sure that it had indeed a fried emmc.

So thanks for the help to everybody.
[G Pad 8.3 Original Android Development] AndroidUser00110001:
Install Instructions:

You will need root.

With custom recovery already installed.

Download

Place zip file on phone

Reboot into recovery

Flash zip file through recovery

Reboot

With stock recovery - Need ADB installed.

Download zip file

Extract recovery.zip to your device's SD Card, not external but internal memory.

Open terminal window/command prompt to execute following commands

adb shell

su

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

exit

exit

adb reboot recovery

You should be in your updated recovery now

Download:

Download HERE

Sources:

My GitHub

Credits:

[MENTION=912474]Dees_Troy[/MENTION]

TeamWin

Everyone involved with TWRP.
[G Pad 8.3 Original Android Development] fefifofum:
I see you used v500 repos as a base for this. If you want, I could try to make it official so we have the three variants of LG G Pad 8.3 supported on the same place: https://twrp.me/devices/lggpad83.html

EDIT: Where does the prebuilt kernel in your sources come from? LG official lollipop rom (35A)?
[G Pad 8.3 Original Android Development] AndroidUser00110001:
Sure, make it official. Thanks!

Yes the kernel came from the 35A stock ROM.

Trying to get TWRP to work on 5.0.2 but having some issues with the boot chain. Looks like LG changed something...
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
Thanks [MENTION=4218641]AndroidUser00110001[/MENTION]! Just wanted to report that it works 100% on a backup and restore of the stock 5.0.2 (with the known caveat of having to flash the old aboot to get into TWRP and then reflash the 5.0.2 aboot to get back into the ROM).
[G Pad 8.3 Original Android Development] AndroidUser00110001:
Thanks! Ran into that issue myself and was like WTF?

We had similar issues on the G2 going from JB to KK. Time permitting I am going to look into a solution so we don't have to do the aboot trick.
[G Pad 8.3 Original Android Development] fefifofum:
Well, it seems [MENTION=2385005]invisiblek[/MENTION] already submitted a device repo to build twrp for the vk810, so I won't be taking care of that model. Now it's up to him to get official twrp support for the vk810 (or let someone else do it).
[G Pad 8.3 Original Android Development] AndroidUser00110001:
Yeah...I believe his works with CM sources by replacing the bootable folder with Omni sources. I am too OCD at times so kept it simple to just Omni sources...
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
Sorry, when I had read about making it official, this was the first thing I thought of, from Thumb Wars:

https://www.youtube.com/watch?v=R1NEKS4nfmk
[G Pad 8.3 Original Android Development] AndroidUser00110001:
I ain't kissing anyone

...unless it is a hot chick to make it official ;)
[G Pad 8.3 Original Android Development] sporty377:
Do i need to do the aboot trick or can i just flash?
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
If you don't already have the 4.2.2 aboot on your VK810, then yes you need it. If you already put TWRP on your tablet and it's working now, then you can just flash the new TWRP zip file from your old TWRP, then choose "Reboot Recovery" in TWRP to get into the new one.
[G Pad 8.3 Original Android Development] stbxxl:
<deleted>
[G Pad 8.3 Original Android Development] 4218kris:
dang i could have sworn i had twrp recovery on my vk810 still so i flashed the 4.2.2 aboot to upgrade to this newer twrp then i rebooted it just went to fastboot so i tried to adb the 35a aboot so it would boot but my pc win10 adb says no device iv installed the drivers.. what in the world damn it..
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
You installed the Verizon specific LG drivers?

Try rebooting the PC? Using the original USB cable with a USB 2.0 (not 3.0) port? In Device Manager, is your VK810 listed? If it's not listed, that's the problem. It can take up to 10 minutes to load the driver you installed the first time you plug the tablet into a different USB 2.0 port on the PC, or on a new Windows installation.

Until you can see it in Device Manager, you won't be able to talk to it via ADB.

Good luck!
[G Pad 8.3 Original Android Development] msaiducar:
Hi,

I tried to do what you said in instruction but I have an error. I exctracter META-INF folder and recovery.img file to my sdcard root.

This is the error:

-------------------------------

Secure booting Error!

Cause: boot certification verify

---------------------------------

These are the terminal output of my commands (your commands actually :P)

mjollnir@mjollnir-thor:~$ adb devices
List of devices attached
VK8104G509288a0	device

mjollnir@mjollnir-thor:~$ adb shell
shell@altev:/ $ su
root@altev:/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recov>
dd: /dev/block/platform/msm_sdcc.1/by-name/recovery: No space left on device
49153+0 records in
49152+0 records out
25165824 bytes transferred in 3.383 secs (7438907 bytes/sec)
1|root@altev:/ # dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/>
25332+1 records in
25332+1 records out
12970000 bytes transferred in 2.560 secs (5066406 bytes/sec)
root@altev:/ # exit
shell@altev:/ $ exit
mjollnir@mjollnir-thor:~$ adb reboot recovery
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
Look at my stickied thread in the General section (also linked in my signature below).

You have to downgrade your bootloader to 4.2.2 first and use the loki hack to install the initial version 2.7.0.1 of TWRP, then upgrade to this version from the old one.

Instructions in my thread.
[G Pad 8.3 Original Android Development] msaiducar:
Hi [MENTION=581991]roi[/MENTION]rraW "edor" ehT,

I noticed that after my reply. Sorry for that. Now my other problem is, I use Ubuntu 15.10 on my pc and I don't know how to downgrade without Lg Flash Tool. I tried to run Lg Tool with wine, but it didn't work. Is it possible to downgrade VK810 with ubuntu?
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
No, but I assumed you were already rooted since you were trying to install TWRP. If you are already rooted you can skip to the step in my instructions about installing the initial v2.7.0.1 version of TWRP, which doesn't require a computer.

The main aim of downgrading is to make it the easiest to root and install TWRP, but as long as you're rooted you can still downgrade just your bootloader in order to use the Loki'd TWRP install.
[G Pad 8.3 Original Android Development] msaiducar:
Yes, I rooted my 5.0.2 VK810 via KingRoot app. But I'm new about all these stuff. How can I downgrade just bootloader?

---------- Post added at 11:35 PM ---------- Previous post was at 10:40 PM ----------

I, finally, understood whats going on and could manage to follow instructions. Now, I have a tablet that has no amazon and verizon apps :) Thank you [MENTION=2560614]roirraW "edor" ehT[/MENTION]
[G Pad 8.3 Original Android Development] roirraW "edor" ehT:
You're welcome!
[G Pad 8.3 Original Android Development] masterx1234:
this ended up bricking my gpad again but only sometimes, it randomly can get into android but half the time it says secure booting error and it also wont go into twrp.
[Huawei Ascend P6, Mate] gulranek:
About a month or two when the official update for the Ascend P6 became available, I installed it and upgraded my phone to Android 4.4.2 (from 4.2) and Emui to 2.3 (from 1.x). Anyway, I've been having issues with that as it started to overheat and work slow, so I decided to revert back to the original state. (Unless there are fixes for the overheating in your experience?)

How do I do that? I found a topic here about reverting to Android 4.2, but I'm not sure which version my phone used to have... Anyway, here's my phone information if someone could shed some light:

Huawei P6-U06

Android 4.4.2

Emotion UI 2.3

Baseband version IMC1202_PENTA

Kernel version 3.0.8-00800-g4e7741b

Build number P6-U06V100R001C150B536

Custom version CUSTHRVC150D536

Thanks in advance.
[Huawei Ascend P6, Mate] tileeq:
Follow these instructions http://xdaforums.com/ascend-p6/general/how-to-downgrade-4-4-4-2-change-chinese-t2951566
[HTC Desire S] omgnull:
Hello.

Successful installed cm11 and base gapps via TWRP unable to load into system. After returning to recovery found that recovery is

unable to mount /system
unable to mount /cache
unable to mount /data

Any wipe not helping me out.

My device is s-off. Also I cant flash anything from fastboot, it just freezes after executing command.

Is there anything I can do in this situation?
[HTC Desire S] jmcclue:
try flashing lastest 4ext recovery via fastboot and see if that mounts.
[HTC Desire S] omgnull:
Thank you for answer. Unfortunately with no luck. It looks like in locked state.

C:\android\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: HT13RTJ54188
(bootloader) imei: *****************
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.250s

C:\android\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (6216 KB)...
OKAY [ 1.201s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 122.164s
[HTC Desire S] Saf98:
Try fastboot erase recovery command then flash the recovery.
[HTC Desire S] omgnull:
Thank you for answer, lilsafbig. This is not working either. Device just freezes, and console waitng with 'erasing `recovery` ...', I believe i takes for ages.

I still can use adb shell, is there a way to enable usb debugging from TWRP?.
[ZenFone 2 Q&A, Help & Troubleshooting] kenbo111:
The version I just ordered from amazon says this: Item model number: ZE551ML-18-2G16GN-SR. Does that look right? I thought ZE551 indicated the 4gb model? But the ad and this model number all say 2. Is this something new?
[ZenFone 2 Q&A, Help & Troubleshooting] cmendonc2:
You are buying this on Amazon: http://www.amazon.com/ASUS-ZenFone-5-5-Inch-16-Smartphone/dp/B00VWKKF52/ref=sr_1_1?s=books&ie=UTF8&qid=1436124889&sr=8-1&keywords=ZE551ML-18-2G16GN-SR?

It must be an error in the Amazon Database, that is the 2GB RAM model.
[ZenFone 2 Q&A, Help & Troubleshooting] Lorka.Tinou:
In some countries there's a 16gb version of the 551ML, with different CPU too if I'm not mistaken, the kind of version you need to run away from in my opinion.
[ZenFone 2 Q&A, Help & Troubleshooting] Trotter516:
This is the 64GB version. The ZE551ML can come in both a 2GB/16GB and 4GB/64GB variety, as far as the US version goes. The 16GB version is item model number ZE551ML-18-2G16GN-SR while the 64GB version is ZE551ML-23-4G64GN-SR, at least for the silver ones.
[Moto G Q&A, Help & Troubleshooting] dbarf55:
So I bought a used XT1034 US 16GB off of Amazon. When I got it the Wi-Fi cnnection was just terrible. I got average speedtest ratings of 3.00MB/PS instead of the average 25 I get on all of my other 2.4GHZ devices. I decided to load the ParanoidAndroid legacy ROM here and I got slightly better wi-fi speeds (probably my imagination lol) but they are still very slow. In some speedtests with PA-L I got 25MB/PS but that stopped quickly and went down to 3.00 again. I really want to know whats going on, and if there is a way to fix it. I've flashed the stock radio firmwares, restarted the phone, and installed a bunch of ROMS. I'm stumped. Please help me, I cant take this Wi-Fi!

EDIT: If you need some more info:

I have a dual-band Xfinity router (2.4GHZ and 5GHZ)

On my PC (connected to 2.4GHZ) I get 40MB/PS on Speedtest, same with Tegra Note 7
[Micromax Canvas A1] SK Mahadevan:
I rooted my Canvas A1 using philz recovery to CM 12.1 Sprout 4 Nightly the Google Apps package was taken as mentioned on droidone site with.cf domain. The package provided Google App and Play Store only and I installed all other Google Apps separately. While the Gmail, Drive and others are working fine, Google Keep is unable to start. It crashes at the very beginning. :(

Don't know it's the package or app or any other thing which is causing this.

Dear members please provide the solution to resolve this problem.

A big thanks in advance :fingers-crossed:
[Micromax Canvas A1] silentbaba_tvp:
I had the same problem. My notes, contact and most of the other data was also gone.

You must try singing syncing your Google account.