Database Develop

[REF]LG G Watch R Stock OTA URLs

Introduction:
This is a list of all known OTA's for the LG G Watch R
The LG G Warch R watch has it's ROMs built directly by google, instead of LG.
Click to expand...
Click to collapse
File List:
KIW52H → KNX01R
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unlocked bootloader (Is this needed?)
Basic understanding of command line/shell (to unlock bootloader)
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode (How do you do this for this device?)
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
AntonChernov
Click to expand...
Click to collapse
Changelog:
Nov 29, 2014: Added KIW52H → KNX01R
Oct 18, 2014: Initial page
Click to expand...
Click to collapse
2char

Kernel source for kitkat-wear Lenok
[QUOTE="Bill Yi]
hi All,
Today, we pushed another kernel project for kitkat-wear release. The kernel source can be found on the android-msm-lenok-3.10-kitkat-wear branch in the kernel/msm project. It has the following tags:
android-4.4w_r7 Factory-ROM
android-4.4w_r8 Update #1
bill
[/QUOTE]
There will be an ota when the product launches.
When it finally ships, could someone hook it up to wireshark/etherial/fiddler/<preferred network sniffer> and grab the full url name along with the filename of it?
Also could someone not update theirs immediately and dump the rom when a custom recovery is eventually made for it?

Confirmed there is an ota out of the box, if you have not powered up your gwar yet, please find the ota url for it.

Reboot into fastboot mode (How do you do this for this device?)
Click to expand...
Click to collapse
Power off.
Start tapping the screen with two fingers (one on the top left and one on the bottom right part of the screen).
Press and hold the power button while tapping.
Stop immediately once you see the LG screen disappearing.
Congrats, you are in the bootloader.

Yay show-p is here. My favourite kernel Dev from HTC sensation days
Sent from my GT-I9505 using XDA Premium 4 mobile app

show-p1984 said:
Power off.
Start tapping the screen with two fingers (one on the top left and one on the bottom right part of the screen).
Press and hold the power button while tapping.
Stop immediately once you see the LG screen disappearing.
Congrats, you are in the bootloader.
Click to expand...
Click to collapse
Got it, uploading a Video right now - HowTo enter Fastboot Mode on my G Watch R (4.4W2)
LG G Watch R - HowTo access Fastboot and Recovery: http://youtu.be/mXoE5_QOxxE
EDIT:
Found an easy way to enter Fastboot (cc @show-p1984)
Also the Bootloader in unlockable (see link in my Signature)

Guys
It's link for 4.4.w1 to 4.4.w2 update:
/4beff7b6437440dceee842ca90bc23f51bb7b990.signed-lenok-KNX01R-from-KIW52H.4beff7b6.zip
Need devicename (red text at next example links) at google servers for full link.
For example, links for G Watch and Moto:
android.clients.google.com/packages/ota/lge_clockwork_gwatch_release_key/1ac2ab1e58461027cbfedc3a028744c276a8ecdb.signed-platina-KNX01Q-from-KMV78Y.1ac2ab1e.zip
android.clients.google.com/packages/data/ota/motorola_minnow_metallica/805b44ea505592a98573cf7a4aa9af24974b815d.signed-metallica-KNX01S-from-KGW42N.805b44ea.zip
So we must found name of G Watch R directory at google servers for make a full link.

I was going to try this to hopefully get the boot image but mine was already updated when it came on. :/

AntonChernov said:
Guys
It's link for 4.4.w1 to 4.4.w2 update:
/4beff7b6437440dceee842ca90bc23f51bb7b990.signed-lenok-KNX01R-from-KIW52H.4beff7b6.zip
Need devicename (red text at next example links) at google servers for full link.
For example, links for G Watch and Moto:
android.clients.google.com/packages/ota/lge_clockwork_gwatch_release_key/1ac2ab1e58461027cbfedc3a028744c276a8ecdb.signed-platina-KNX01Q-from-KMV78Y.1ac2ab1e.zip
android.clients.google.com/packages/data/ota/motorola_minnow_metallica/805b44ea505592a98573cf7a4aa9af24974b815d.signed-metallica-KNX01S-from-KGW42N.805b44ea.zip
So we must found name of G Watch R directory at google servers for make a full link.
Click to expand...
Click to collapse
Connect PC, then open USB debugging and use adb command.
Code:
dumpsys dropbox --print | grep 'android.clients.google.com'

EthanFirst said:
Connect PC, then open USB debugging and use adb command.
Code:
dumpsys dropbox --print | grep 'android.clients.google.com'
Click to expand...
Click to collapse
Oh, but I already updated. Is it command actual for updated watches?

AntonChernov said:
Oh, but I already updated. Is it command actual for updated watches?
Click to expand...
Click to collapse
This command for got past log.

EthanFirst said:
This command for got past log.
Click to expand...
Click to collapse
I forget to say that I made factory data reset from stock recovery after update and perhaps logs were deleted?

AntonChernov said:
I forget to say that I made factory data reset from stock recovery after update and perhaps logs were deleted?
Click to expand...
Click to collapse
Yes :crying:

EthanFirst said:
Yes :crying:
Click to expand...
Click to collapse
Oh, sadness.
Why nobody of the owners could not do it?! Rhetorical question of course. That's very easy

I have a great news, friends.
OTA Link:
Code:
http://android.clients.google.com/packages/ota/lge_lenok_lenok/4beff7b6437440dceee842ca90bc23f51bb7b990.signed-lenok-KNX01R-from-KIW52H.4beff7b6.zip

Here it comes...
http://googleblog.blogspot.com/2014/12/android-dress-code-wear-what-you-want.html

Latest lollipop OTA is http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip

tonu42 said:
Latest lollipop OTA is http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
Click to expand...
Click to collapse
How do we install this once it's downloaded?

jmwils3 said:
How do we install this once it's downloaded?
Click to expand...
Click to collapse
Facepalm myself. I tried to do just that, but I ended up bricking my device...... so yea.....

tonu42 said:
Facepalm myself. I tried to do just that, but I ended up bricking my device...... so yea.....
Click to expand...
Click to collapse
Was it because you were using TWRP, or because sideloading the update actually bricks the device?

[RECOVERY] TWRP 3.0.2.0

Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
IMPORTANT
- Only works with devices that originally had and retain the bootloaders fromFireOS 5.0.1
- This recovery cannot be flashed whilst the bootloader is locked. In order to boot recovery use the following command from fastboot.
Code:
fastboot boot twrp_fire7_302-0.img
*** Please do NOT create any mirrors ***
Downloads
- Amazon Fire (ford) TWRP Image
Source Code
- Kernel Source
Thanks
csolanol
diegocr
Dees_Troy
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Fire
Contributors
ggow
Version Information
Status: Stable
Created 2016-11-25
Last Updated 2016-11-26

New Build is Up
- Dated 25 November 2016
- Build Number 3.0.2-0
- Initial Release

Does this work with any FireOS version?
I remember you could only run it with 5.0.X.
Can you run it with other versions now?

tonibm19 said:
I remember you could only run it with 5.0.X.
Can you run it with other versions now?
Click to expand...
Click to collapse
Only works with 5.0.x, will add a note to the OP.

this is awesome! Thanks!

Any chance you could make a 3.1.0 build?
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/

FBis251 said:
Any chance you could make a 3.1.0 build?
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Click to expand...
Click to collapse
Yes, I'm on holiday next week so will do so after that.

ggow said:
Yes, I'm on holiday next week so will do so after that.
Click to expand...
Click to collapse
Current version doesn't let me unencrypt /data. Do you think an updated one will? Have you tested this with an encrypted tablet?

nirogu325 said:
Current version doesn't let me unencrypt /data. Do you think an updated one will? Have you tested this with an encrypted tablet?
Click to expand...
Click to collapse
This appears to be an unresolved issue on some/many devices starting with v3.0.2 and continuing through the 3.1.x series. Head over to TewmWin's site for details - although a well crafted Google search may be more productive.

Davey126 said:
This appears to be an unresolved issue on some/many devices starting with v3.0.2 and continuing through the 3.1.x series. Head over to TewmWin's site for details - although a well crafted Google search may be more productive.
Click to expand...
Click to collapse
No need. It works on my Nexus device with 3.1.x, but it would be better to try an updated TWRP on this tablet to see if it lets me decrypt /data. Also my post is an indirect suggestion to put a warning on the original post that states it doesn't work with encryption. Hopefully it'll work with 3.1.x whenever ggow updates this. Right now, all TWRP shows me is an option to modify system, but doesn't recognize there's an encrypted partition and that's why it doesn't show me the screen where I input the password.

nirogu325 said:
No need. It works on my Nexus device with 3.1.x, but it would be better to try an updated TWRP on this tablet to see if it lets me decrypt /data. Also my post is an indirect suggestion to put a warning on the original post that states it doesn't work with encryption. Hopefully it'll work with 3.1.x whenever ggow updates this. Right now, all TWRP shows me is an option to modify system, but doesn't recognize there's an encrypted partition and that's why it doesn't show me the screen where I input the password.
Click to expand...
Click to collapse
Field reports suggest a password prompt is raised on 3.1.x for some devices but decryption ultimately fails. Didn't dig deep enough to identify device types or commality across posts. Appears hardware dependent.

Davey126 said:
Field reports suggest a password prompt is raised on 3.1.x for some devices but decryption ultimately fails. Didn't dig deep enough to identify device types or commality across posts. Appears hardware dependent.
Click to expand...
Click to collapse
Yeah, that's why I said it's more productive to try a newer version on this tablet. I learned a lesson some months ago and no longer run any device unencrypted. That's why it's important to me.

@ggow
can we use 2ndinit source code from https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286 (thanks to @rbox for source code https://github.com/androidrbox/firetv-2ndinit ) for boot TWRP on rooted Fire up to 5.3.2.1?
my knowledges is not enough for this

Kramar111 said:
@ggow
can we use 2ndinit source code from https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286 (thanks to @rbox for source code https://github.com/androidrbox/firetv-2ndinit ) for boot TWRP on rooted Fire up to 5.3.2.1?
my knowledges is not enough for this
Click to expand...
Click to collapse
No. Recoveries and ROMs built for other devices do not work. Also, 5.3.2.1 is not able to be rooted, except in one, as of now, unrepeatable instance. Lastly, only 5.0.x can boot TWRP, as Amazon removed the command in later versions.

@PorygonZRocks
I know it all
I'm talking about principle. Not about using "FireTV 1 (bueller) TWRP Recovery" as-is
As i understand, 2ndinit can be adapted for Amazon Fire with some nuances

Kramar111 said:
@PorygonZRocks
I know it all
I'm talking about principle. Not about using "FireTV 1 (bueller) TWRP Recovery" as-is
As i understand, 2ndinit can be adapted for Amazon Fire with some nuances
Click to expand...
Click to collapse
Sorry, I probably should have read the link before talking ?
It looks cool, but I don't have the technical knowledge to know if it's portable.

ggow said:
Yes, I'm on holiday next week so will do so after that.
Click to expand...
Click to collapse
Any progress on a new TWRP for this device? Your post is months old, that's why I'm wondering. A new version might finally let me decrypt /data.

nirogu325 said:
Any progress on a new TWRP for this device? Your post is months old, that's why I'm wondering. A new version might finally let me decrypt /data.
Click to expand...
Click to collapse
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?

Dakotalee24 said:
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?
Click to expand...
Click to collapse
I assume at least one of your 5th gen Fire devices is rocking a 5.0.x bootloader. While you need a tether to load/boot TWRP the SuperTool is not required. Simply place your device in fastboot mode and issue the following command from the host command prompt;
fastboot boot <recovery.img>
....where 'recovery.img' is the name of the TWRP image. You'll need to prefix as needed depending where the image file is located.

Dakotalee24 said:
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?
Click to expand...
Click to collapse
Addressing the first question since Davey126 already addressed the second one. By the time of that post, I had my tablet encrypted and the current TWRP version in this thread never prompt me for decryption. I stopped using encryption because I read this device's SoC doesn't have AES (hardware encryption acceleration) plus Lollipop doesn't behave well when encrypted (unlike Marshmallow or later Android versions).

Will A2 be under Anti-Rollback policy??

You all know that, now Mi phones will have anti rollback features while upgrading to MiUi 10.
Though A2 is stock androud, will it face any such kinds of restrictions somehow??

There is good post describing rollback policy in Android. Mi A2 was released with Android Oreo, so we need someone with phone who will check support of Verified Boot using adb commands provided in post:
Code:
adb shell
dumpsys package | grep "verified_boot"
OR
Code:
adb shell
getprop | grep "avb"
Click to expand...
Click to collapse

AlexX333BY said:
There is good post describing rollback policy in Android. Mi A2 was released with Android Oreo, so we need someone with phone who will check support of Verified Boot using adb commands provided in post:
Click to expand...
Click to collapse
PS E:\platform-tools> adb shell
>> dumpsys package | grep "verified_boot"
jasmine_sprout:/ $
this is output, every time i type the code

Syed Shahriar said:
PS E:\platform-tools> adb shell
>> dumpsys package | grep "verified_boot"
jasmine_sprout:/ $
this is output, every time i type the code
Click to expand...
Click to collapse
I suppose that means no Verified Boot. Try another command, just in case.

AlexX333BY said:
I suppose that means no Verified Boot. Try another command, just in case.
Click to expand...
Click to collapse
tried both, same result

Enter fastboot.
Type "fastboot getvar anti".
If none, the phone is not under Anti-Rollback policy.
If 2 or 3, it is under ARP, but is not yet activated.
If 4 or above, it is surely under ARP, and is already activated.

Sithu Htun said:
Enter fastboot.
Type "fastboot getvar anti".
If none, the phone is not under Anti-Rollback policy.
If 2 or 3, it is under ARP, but is not yet activated.
If 4 and/or above, it is surely under ARP, and is already activated.
Click to expand...
Click to collapse
it shows "2" on my device (4GB/64GB, HK).

matchung said:
it shows "2" on my device (4GB/64GB, HK).
Click to expand...
Click to collapse
Be sure to check it before downgrading. Upgrading is okay.

Didn't see this thread (need to del the one I started just now), but yeah, mine also says '2'.
Sad to see that, didn't think the A2 would have this.

I was on V9.6.10.0, installed the OTA update (v9.6.12.0), tried to root with Majisk and things gone wrong. So, I flashed v9.6.10.0 again.
This counts as a downgrade?

kadu20es said:
I was on V9.6.10.0, installed the OTA update (v9.6.12.0), tried to root with Majisk and things gone wrong. So, I flashed v9.6.10.0 again.
This counts as a downgrade?
Click to expand...
Click to collapse
Not sure, but knowing they've implemented this on the A2, I'd be ** extremely ** cautious. If it bricks, sounds like a serious pia to fix.
Boot to fastboot and type 'fastboot getvar anti'. If you get a number back, then it's been implemented on your phone. If you get nothing back then it's not yet implemented. It's possible this was just introduced?
If you flashed 9.6.10 successfully, try above command and see if it's implemented in that version.

That 2, 3, 4 is just the counter. Once you unlock the bootloader, ARB should be off in Android One phones.
Here's everything you need to know about it:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/

ILA said:
That 2, 3, 4 is just the counter. Once you unlock the bootloader, ARB should be off in Android One phones.
Here's everything you need to know about it:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Click to expand...
Click to collapse
From the Frequently Asked Questions at the bottom of said article:
<quote> Why doesn’t Xiaomi disable anti-rollback protection when you unlock the bootloader?
That’s a good question. </quote>
In Other Words: the article indicates it does not disable ARB after an unlock. Where do you get that it's disabled on their Android One devices? Because the article doesn't say that. I certainly hope it's true though.
Maybe someone with an unlocked bootloader can verify the fastboot query does not return a number?

AsItLies said:
From the Frequently Asked Questions at the bottom of said article:
<quote> Why doesn’t Xiaomi disable anti-rollback protection when you unlock the bootloader?
That’s a good question. </quote>
In Other Words: the article indicates it does not disable ARB after an unlock. Where do you get that it's disabled on their Android One devices? Because the article doesn't say that. I certainly hope it's true though.
Maybe someone with an unlocked bootloader can verify the fastboot query does not return a number?
Click to expand...
Click to collapse
From here:
"The biggest difference between Google and Xiaomi’s implementation is that Google’s anti-rollback protection is disabled if you unlock the bootloader while Xiaomi’s can’t be disabled. Once you install a build with anti-rollback protection enabled on a Xiaomi device, there’s no going back.
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
Ok, so the XDA app just misfired and didn't post my (very) lengthy explanation... Will post tomorrow, I'm just too tired to re-explain again :/

I have a mobile Mi A2 that does not exit from the edl mode
AsItLies said:
Didn't see this thread (need to del the one I started just now), but yeah, mine also says '2'.
Sad to see that, didn't think the A2 would have this.
Click to expand...
Click to collapse
I have a mobile Mi A2 that does not exit from the edl mode and this is due to the installation of the ROM Mi 6X and urged that when I tried to restore it to the original ROM on Android, and if I repeatedly tried to restore it in more than one way, but to no avail, it does not exit from the edl mode even if before flashing

Ahmed 2009 said:
I have a mobile Mi A2 that does not exit from the edl mode and this is due to the installation of the ROM Mi 6X and urged that when I tried to restore it to the original ROM on Android, and if I repeatedly tried to restore it in more than one way, but to no avail, it does not exit from the edl mode even if before flashing
Click to expand...
Click to collapse
your problem is you can't return to mi A2 jasmine android 1 ..NEVER AGAIN ..you can only flash LATEST stock MIUI rom fastboot via miflash when edl ...or you can use custom rom after recovering phone ..search for my other posts on how to do it .
Sent from my wayne using XDA Labs

[Guide] Rooting Nexus 7 (2012) Lollipop [5 Simple Steps]

Every single guide i found went through a little bit too much, in this guide i'll show you how to root your device without installing custom recovery in 5 easy steps. I am going to assume that you already have android platform tools installed on your computer
Downloads
TWRP: Asus Nexus 7 2012 Wi-Fi | Asus Nexus 7 2012 3G
Latest Magisk from the official github repo
Steps
Boot into the bootloader by holding Power + Vol Down for about 10 secs
Connect your device using a usb cable to your computer
If you see LOCK STATE - UNLOCKED, skip this step, otherwise you need to unlock your bootloader by running this command from your computer. Accept and wait while device resets. *this will wipe your device
Code:
fastboot oem unlock
Your bootloader should now be unlocked, running this will give you access to twrp without installing it
Code:
fastboot boot path/to/twrp-recover.img
Now you have two pathways:~
Normal: Use your touch screen to install magisk.zip file you downloaded from github and you're done
Broken Screen/Digitizer: From your computer while twrp is open, type this command. * assuming that you renamed magisk archive to magisk.zip and copied it to your sdcard with adb push
Code:
adb shell twrp install /sdcard/magisk.zip
Going Back
GedBlake said:
If, in the unlikely event, you do mess up rooting your tablet, you can easily re-flash to factory using the factory stock images available at the links below...
Nexus 7 - WiFi only
https://developers.google.com/android/images/#nakasi
Nexus 7 - WiFi and 3G
https://developers.google.com/android/images/#nakasig
Click to expand...
Click to collapse
Reboot, Have fun!

pushqrdx said:
Every single guide i found went through a little bit too much, in this guide i'll show you how you can root your device without installing custom recovery with 5 easy steps. I am going to assume that you already have android platform tools installed on your computer
Downloads
1- TWRP: Asus Nexus 7 2012 Wi-Fi | Asus Nexus 7 2012 3G
2- Latest Magisk from the official github repo
Steps
1- Boot into the bootloader by holding Power + Vol Down for about 10 secs.
2- Connect your device using a usb cable to your computer.
3- If you see LOCK STATE - UNLOCKED, skip this step, otherwise you need to unlock your bootloader by running this command from your computer. Accept and wait while device resets * this will wipe your device
4- Your bootloader should now be unlocked, running this will give you access to twrp without installing it.
5- Now you have 2 pathways
Normal: Use your touch screen to install magisk.zip file you downloaded from github and you're done
Broken Screen/Digitizer: From your computer while twrp is open type this command. * assuming that you renamed magisk archive to magisk.zip and copied it to your sdcard
Reboot, Have fun
Click to expand...
Click to collapse
Hi, pushqrdx...
A nice and concise guide, and whilst it's perhaps a little late in the day (the Nexus 7 is, after all, some 7 years old now ~ where does the time go!), I always think that the more of these guides there are, the better.
For example, someone might have just picked up an old Nexus 7 somewhere second hand, and might be looking for such instructions as yours.
I also like the way you've updated the procedure for Magisk. The last time I rooted anything, let alone a Nexus 7, was with Chainfire's SuperSU root package. But of course, root is done via Magisk these days, so yours is a nicely updated guide.
And you've also provided a contingency scenario for a damaged screen/digitizer - not something I've had to deal with myself.
-------------------------
I hope you don't mind me adding a little additional tip for anyone reading this...
If, in the unlikely event you do mess up rooting the Nexus 7, you can easily reflash back to factory using the factory stock images available at the links below...
Nexus 7 - WiFi only
https://developers.google.com/android/images/#nakasi
Nexus 7 - WiFi and 3G
https://developers.google.com/android/images/#nakasig
-------------------------
So, in conclusion then, a straightforward and concise guide that covers all the basics to rooting the Nexus 7 - kudos to you sir for writing it.
Kind Rgrds,
Ged.

GedBlake said:
Hi, pushqrdx...
A nice and concise guide, and whilst it's perhaps a little late in the day (the Nexus 7 is, after all, some 7 years old now ~ where does the time go!), I always think that the more of these guides there are, the better.
For example, someone might have just picked up an old Nexus 7 somewhere second hand, and might be looking for such instructions as yours.
I also like the way you've updated the procedure for Magisk. The last time I rooted anything, let alone a Nexus 7, was with Chainfire's SuperSU root package. But of course, root is done via Magisk these days, so yours is a nicely updated guide.
And you've also provided a contingency scenario for a damaged screen/digitizer - not something I've had to deal with myself.
Click to expand...
Click to collapse
Thanks! I had to deal with a broken tablet recently and i thought it would be nice to share incase anybody finds it useful. And yeah Nexus 7 is so damn old ?. Also thanks for the tip i have edited the post to include it as a quote from you

Problem with Nexus
I have a Asus Nexus 7 2012 Wi-Fi. I have managed to unlock the bootloader and, using adb, checked the devise is authorised. When I try to run 'flash-all', I get stuck at '<waiting for a device>'.
PS C:\Users\OFFICE PC\Desktop\Nexus 7 KitKat\nakasi-ktu84p> .\fastboot flash-all
< waiting for any device >
I cannot fix this problem so I went to your tutorial, I have downloaded twrp and magisk. Do I run these from CMD?. Also, where is twrp-recover.img?

GaryWilliams said:
I have a Asus Nexus 7 2012 Wi-Fi. I have managed to unlock the bootloader and, using adb, checked the devise is authorised. When I try to run 'flash-all', I get stuck at '<waiting for a device>'.
PS C:\Users\OFFICE PC\Desktop\Nexus 7 KitKat\nakasi-ktu84p> .\fastboot flash-all
< waiting for any device >
I cannot fix this problem so I went to your tutorial, I have downloaded twrp and magisk. Do I run these from CMD?. Also, where is twrp-recover.img?
Click to expand...
Click to collapse
TWRP has to be in the same folder on the PC as your ADB tools. Then using the command given, you boot into TWRP. You don't install it as per this procedure. Then using the TWRP's 'Install' button, find the Magisk zip and install it(you should have copied/pushed it to the tab before).
EDIT: The 'twrp-recover.img' is the name you give to the TWRP which you downloaded.

Thanks, my mom still uses her 2012 nexus 7, great little tablet, but I updated to whatever the latest droid version and it SUCKS, stopped it in its tracks, jams up and slower than ever, want to get it back on the previous version of droid when it worked 10 times better.

doitinthedirt said:
Thanks, my mom still uses her 2012 nexus 7, great little tablet, but I updated to whatever the latest droid version and it SUCKS, stopped it in its tracks, jams up and slower than ever, want to get it back on the previous version of droid when it worked 10 times better.
Click to expand...
Click to collapse
Maybe it would run well on Android Go Edition, as that is designed for devices with 2GB of RAM or less. I'm thinking of trying that with my one but have no idea of how to go about it at the moment. Will have to read the OP here at least 7 times before any of it sinks in!

thank you

Kindle Fire 7" (9th Gen, 2019) Any way to install Lineage OS to it?

Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.

Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329

Michajin said:
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Click to expand...
Click to collapse
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?

Reiixas said:
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?
Click to expand...
Click to collapse
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.

Michajin said:
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.
Click to expand...
Click to collapse
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?

Reiixas said:
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?
Click to expand...
Click to collapse
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.

Michajin said:
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.
Click to expand...
Click to collapse
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?

Reiixas said:
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?
Click to expand...
Click to collapse
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?

Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
Hello,
I managed to fix it. But I REALLY appreciate your help. You helped A LOT.
THANK YOU :victory:

How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks

brankota said:
How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks
Click to expand...
Click to collapse
You need to do the hardware hack by opening the tablet.
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/ama...grade-t3944365

Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
OP says local video playback in LOS is still not supported. Is this still true?

thisisnotatest said:
OP says local video playback in LOS is still not supported. Is this still true?
Click to expand...
Click to collapse
Seems like it was all working. I haven't had it on in months. Make a back up flash it and test it. If you don't like it or it has many issues, restore the backup.

Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
For everyone that has the fire tablet 7 gen 9 , aka mustang , if your tablet was made
in 2020 or later you won't be able to unlock , or flash it .
After 2019 and the first production run , they hardware locked this model tablet.
Starting in 2020 the fire tablet 7 gen 9 aka mustang was shipped with the
chip hardware locked and even opening it up to perform the bypass won't work.
They basically did a bait and switch at Amazon ,
Mid production run for this model they secretly changed the major
possibilities and functions that could be done on it .
Essentially you were buying an inferior unit with the same model number .
Personally I think Amazon should give millions of people their money back for
unethical and wrong business practices being used on its customers.
I talked to Amazon corporate offices and they said that their policy is that at any time
They can modify a current model unit and change its hardware features , all without
informing the customer that their current model being sold was now
with a hardware lock . just like in 2019 , people bought this model tablet , but by 2020
The same model tablet was redesigned secretly to now be fully hardware locked.
People who were unaware like me bought this model in 2020 , and yes it
unfortunately was made hardware locked , but people who bought the first
production run of them in 2019 were lucky enough to buy ones that were not made with any
Hardware lock .
There's different methods to see if your mustang model tablet is locked ,
Either way it all means one thing . your tablet will never be unlocked or flashed ,
At least not without specific engineering , and ROM flashers anyway.
Even then , good luck .
It don't look good .