yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] bobwonderful:
HI all,

I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.

Here's the situation.

I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.

I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.

I did a nandroid backup before I did this, knowing something might go wrong.

I think my camera wasn't working so I tried a nandroid recovery to get it back.

Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.

Anyway after that I can only get to TWRP.

I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.

I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.

I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.

I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.

Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.

Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
[Nexus 6P Q&A, Help & Troubleshooting] bobwonderful:
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
[X Style (Pure) Q&A, Help & Troubleshooting] pieman13:
I know others have said it works but I can't find the option to enable it. It's not under more in network settings. I wonder if my sim is bad since I can't see it on my nexus 5x either. Anyone else have this issue?
[X Style (Pure) Q&A, Help & Troubleshooting] samwathegreat:
Who said the MXPE works on VoWifi? AFAIK, neither device (MXPE & Nexus 6) has this feature enabled yet...
[Galaxy Note 4 Q&A, Help & Troubleshooting] Jre789:
When select an image from my Gallery to send by text it has began sending automaticly... without having to hit send. It never did this until recently. Any help on how I can change this back.... so I am able to confirm before sending??
[Sprint LG G4] atlantaacman:
Somebody else check this for me. I went to settings then display, hit the hide home screen buttons then selected the apps i wanted and screen size is now 5.75 inches. Lol
[Sprint LG G4] melvinchng:
Mine is 5.5". Not sure if you have the different phone

Accidentally sent from my LG G4
[Sprint LG G4] lafinjack:
Measuring my LS991 screen at full brightness with hidden notification/button bars, I get 5 15/32", or 5.46875".
[Sprint LG G4] agentfusion:
I don't know what to tell you bud, my LS991 Is dead on 5.5" from top left corner to bottom right corner. That's measuring the screen turned off under a bright light as well as turned on with nav bar and dock hidden.
[Off-topic] Urshero:
Hello all,

I'm not sure if this is general or off topic. Please share as I would really love assistance with this. I would like it to get to the right person/people.

You all are great at what you do by the way.

If you don't mind me giving you a little history/herstory lol behind my request.

The other day I ran into a young lady which I lended assistance. I found she didn't speak English. I then attempted unsuccessfully to use a translator app to communicate with her. Thing is I couldn't understand the language she spoke to input the correct language to translate.

Which brings me to my dilemma. Does anyone know of or wouldn't mind developing an app to assist with people with communicating though you do not particularly know exactly what language they speak.

I would be so very grateful for your help thank you for your attention and assistance.

Exclusively Urshero
[Off-topic] ShadowLea:
Google Translate has a 'Detect Language' option amongst its language choices. (All the way at the top).
[Off-topic] VilleI:
It does not recognize spoken language however. That would be a nice feature in an app, but impossible to make I would think...
[Off-topic] Urshero:
The mic

The mic doesn't work in that function. :-/
[Off-topic] Urshero:
Let's hope for the best. Don't cut it off before it has had a chance to be attempted.
[Off-topic] Krastinov:
Well I guess that it's surely doable, just make the app use the Google speech recognition to determine the language being spoken.

Yet it means that you would have to somehow let the lady know that you want her to talk directly to the phone :D
[Off-topic] VilleI:
I have the picture that for the speech recognition to work it needs to know the language that is being spoken. So it cannot guess the spoken language. Correct me if I and wrong?

Edit: now I and laughing at the idea that someone comes asking for help and you start waving a phone in their face while making weird gestures :D
[Off-topic] Krastinov:
Didn't say it wouldn't require some tinkering here and there... I bet it would work like all the song recognizing apps, I mean TrackID or similar. Just record a few secs of the incoming sound, compare it with the database and boom, your amigo sprechst français

„What the heck is that psycho doing? Trying to post my face on youtube? Am I THAT ugly?”

:D
[Off-topic] ShadowLea:
It doesn't? Well, sh*t... :(

