yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Q&A, Help & Troubleshooting] stiso:
Hello guys,

I need some help with installing a custom ROM ( This one: https://xdaforums.com/lg-g-pad-83/development/rom-android-7-0-nougat-20161008-r16-t3476750 ).

As stated in the title I have a LG GPad 8.3 with Android 5.0.2 (Korean version flashed through .kdz), software version v50030a.

What I did:

- rooted the tablet with Kingroot

- installed SuperSu and a terminal emulator and followed a tutorial on the web on how to remove all Kingroot stuff

- installed: Root Checker (it confirms that I have root), Oficial TWRP App and Flashify

- downloaded: the ROM and Gapps from the link above, and twrp-3.0.2-2-v500.img (on my external sdcard)

I flashed from Official TWRP App the .img file but when I try to enter the Recovery I get the error:

Secure booting Error! Cause: boot certification verify

If i hold the power buton for a longer time it shuts down after that if I power it (normal) it boots normal

I flashed from Flashify the same .img file but the story is the same, I get the same error:

Secure booting Error! Cause: boot certification verify

And again, if I power it down and restart it it boots normal.

I am stuck on this. I always get to the point with that error. What to do next?

From what I understand I need to get to the TWRP screen from the recovery mode but It doesn't go there.

Some youtube videos showed the same error for 1-5 seconds and after that entered that menu, but mine does not .... I left it for minutes and nothing. :(

P.S. Also tried with : twrp-2.8.7.0-v500.img and twrp-3.0.0-0-v500.img and got the same result.
[G Pad 8.3 Q&A, Help & Troubleshooting] xdamend:
Hi I am in similar situation.

I also had the korean v50030a installed. I experienced the same problems as described above.

In addition to that i went back to V50010A_00.kdz (via Flashtool)

Afterwards i did following:

1. Root with towelroot

2. root was confirmed via SuperSu

3. installed flashify -> flashed most recent twrp (twrp-3.0.2-2-v500)

4. boot into recovery

5. flashed V50020F-Bootloader.zip then lineage-14.1-20170126-nightly-v500-signed from twrp

after reboot i get:

Secure booting Error! Cause: boot certification verify

I even tried the workaround https://xdaforums.com/showpost.php?p=62050593&postcount=2 (after reflashing 4.2.2 with Flashtool and re-doing Steps 1 and 2)

no change.

Can anyone please point me in the rigtht direction? What am i missing?
[G Pad 8.3 Q&A, Help & Troubleshooting] aventu:
I don't have a korean model but I also got "Secure booting Error! Cause: boot certification verify" because I was still using the loki bootloader bypass method. The recent one is called "bumped".

https://xdaforums.com/lg-g-pad-83/development/script-convert-loki-kernel-to-bumped-t3081457

lineage-14.1-20170126-nightly-v500-signed worked for me after flashing this.
[Xiaomi Mi 5 Questions & Answers] RootNightmareX:
I am about to buy a new phone, to have at least 2-3 years and i want it to be future proof.

I have to choose between MI5 and NOTE 3 PRO.

The price difference is 70$. Does it worth the extra bucks?

Which one of this devices has better development ? I am really intrested to have a good dev support (lineage, ressurection, nitrogen,xenon and kernels)

Which one should i chose? Which one is more resitent ?
[Xiaomi Mi 5 Questions & Answers] glogal:
Same company but different commercial line (of product): high-end and medium-low-end; with different hardware "particles" inside and different screen sizes and different weights...

Advice: If you are going for the lowest model of the high-end and comparing that with the highest model of the medium-low-end ... you are not doing a good job in the decision-making process.

The MI company is famous for the MIUI (their rom) and .... are expanding around the world but, for now, they have a presence in their motherland and in the asian market (mostly India); the rest are resellers.

So you should consider, for the final decision, the nation in wich will operate your device.

And if you really want (it's the first item in your wish/need list) a "dev supported device" maybe the MI company is not the best one for you.
[Xiaomi Mi 5 Questions & Answers] RootNightmareX:
I am talking about xda devs software support and i saw it has Lineage official. How it is compared to NOTE 3 PRO?

And the difference between them is only 70$..

So do you think it worths the extra bucks?

Does mi5 have construction problems or heating/throtthling specific for sd820?
[Xiaomi Mi 5 Questions & Answers] Eraron:
Mi5

Go for the Mi5, it's lighter thinner and the GPU is a lot better.

It's been my main phone for a year now and hasn't let me down once.

And lot's of support for it, LineageOS 14.1 is running great.

The Note 3 pro does have a lot longer battery life thanks to the 4000mah battery vs 3000mah and the SD625 is more energy efficient.

I usually recommend the Note 3 to 9/10 people, since battery life > games.

Although it will run all games just fine, i doubt you can run Google Daydream on it like i am on my Mi5.

As for overheating and build quality neither of them have any problems whatsoever, the SD820 doesn't have the problems the SD830 had.
[Xiaomi Mi 5 Questions & Answers] RootNightmareX:
If i will change my phone after 1 year, still worth it? I saw note 3 has better development which i like.

PS: wtf is 830 even launched?!
[Xiaomi Mi 5 Questions & Answers] RootNightmareX:
uppppppp
[Xiaomi Mi 5 Questions & Answers] Eraron:
I meant the SD810, my bad.
[Xiaomi Mi 5 Questions & Answers] xdadevet:
The Redmi Note 3 is more popular and has better development. But that doesn't mean development for the Mi 5 is bad. And since almost all ROMs are AOSP or CM based these days, the scene is pretty much the same between the two. It's the better phone. If you have the money, the choice is simple really. It's camera, display and performance is excellent, and development is good. It's got Gorilla Glass 4 as well, which is a bonus. Battery life is okay, so if that's a concern you might be better of with the Note 3.
[Samsung Galaxy S7 Edge Questions and Answers] danny772:
Is there any difference between using the device at 720p , 1080p or quadHD resolution in new nougat update ?

performance or battery wise ?
[Samsung Galaxy S7 Edge Questions and Answers] CuBz90:
The difference in battery life is so small you wouldn't even notice. Performance is not affected either. I have no idea why they included this feature.
[Android Software Development] akhilkedia94:
Android Auto-Localization - Translate Strings.XML

This is a project to localize your Android app , by translating your string resources(e.g. `strings.xml`) automatically using Microsoft Azure Translate.

It requires Microsoft Azure Translation API key (instructions below).

Helps developers localize their Android app easily to 56 languages, with just one click.

Features

Translates to 56 languages

Cache translations so you dont end up using all your quota everytime

Handles some XML escaping

Usage

Download the Source Code from https://github.com/akhilkedia/Android-Auto-Localization_Translate-Strings.XML

Simply edit the constants in `src/main/Const.java`

Run the java code (using Eclipse/AndroidStudio/etc. in Windows/Linux.) - It will generate all possible translations for you

How to get FREE Microsoft Azure Translate Subscription Key

Sign up for a Microsoft Azure account. If you don’t already have an Azure account, sign up for a Microsoft Azure account at http://azure.com.

After you have an account, sign into the Azure portal at http://portal.azure.com.

Add a Microsoft Translator API subscription to your Azure account -> Choose a pay-as-you-go subscription (Will require a credit card, but don't worry, nothing will be charged) -> Select the ﻿+ New ﻿option -> Select ﻿Intelligence﻿ from the list of services -> Select ﻿Cognitive Services APIs﻿. Select the ﻿API Type﻿ option -> ﻿Select ﻿Text Translation. In the ﻿Pricing Tier﻿ section, select the Free Tier (F0) -> Fill out the rest of the form, and press the ﻿Create﻿ button.

Retrieve your authentication key -> Go to ﻿All Resources﻿ and select the Microsoft Translator API you subscribed to -> Go to the ﻿Keys ﻿option and copy your subscription key to access the service.

Limitations

Does not handle String Arrays so far

Does not handle CDATA

Keep your strings simple, and this will work just fine. For any issues, post here or on GitHub. Or even better, send a pull request.

XDA:DevDB Information

Android Auto-Localization - Translate Strings.XML, Tool/Utility for all devices (see above for details)

Contributors

akhilkedia94

Source Code: https://github.com/akhilkedia/Android-Auto-Localization_Translate-Strings.XML

Version Information

Status: Stable

Current Stable Version: 1.0.0

Stable Release Date: 2017-01-29

Created 2017-01-29

Last Updated 2017-01-29
[Huawei Mate 9 Questions & Answers] mastereric12:
Hi everyone, I'm new in this forum making a new thread but I need help in some questions that I have, right now I am in China and have realized that Huawei Mate 9 in the version of 128 Gb of internal memory and 6 Gb ram (MHA-AL00) is cheaper here in china. ( I am from Panama). The issue is that I don't know if there is an international ROM that includes all Google services and if it is compatible with the LTE network in Panama(700 MHz band 28). It would be of great help to me advise if buy me here in China the 128 Gb version coming in $650 or settle for the model of 64 gb and 4 gb RAM sold in Panama that coupled with tax is $ 700.

Thanks to all that can help me and best regards for all.
[Android One (First-Generation) Cross-Device Genera] Uchoosme:
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.

Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.

After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.

Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.

Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.

I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.

If you guys have any other ideas/solutions I'm all ears.
[Fire General] DB126:
A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit.

https://xdaforums.com/amazon-fire/d...-5th-gen-supertool-root-t3272695/post70784402

Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.
[Fire General] stonedpsycho:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?

I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.

Maybe I am just unlucky.
[Fire General] joey_slugs:
Not having any luck with it either.
[Fire General] TechDad378:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...

1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.

2. Once connection is working follow the "Super Tool" setup directions.

3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.

4. Once you have Gplay setup, use Super Tool to install KingRoot.

5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.

6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.

7. Please keep in mind it is just an overview in order to determine the steps correctly.

If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)

My apologies for not providing more accurate details, its just an overview.
[Fire General] Mr McBoatface:
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.

How did you roll back ? Through ADB or placing the update file in the internal SD ?
[Fire General] TechDad378:
Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.

Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".
[Fire General] jextrevor:
No luck with this method. Will keep trying.
[Fire General] Duke91:
Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.
[Fire General] TechDad378:
Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.
[Fire General] Takash1M0T0:
You still need to provide us with one of the most important tips, what version of kingroot you are using.

Thank you
[Fire General] DB126:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
[Fire General] BeeWall:
If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.
[Fire General] Geek Surfer:
What ever happened to the guy that had rooted it? I knew he was bs.
[Fire General] TechDad378:
Hmm...

Interesting response.

With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.

Recommending following command,

C:/yourself/ adb sideload patience.zip

---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------

Point taken. Just hoping LineageOS will be as widespread.

As for the root, I reverted back to original. Trying to recreate the environment which allowed success.
[Fire General] DB126:
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.
[Fire General] jextrevor:
What a shame that people can't be considerate online anymore.
[Fire General] Mr McBoatface:
[MENTION=5278919]TechDad378[/MENTION] Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?

I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.

Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed

My router is blocking OTA so going keep playing with this
[Fire General] Mr McBoatface:
5.1.4 Rooted !!!!!

Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!

I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://xdaforums.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.

Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://xdaforums.com/devdb/project/?id=9793#downloads

Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.

Moral of the story never give up and try some kingroot versions from the xda links above

Going to reset the device and confirm it's repeatable.
[Fire General] BeeWall:
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
[Fire General] Mr McBoatface:
Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.

It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.

See attached video in zip to confirm
[Fire General] DB126:
Well, it is rootable (and thus ROM replaceable) as-is. Not sure why you would want to update beyond 5.3.1 unless Alexa is the draw.
[Fire General] TechDad378:
Alexa should be a "draw back", due to privacy concerns. This tablet has become more time consuming then imagined. But will play around with it from time to time. Will add any additional info if something of interest comes across while playing.

TD378
[Fire General] DB126:
Not a fan of Alexa and similar tech for similar reasons. But some level of big tech sharing/tracking is all but inevitable. Tablet is as time consuming as you allow it to be. Can be pretty straight forward and maintenance free with a small up front effort. Sticking with stock reduces that to near zero. Amazon has done a good job at simplify the Android experience. But you give up a lot for that 'benefit'.
[Fire General] ctodd111:
Is there any way to tell from a picture of the box whether a Fire 7 (unopened) is old enough to predate 5.3.2.1?

Or can one tell by the purchase date or serial number?
[Fire General] Jake1702_:
Waste of $15. I followed instructions on another post and disabled ads without root and without paying. Issue is, you do have to do it every once in a while as it sometimes comes back, but a small price to pay anyway.

Also, how would one block OTA updates without root?
[Fire General] DragonFire1024:
It is if their "unsubscribe" feature doesn't actually *unsubscribe* you from anything. Is there any fine print on the rules for Special Offers?
[Fire General] DB126:
It prevents the display of ads (after $15 USD payment) but does not stop the associated data download and associated background activity.
[Fire General] Ayden7777:
Amazon is pretty stupid, but can this be rooted by psneuter or rageagainstthecage?
[Fire General] DragonFire1024:
Then their "unsubscribe" feature is false advertising...heh. Ironic eh? I'll chat with them when my new tablet arrives.
[Fire General] DB126:
Not really but you can discuss that w/Amazon. You'll probably score a freebie unsubscribe with enough noise. Good luck achieving anything else.
[Fire General] DB126:
Ha! Amazon is one of the best at preventing root exploits and not exposing bootloader vunerabalities. Don't know if FireOS is susceptible to the methods mentioned above; grab a $40 USD device and give it a whirl.
[Fire General] Skar3:
Sharing my experience with version 5.3.1.0:

I tried several times using the kingrooot application unsuccessful. In the end I used the desktop version, the program has reached the 35% then the message appears that the device could not be rooted, I checked and kingroot was installed correctly and the root was present. Through Supertool I installed supersu without any problems!
[Fire General] Ayden7777:
You really haven't heard of the Rageagainstthecage ADB exploit??

http://www.droidxforums.com/forum/hacking-help/12440-simple-beginners-guide.html

Also tell me if this works:

(Method 2 "Psneuter")

https://xdaforums.com/showthread.php?t=2684210

Also I think Amazon really doesn't want you touching thier bootloader...

Otherwise use launcherhijack v2.1 while we wait for an exploit...or we can bug amazon....jk
[Fire General] DB126:
Lol - give them a whirl; not holding my breath.
[Fire General] Ayden7777:
Oh ok good luck I guess...Make sure Amazon doesn't lock your luckloader either! I just think that the exec of the files will not work, but the exploit is adb itself not android...don't know about psneuter though
[Fire General] Jake1702_:
As Davey said it stops them showing but they are still downloaded.

I myself used this topic: https://xdaforums.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946

No root needed and no $15 needed!
[Fire General] crazyates:
LoL! Rageagainstthecage was from years ago. I think the thread you linked was from 2010? Next you're going to suggest Z4root?

I remember using those on my Virgin Mobile Optimus Slider running Gingerbread. Whatever exploits those used have long since been patched.
[Fire General] DragonFire1024:
As of the moment, there is not root or rollback for the Fire 7, 5th generation, running 5.3.2.1.