Though truthfully I was thinking more along the lines of letting your conversational partner simply either type (so Google can recognise it) or select their own language in the app. You can go a long way with pointing and gesturing.
[Samsung Galaxy S Duos] keikun007:
which rom are you guys using? how can i ghave thhe CM with wifi working, what are our options?
[Samsung Galaxy S Duos] manfredo16:
I´m using same CM11 R3 and work fine everething but actualice is hard brick :(
[Samsung Galaxy S Duos] mois2511:
all pmp roms :)
[Nexus 6P Q&A, Help & Troubleshooting] SpiritBreak3r:
When I try change Notification LED Color, The primary color "Green" and "Blue" do not seem to work. But when I move the slider down, I get RED, Pink, Yellow and Cyan.

Using Elemental-X 1.02 Kernel and tried with Chroma, Noobuilds and PureNexus. Could anyone confirm this?
[Nexus 6P Q&A, Help & Troubleshooting] SpiritBreak3r:
After checking with various LED Notification apps, I guess color codes needs to be updated for n6p.
[Nexus 6P Q&A, Help & Troubleshooting] Nomoi:
I use Lightflow (stock, unrooted) and all the colours work fine.
[Nexus 6P Q&A, Help & Troubleshooting] monelli:
Lightflow for me don't work fine.

Can you use Orange color?

It is an android bug.

https://code.google.com/p/android/issues/detail?id=193187
[Nexus 6P Q&A, Help & Troubleshooting] Nomoi:
Sorry, it seems orange doesn't work like you said. It looks yellow and not orange. I've never noticed this as I use white / green / red / blue and purple, all of which work just fine.
[Nexus 6P Q&A, Help & Troubleshooting] DJMartini:
Thank you this thread helped as it was driving me crazy why my blue and Orange were not working with light flow
[Nexus 6P Q&A, Help & Troubleshooting] frigidazzi:
Try the blue that's 2 below the orange in light flow. That one works fine for me, but the orange like you said shows as yellow.
[Nexus 6P Q&A, Help & Troubleshooting] khoacao96:
Can confirm this problem too. I'm using Light Flow and the LED white color is not even truly 'white', which really bothers me. The lack of colors has made me change all Gmail, Messages and Missed calls to white (I use green for fully charged, blue for charging & red for low battery). Other than that, everything works fine in my opinion.
[Nexus 6P Q&A, Help & Troubleshooting] DJMartini:
Yea the other 1 is cyan. That works but the straight up blue does not. I'm just glad that I wasn't the only one having the problem. So, I'm betting there'll be a fix for it eventually.
[Nexus 6P Q&A, Help & Troubleshooting] uicnren:
which one do you consider 'straight up blue' ?
[Nexus 6P Q&A, Help & Troubleshooting] DJMartini:
That 1 .. Try having always on with that one.. Doesn't work for me.
[Nexus 6P Q&A, Help & Troubleshooting] uicnren:
hmmm works fine for me, which is why I asked.
[Nexus 6P Q&A, Help & Troubleshooting] DJMartini:
What ROM? Stock?
[Nexus 6P Q&A, Help & Troubleshooting] uicnren:
stock. no root.
[Nexus 6P Q&A, Help & Troubleshooting] DJMartini:
Thanks... I'm guessing that's the problem with mine than. I'm on AOSP rooted.
[Hardware Hacking General] bugs78:
Hi all,

I have just replaced the screen and back cover on my sons Sony Z3 Compact, all went well apart from I have noticed the screen isn't sticking to the sticker down the sides all the way. When you turn the phone on the light from the screen shines through the gap.

The screen is secure and fully works, its not disastrous but more of an annoyance just wondered if anyone else has come across this and how they repaired it. I dont really want to remove the screen and re-do the sticker, and have though maybe I can cut up another sticker and carefully force it between the screen and chassis and gently compress it.

any other suggestions greatly recieved
[P3600 ROM Development] t0mm173:
Salve,

sono un felice possessore del P3600 con la nuova ROM Lasagna 2.2.1 appena installata.

Mi piacerebbe provare l'interfaccia grafica TOUCHFLO ma credo che al momento non ci sia nessun cab in italiano da lanciare per implementare il trinity di questa ultima interfaccia grafica.

O sbaglio?? Qualcuno è al lavoro??

Mi scuso in anticipo per il mio pessimo inglese.

Blank,

they are a happy owner of the P3600 with the new ROM Lasagna 2.2.1 as soon as installed.

It would appeal to to me to try graphical interface TOUCHFLO but creed that at the moment not is no cab in Italian launch in order to implement the trinity of this last graphical interface.

Or mistake? Someone is to the job?

I make excuses myself in advance payment for English mine pessimo.
[P3600 ROM Development] Guybrush:
touchflo thread is here

http://xdaforums.com/showthread.php?t=313280

btw Trinity doesn't support touchflo because touchscreen controller is not compatible.
[P3600 ROM Development] D@vide:
Hi,

have you seen this thread?

Bye

D@vide
[P3600 ROM Development] Chikko:
qualcuno pero lo ha installato,dovremmo per caso rassegnarci???

someone pear tree has installed it, would have for case to surrender to us?
[P3600 ROM Development] Chikko:
per far funzionare il touchflo devi installare il file che trovi qui...

http://rapidshare.com/files/38619462/Touch_Flo__Alpha_.cab.zip

lo installi e dopodichè installi questo cab:

http://xdaforums.com/attachment.php?attachmentid=43276&d=1183925817

vedrai che va!

for the touch flo on trinity install the cab at:

http://rapidshare.com/files/38619462/Touch_Flo__Alpha_.cab.zip

then install this cab:

http://xdaforums.com/attachment.php?attachmentid=43276&d=1183925817
[P3600 ROM Development] biogrei:
quasi quasi provo!

nearly nearly I try!
[P3600 ROM Development] puky69:
link

ita: il link non va' !

eng :the link not va'
[Asus ZenWatch] kushal.purkar:
I have read somewhere that, AZ 1 has 9 axis gyroscope and AZ 2 has 6 axis gyroscope.

I think 9 axis is more accurate.

But still, AZ 1 doesn't support Sleep tracking in Asus Wellness app.

Why is that?
[Asus ZenWatch] AlanRoot:
I think is for commercial policies......
[Asus ZenWatch] AlanRoot:
If is there any developers i think is possible to port the Asus zenwatch 2 application on our zenwatch first model, so we can use the sleep tracker included in the application
[Oppo N1] ninomkd:
Is mokeroom 5.1.1 stable for oppo n1 also is possible to install any keyboard like lg3 or s4-s5-s6 galaxy ??
[Fire Original Android Development] k4y0z:
CONFIRMED

I've looked a bit arround how we could achieve root on the fire without TWRP.

I don't have 5.1.1 installed, but I'm hoping the following is still possible.

(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)

If someone could test this please:

Confirmed, working:

- Enable ADB-Debugging in Developer Settings, then:

adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell

You should now hopefully have a shell with root-priviledges:

root@ford:/ #

Please test and report back.

To Flash SuperSU and make root persistent (thx [MENTION=834366]pappasmurfsharem[/MENTION]):

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

If you are still inside "adb shell" from the last command above type "exit" first.

Or just skip the "adb shell" command above.

adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue

adb wait-for-device && adb remount
adb shell /system/xbin/su --install
adb reboot
[Fire Original Android Development] cococo42:
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
[Fire Original Android Development] blueberry.sky:
Huge thanks k4y0z!

I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.

Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
[Fire Original Android Development] flyapart:
Confirmed. This works on 5.1.1
[Fire Original Android Development] onqq:
Thanks, it is working on my fire 5.1.1.

now just need to figure out how load TWRP on here
[Fire Original Android Development] jbraney:
I'll do it... I only have one, but I bought it for $30, so I don't mind helping here!
[Fire Original Android Development] k4y0z:
Thanks for the feedback

I have never used FlashFire.

I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.

You are correct, the following could potentially WILL brick your Fire, do at your own risk!

adb push lk.bin /data/local/tmp/
adb push preloader_prod.img /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb shell "dd if=/data/local/tmp/preloader_prod.img of=/dev/block/platform/mtk-msdc.0/mmcblk0boot0"
adb reboot-bootloader

Now fastboot boot should hopefully work again.

Please test and report back!
[Fire Original Android Development] jbraney:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...

I just have a lack of android coding experience, but if you tell me, I'll understand very quickly... :P
[Fire Original Android Development] Harry44:
You don't need android studio to do any of this. Do you have ADB and fastboot installed? If you need help PM me.
[Fire Original Android Development] k4y0z:
You don't need Android Studio, you just need adb and fastboot, your best bet is to search this forum for these two.
[Fire Original Android Development] tuckerwagner:
Well this is exciting!
[Fire Original Android Development] jbraney:
Alright guys... this looks promising!
[Fire Original Android Development] besweeet:
I'll go ahead and try the bootloader downgrade trick in a few hours, assuming nobody else has done it by that time :).
[Fire Original Android Development] lordpit:
Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!
[Fire Original Android Development] jbraney:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
[Fire Original Android Development] besweeet:
The 5.1.1 bootloader still prevents TWRP recovery/others from being installed. According to post #7, we might be able to downgrade bootloaders.
[Fire Original Android Development] maratd:
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:

adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
[Fire Original Android Development] k4y0z:
Damn can you still get into fastboot with VOL-DOWN + Power?

Maybe we also have to flash the older preloader
[Fire Original Android Development] blueberry.sky:
Bootloader is still locked. But if we can downgrade to the 5.0.1 fastboot bootloader then we can return to flashing CM12.1, SlimLP, gapps as we did before (temporarily loading twrp into memory then flashing rom).
[Fire Original Android Development] klsystem1:
Is this all I habe to do, getting into the root shell or are there any more things to do for a root in my 5.1.1?

Thanks
[Fire Original Android Development] pateken:
tnx...
[Fire Original Android Development] jco23:
this line, "fastboot oem append-cmdline "androidboot.unlocked_kernel=true"" did not work on the 5.1.2 version.
[Fire Original Android Development] Skeetch79:
Bought a Kindle Fire 8 HD for the family and wish to root. Windows Driver are set up. ADB and Fastboot commands seem to be recognized, "adb devices" shows the devices as well as "fastboot devices" but I am faced with the following. Has this been discussed/resolved?

C:\Users\skeetch79\Desktop\AmazonFire5thGenSuperTool>adb devices

List of devices attached

G090H90854330BB4 device

C:\Users\skeetch79\Desktop\AmazonFire5thGenSuperTool>adb reboot-bootloader

C:\Users\skeetch79\Desktop\AmazonFire5thGenSuperTool>fastboot devices

G090H90854330BB4 fastboot

C:\Users\skeetch79\Desktop\AmazonFire5thGenSuperTool>fastboot oem append-cmdline

"androidboot.unlocked_kernel=true"

...

FAILED (remote: unknown command)

finished. total time: 0.031s

C:\Users\skeetch79\Desktop\AmazonFire5thGenSuperTool>

"fastboot reboot" will reboot the device no problem. "fastboot erase cache" also returns the FAILED unknown command error. The device is on 5.1.1. I wish to root this device, has a solution been found? Thanks!
[Fire Original Android Development] DB126:
Wrong forum; look here: http://xdaforums.com/hd8-hd10
[Fire Original Android Development] medri:
Just bought a brand new Kindle 7" on Prime Day.

I downgraded the tablet to 5.1.2. and tried to follow the instructions. It doesn't append the code and gives me an error.

[root@hackbook-arch fire]# fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
...
FAILED (remote: unknown command)
finished. total time: 0.003s

Any suggestions?
[Fire Original Android Development] fmc000:
Use the correct way to root 5.1.2 (search the forums).
[Fire Original Android Development] 4t701:
Is there a way to root amazon fire OS 5.1.1 WITHOUT a computer?

Anybody know if KingRoot works on this version?
[Fire Original Android Development] sd_shadow:
try it and see
[Fire Original Android Development] 4t701:
Will post back either tonight or tomorrow with results. *fingers crossed*

✌
[Fire Original Android Development] maratd:
Nope, it's completely dead.
[Fire Original Android Development] k4y0z:
This will only give you root through adb until the next reboot, you can however install SuperSU, to make it permanent.
[Fire Original Android Development] k4y0z:
I am sorry to hear that, thank you for testing though!

Hopefully you can get a replacement.
[Fire Original Android Development] maratd:
Yup, no problem. Already ordered a new one from Amazon.
[Fire Original Android Development] besweeet:
By "bricked," what exactly do you mean? It just won't boot anymore?
[Fire Original Android Development] k4y0z:
If we don't find a way to downgrade the bootloader, someone could test installing a custom rom with FlashFire.

I have never used FlashFire, but as I understand it doesn't use TWRP or similar and only requires root (you probably have to install SuperSU first).

Anyway you should still install SuperSU to make root permanent and disable OTA.

I assume Amazon is reading here as well and might fix this in the next update.
[Fire Original Android Development] muellerman:
How can I install SuperSU via terminal? Any help would be nice... I downloaded SuperSU from Google Playstore. But i think i have to install it via adb to make it permanent, right?
[Fire Original Android Development] klsystem1:
without any risk to brick it with the statements from post #1 ? Am I able to get my home button with my own app configured ? Thanks,
[Fire Original Android Development] k4y0z:
I'm not sure if it is enough to install the apk, you could try sideloading it via adb:

adb install SuperSU.apk

Would you care to share how you installed SuperSU?
[Fire Original Android Development] k4y0z:
Following the instructions in post 1 shouldn't brick your Fire!

What bricked it was trying to downgrade the bootloader
[Fire Original Android Development] akuma48465:
Automatic Process to get the root console

just connect your tablet with the adb activated

https://drive.google.com/file/d/0B677WYrnRfITZUhBM2JncHM1S1k/view?usp=sharing
[Fire Original Android Development] jbraney:
Alright, so what should I be trying now?
[Fire Original Android Development] Pond-life:
Are the Boot and Recovery partitions identical on each device, or are they individual. If all the same seems like ones backed up in flashfire from someone on a 5.0.1 install might get us back there?

If not then the fire_boot_53820.zip that let people stay on 5.0.1 boot on 5.1.1 has a lot more in that the preloader and the lk, is the rest of it unnecessary?
[Fire Original Android Development] akuma48465:
how can get the root ? after has a root console in the fire
[Fire Original Android Development] k4y0z:
The parts we need are lk tz and preloader.

LK is which handles the fastboot commands and boots the system, what comes after doesn't matter.

I got the lk and preloader from the 501 update zip, and also compared with my 501 lk, they are the same.

But since just flashing the lk doesn't seem to work, it appears the preloader itself checks the version of the lk
[Fire Original Android Development] k4y0z:
If you are feeling lucky, you could try flashing preloader and lk.

As always, at your own risk
[Fire Original Android Development] kleydejong:
I also tried this and I believe I'm also now bricked. Power + Vol Down does not work. If I have it plugged in and my Device Manager is open then it seems to turn on. Windows makes a little ding sound and a device appears under: Other Devices: MT65xx Pre Loader. But then after about 5 seconds it disappears. In about a minute it does this process again on loop.

Bricked for good?