yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note5] shamelin73:
Was on the 6.0.1 MM then Odin back to 5.1.1 took the last security update. I didn't notice this till now. It wouldn't work in 6.0.1 and now it won't work with 5.1.1.
[AT&T Samsung Galaxy Note5] shamelin73:
This still won't work or turn on.

Could it be package Disabler?
[AT&T Samsung Galaxy Note5] MrMike2182:
You need to enable OEM unlock first!
[AT&T Samsung Galaxy Note5] shamelin73:
Sorry that still didn't work unless I need to reboot.
[AT&T Samsung Galaxy Note5] MrMike2182:
Looks like you're going to have to factory reset unfortunately.. That shouldn't have been grayed out to begin with... As soon as you tapped on the build number 7 times that should have been ready to go but in any case tap on it 7 times again and if not then factory reset.
[AT&T Samsung Galaxy Note5] shamelin73:
Yes a bit strange. Was like this in 5.1.1 and now.

Factory reset didn't change it.
[AT&T Samsung Galaxy Note5] MrMike2182:
I'd odin the firmware but then again, I don't think you can use Odin without USB Debugging on..

Download terminal from the Play Store and see if this works, if not, then I don't know..

This probably won't work since you need root but it's not going to hurt to try.

echo 1 > /data/property/persist.service.adb.enable
[AT&T Samsung Galaxy Note5] jack man:
Odin will work either way. Odin uses download mode to flash to the phone.
[AT&T Samsung Galaxy Note5] shamelin73:
I have Odin it back to 5.1.1 and same issue but didn't think to check until system had already been restored. I am back on 6.0.1 I am thinking it is My Knox security or something as I have company email on my phone.
[AT&T Samsung Galaxy Note5] MrMike2182:
If Knox is installed on your phone and it's a company phone, then that's why it's like that.. You'd have to get rid of it but your probably going to need permission from said company since it's probably password protected.
[AT&T Samsung Galaxy Note5] shamelin73:
Is a personal phone. They allow BYOD but have to allow their security but usually is contained within My Knox but I guess that USB debug is one thing it disables outside of Knox.
[AT&T Samsung Galaxy Note5] shamelin73:
I can confirm that it was KNOX that killed it. I removed KNOX to see and when I checked it was able to be enabled again.
[Nexus 5 Q&A, Help & Troubleshooting] rockerblood:
i got this message this morning... im already at 6.0.1 any idea what this update all about? thanks
[Nexus 5 Q&A, Help & Troubleshooting] Logansj1:
You got a security update for the month of February. Google has been putting out monthly security updates.

Its may now though, so I don't understand why you're just now getting February's.
[Nexus 5 Q&A, Help & Troubleshooting] rockerblood:
because my patch is still january 2016, if i flash it my root wont be gone?
[Nexus 5 Q&A, Help & Troubleshooting] Logansj1:
Oh, I actually have no idea about this, but I imagine that might be the case. But they are also small updates.
[Android Q&A, Help & Troubleshooting] aimzzz:
I just got a fairly new phone model... T-Mobile LG K7. There's not much info on rooting it, so I used KingRoot. It worked fine, but I really want to remove the KR app & use SuperSU. There doesn't seem to be a custom rom for LG K7 as yet, so I can't go that route.

Any suggestions either for an alternate way to root, or a way to drop KR & install SuperSU? Do you have any experience with Wolfdroid?
[Android Q&A, Help & Troubleshooting] PackoPunchX:
I just purchased the Fire HD 10.1

I want to install custom recovery so I can flash Cyanogemod 12.1, I already did it with my galaxy S3 so I'm familiar with Odin. Can anyone provide the required files? Or even links?
[ZenFone 2 General] kanagawaben:
The autostart manager app is absolute garbage. Have discovered it to be the cause of my RAM management issues on my 2GB 550 model. With it running, the phone fails to free up RAM and starts to stutter and run badly as the free RAM falls under 250MB. With autostart manager disabled, no such problems. Wish I had realised this sooner!
[ZenFone 2 General] Firstyxd:
Try 360 security. Works like a charm for me!
[ZenFone 2 General] Dan_Jacques:
Isnt the 360 Security the app from Qihoo that steal personal data?

Try the bootmanager xposed module.
[XDA Assist] ShowMustGoOn:
Hello all, I have a problem because when you unlock my mobile phone started looping off and in general does not start.

I can not enter into TWRP because I gave erase all data.

What do I need to download? Where all this throw?

Im from poland and I do not know which version of the software should be good

I would greatly appreciate if anyone will be able to help me!

I download old firmware 5.1.1 from producent page i put dload folder on sd card and this is what happens

https://youtu.be/OyyD1vd8NHA

If i connect usb cable to phone, instalation started, but its stuck on 90%

Phone is unlocked, but adb dont see my phone in fastboot mode!

Im write another thread because in http://xdaforums.com/honor-4c/help/broken-honor-4c-t3385711

no one want to help me!
[XDA Assist] ShowMustGoOn:
refresh
[XDA Assist] GuestK0087:
Thread closed.

Duplicate:

http://xdaforums.com/honor-4c/help/broken-honor-4c-t3385711

Do not duplicate posts. Be patient and wait for a response in your original thread.
[Android Apps and Games] snes9x ex+:
Guys could you help me out here? I'm using an LG G2 D802 running Paranoid Android 5.1.1 Lollipop.

Ever since updatd 1.18.1 rolled ouf, the game simply won't install/unpack its data as if it doesn't detect my phone's internal storage.

Here's a pic of my problem:

i.imgur.com/lqeaF5Q.jpg/

Any fixes for this? I got in touch with their support the other day via email, and they ultimately told me that they couldn't do anything about it, so you guys are the only ones that could help me.
[Fire Android Development] hwmod:
Reserved for future expansion
[Fire Android Development] sd_shadow:
nice work
[Fire Android Development] Tomsgt:
I will try to make a video on this soon
[Fire Android Development] STrRedWolf:
Ahhh! A glimmer of hope for a bricked Fire. I had tried to downgrade a 5.1.2 to a 5.1.1 and bricked it... but I did see the MediaTek USB ACM device pop up and down. If I can find a 5.1.2 update, I can try to extract that, slap that on the internal MMC, and see if I can unbrick my (first) Fire that way.
[Fire Android Development] sd_shadow:
http://xdaforums.com/showpost.php?p=62986665&postcount=3
[Fire Android Development] hwmod:
Quick guide to "unbrick" 5.1.2 from downgrade attempts

This is a condensed resume of post #1 to "unbrick" and rollback to stock firmware 5.1.2.

You will need a working system with Python3 installed and the "pyserial" module.

Download and unzip AFTV2-Tools in a new folder on your PC.

From inside the AFTV2-Tools folder execute the following script:

./handshake.py

if your setup is OK the script will print this message to the console:

waiting for preloader ...​

now ensure the tablet is switched off, then connect it to the PC with the USB cable.

In a couple of seconds the script will detect the serial port and print this message:

Found port = /dev/ttyACM0

Handshake complete!​

confirming the tablet was successfully switched to [USBDOWNLOAD] mode.

Next you need to write the 5.1.2 version of "lk.bin" to the UBOOT partition:

./write_mmc.py $((0x1460000)) lk_512.bin

now exit the [USBDownload] mode by executing the following script:

./read32.py 0 1

this will possibly print a few error in the console but that is expected.

Wait 10 seconds and then pull the USB cable to disconnect it from the PC.

If all went well the device will reboot with a working "UBOOT/lk.bin" partition.

You can now boot into recovery mode and "adb sideload" stock fire os 5.1.2 update.

You will have your device fully working again (not downgraded but fully functional).

.:HWMOD:.
[Fire Android Development] STrRedWolf:
I've just tried that... and no go. It won't boot into it. I'm wondering what else needs to be flashed this way...
[Fire Android Development] hwmod:
Did the "handshake.py" script return the expected messages ?

Did the "write_mmc.py" script output the progress of writing the "lk_512.bin" ?

Did you get some message indicating errors from running the two scripts above ?

I suggest people trying this method to save the output and include relevant parts in their posts.

This way I may be able to give extra instructions or help.

.:HWMOD:.
[Fire Android Development] hwmod:
Looking at your log It looks like a successful "unbrick". The errors at the end after the "./read32.py 0 1" are the expected behavior for the wrong command needed to exit [USBDOWNLOAD] mode.

Try to remove the battery for 10 seconds then reconnect it and see if it reboots now.

Could you tell the size in bytes of the "lk.bin" you wrote ?

.:HWMOD:.
[Fire Android Development] STrRedWolf:
Ugh. Time to take a spludger to my Kindle. :(

sandra aftv2-tools # ls -l ~tygris/dls/kindle/lk.bin
-rw-r--r-- 1 tygris tygris 407096 Apr 15 2015 /home/tygris/dls/kindle/lk.bin
[Fire Android Development] Tomsgt:
FIre OS 5.1.2 LK.bin is 400 KB (409,600 bytes)
[Fire Android Development] STrRedWolf:
And... negative. No reboot into recovery.
[Fire Android Development] Tomsgt:
did you pull the battery and then plug it back in and try to reboot
[Fire Android Development] STrRedWolf:
Reflashed with the correct lk.bin file, pulled the battery... nothing. No reaction on screen. At least we are getting somewhere...
[Fire Android Development] hwmod:
I can see that the length of "lk.bin" is different from what you suggested, both in 5.1.2 and 5.1.2.1.

update-kindle-global-37.5.4.2_user_542168620.bin (version 5.1.2) - lk.bin is 407096 bytes

update-kindle-37.5.4.2_user_542169020.bin (version 5.1.2.1) - lk.bin is 407096 bytes

the two "lk.bin" from these two versions are exactly the same and their "md5sum" is:

d73a2c504dc4db427d1dc3996ce4e206

This could be one of the possible reasons for [MENTION=7503382]STrRedWolf[/MENTION] not being able to "unbrick" his tablet. To reduce the risks of errors it would be advisable to always include the exact length of the files in bytes accompanied by the "md5sum".

.:HWMOD:.
[Fire Android Development] STrRedWolf:
I would also not post the MD5 hash but instead the SHA-256 hash. MD5's deprecated due to known security attacks against it. SHA-256 is considered much more secure (enough that SSL/TLS certificates are required to use it).

Here's the "sha256sum" of the lk-5.1.2.bin from the update-kindle-global-37.5.4.2_user_542168620.bin

tygris@sandra ~/dls/kindle $ sha256sum lk.bin
ef3e0cd928ddf380fa00da1f79fd63e6ed1279be1f4f2e093498116f6faec48e lk.bin
tygris@sandra ~/dls/kindle $ ls -l lk.bin
-rw-r--r-- 1 tygris tygris 407096 Apr 15 2015 lk.bin
[Fire Android Development] DB126:
Security concerns are irrelevant in the context of determining file equivalency/integrity. Fine to provide one or both checksums but no valid reason to avoid MD5 in this use case.
[Fire Android Development] Kramar111:
MD5 or SHA-256?

Don't need reinvent the wheel

Amazon says "SHA-1" and publish SHA-1 for system, boot, recovery, UBOOT(=lk.bin), TEE1(=tz.img) in each update META-INF/com/amazon/android/target.blocklist + copy that to /cache/recovery/last_blocklist

For example, lk.bin

Ver	Size	Sha-1
5.0.1	406964	4690a896d2964b39d5dd8aea7b09b57a80511f22
5.1.1	409060	5f0c2350956fc03aaed24fa83c6c0f441af2b578
5.1.2	407096	995983f35352a3d20c979db447e82739249c52d8
5.1.2.1	407096	995983f35352a3d20c979db447e82739249c52d8
5.1.4	407160	618df04cb5cb96fc286d9c0eacba5256976aee4e

P.S. Same sha-1 and size :) for 5.1.2 and 5.1.2.1 = no brick after downgrade 5.1.2.1 -> 5.1.2

If lk.bin in 5.1.4 will have size 407096 and SHA-1 995983f35352a3d20c979db447e82739249c52d8 - downgrade to 5.1.2 is possible.
[Fire Android Development] apravint:
how to write for the below target..

{

"partitions": [

{

"caremap": "54,0,32767,32768,32770,32873,32875,33372,65535,65536,65538,66035,98303,98304,98306,98409,98411,98908,131071,131072,131074,131571,163833,163840,163842,163945,163947,164444,196607,196608,196610,197107,219648,229376,229378,229481,229483,229980,262143,262144,262146,294912,294914,295017,295019,295516,327679,327680,327682,360448,360450,393216,393218,393715,413254",

"mount_point": "/system",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/system",

"sha1": "3306bf2e44223a49a87d280ec7898f1e344fbdd6"

},

{

"length": 8591360,

"mount_point": "/boot",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/boot",

"sha1": "d9940c61221ead6483b659c2fd5580e597be6de5"

},

{

"length": 9197568,

"mount_point": "/recovery",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/recovery",

"sha1": "8457735fdb219efd8d9a858c5b7c55406f40cde1"

},

{

"length": 477584,

"mount_point": "/lk",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/lk",

"sha1": "0c6b6f9a231a9f0eac6153825415ac01afe35979"

},

{

"length": 3307008,

"mount_point": "/tee1",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/tee1",

"sha1": "798e1bd1f1ff4ef20b1dc634db2686caed64b036"

},

{

"length": 2048,

"mount_point": "/pl_hdr0",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/boot0hdr0",

"sha1": "e382f00b844c777f296ac1c38651423a95b1aa3d"

},

{

"length": 136692,

"mount_point": "/pl_img0",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/boot0img0",

"sha1": "868f1b695ef80ca9e6763fdffc9538c336e93726"

},

{

"length": 2048,

"mount_point": "/pl_hdr1",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/boot0hdr1",

"sha1": "90de972d84bd7daf405c0d7f2216ff54668f9712"

},

{

"length": 136692,

"mount_point": "/pl_img1",

"dev": "/dev/block/platform/mtk-msdc.0/by-name/boot0img1",

"sha1": "868f1b695ef80ca9e6763fdffc9538c336e93726"

}

],

"fingerprint": "Amazon/full_giza/giza:5.1.1/LVY48F/49.5.5.4_user_554206920:user/release-keys"

}
[Fire Android Development] aaa4b4b:
Hey XDA community!

I found this thread lurking the un-brick method for my Fire 7 5th gen. I've bricked it the regular way trying to downgrade 5.4.4 to 5.3.1 via adb sideload.

Since the OP method reported not to be workable with different combination of Fire OS versions, my question is:

If the OP-method just needs the update (maybe some code changes to the python script) to cover different combinations, or it is just unapplyable for newer Fire OS versions?

Ninja-edit:

OK, it is impossible to write to BOOT1 section of the pre-loader in newer firmwares (newer than 5.1.1 I believe). So there is no way, even theoretically to unbrick, right?
[Fire Android Development] mrmazak:
Do you know if these cmds work, or just that they are listed in strings from the lk. ?

What I'm after here is; with the bootloader locked, will fastboot accept these flash commands. From my general Android history "flash" and "boot" not working when bootloader is locked.
[Fire Android Development] DragonFire1024:
You're pretty much correct. You can input the commands, but from what I have seen, on my own devices, is a string of error messages...something along the lines of "cannot perform this operation on a locked device."
[Fire Android Development] theashleyd123:
I see as mentioned above that no success has been achieved from newer versions being bricked, I was on 5.4 and silly me thought I'd try to go back to 5.1 bricked of course, I'm wondering whether or not there are any new anti rollback checks being carried out as well as the one being patched in this process, if so would it be possible to manually flash the entire stock ROM and thus being able to downgrade? New to this but surely if we can flash one partition we could flash them all.
[Fire Android Development] DragonFire1024:
Bootloader is locked. Nothing can be flashed on a locked bootloader.
[Fire Android Development] DB126:
Actually, several partitions can be flashed/modified with a locked bootloader as evidenced by the installation of custom ROMs on rooted devices. That said, nothing can be done w/o a functional bootloader which is the case on your bricked device.
[Fire Android Development] theashleyd123:
So does that mean that the bootloader version is still 5.4? If so could I rewrite the other partitions with those from the 5.4 official update? I'm not sure whether that's possible?
[Fire Android Development] munwwer:
hi

above method is suitable for kindle fire 2nd genration? and what is pip utility?

thanks
[Fire Android Development] sd_shadow:
It is very unlikely this would work on a 2nd gen fire.

This only works on a very specific situation , with 5th Gen Fires
[Fire Android Development] mohsin05:
:crying: help me in my case return no output curser is bling i am waitng for 15 mins after 15 mins message show device return no output or multiple acess on port?

./write_mmc.py $((0x1460000)) lk.bin

my curser is just blinking and nooutput :confused: i download lastest os bin and covert into zip after extract i put ik.bin from it and put it on atv2 / help me plz
[Fire Android Development] sd_shadow:
This only works if device was on Fire OS 5.1.1, then downgraded to 5.0.1.

Any other scenario, is futile.
[Fire Android Development] Najeeb Baba:
Hello Bro

bro where is your make vedio link pllazz help me???
[Fire Android Development] Najeeb Baba:
Hello Bro

How To Connect With Pc My Tab Is Completely Dead After Flash Please Till Me Bro????
[Fire Android Development] sd_shadow:
This method is not going to work for you.
[Fire Android Development] Najeeb Baba:
Hello Bro

But How To Sloved My Problem Please Help Me :crying::crying:
[Fire Android Development] DB126:
You screwed the pooch; there is no recovery. Save/sell it for parts.
[Fire Android Development] Najeeb Baba:
oh no

:crying::crying: I flash with adb sideload
[Fire Android Development] dronga:
Fire HD 10

Does this method work for kindle fire hd 10 7th gen :(((

my hd 10 is bricked after downgrade from 5.6.2.0 to 5.6.1.0
[Fire Android Development] sd_shadow:
No, read post #1
[Fire Android Development] MrPollardsOpus:
Boot Loop

Hey, thanks for the awesome post.

I have a fire that is stuck in a boot loop from a downgrade, this method starts to work except in the middle of the connection the device restarts itself preventing the connection from being fully executed. I googled around for a little bit but only seemed to have found posts that simply ended with "if you can't get to the stock bootloader screen you can't fix your device" I find that hard to believe seeing as the device is rebooting itself in such rapid succession.

I've tried disconnecting the battery and attempting to connect but I still get the same issue. The device connects get's recognized and then disappears and `.handshake.py` throws an error. I am totally prepared to go a step further and solder some leads to the serial pads on the board and connect to my serial debug cable, except I'm not seeing where to make that connection on the board.

Any help or direction much appreciated.
[Fire Android Development] sd_shadow:
You have a 7in 5th Gen Fire that you downgraded from 5.1.1 to 5.0.1 ? Seems unlikely.

---------- Post added at 08:15 PM ---------- Previous post was at 08:12 PM ----------

This was an unusual situation in 2016, now it's just inconceivable.
[Fire Android Development] MrPollardsOpus:
So that's a no on it being fixable?

I've had the tablet for some time and I'm fairly positive it is a 7 inch 5th gen, the other 2 that I own that were purchased at the same time on the same order all say Fire (5th Generation) under Device Model on the Device Options Screen and they're all not larger than 7 inches.
[Fire Android Development] sd_shadow:
Current firmware is 5.6.0.1

https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
[Fire Android Development] TheGoliath:
Unbrick Fire 7 5th gen (recovery flashback?)

Greetz,

I just wanted to ask if there is any known method or possibility to get a working stock recovery through this?

Cause currently my device is broken cause I had a bad flash (tried to flash magisk (obv, doesn't work with unlocked bootloader)) and previously tried to flash twrp over the stock recovery while being on a 5.2. bootloader. Thus I can't do anything from now on.

But maybe you guys have an idea, how to get that working properly?

Thanks in advance,

Felix aka TheGoliath
[Fire Android Development] sd_shadow:
There is no fix.

---------- Post added at 07:33 AM ---------- Previous post was at 07:31 AM ----------

Which has been stated many times
[Fire Android Development] TheGoliath:
But just theoretically. Why can't we flash the recovery with the method stated above? We just need to examine the recovery hex and then we should be able to flash the recovery.bin/img or am I wrong/why am I wrong?
[Fire Android Development] DragonFire1024:
Because the bootloader is locked. Flashing anything to any partitions besides the system will brick the device because it's not signed by Amazon's key.
[Fire Android Development] TheGoliath:
Okay. Another question. Can I flash the official signed update.bin via this method? So theoretically it shouldn't brick cause of Amazon's signature. Cause as mentioned in the first post, there is no signature/cert/sha checking. But maybe I'm just stupid
[Fire Android Development] DragonFire1024:
The only thing you can flash is signed Amazon software or a custom rom signed with a test key. So if the update.bin is signed by amazon, ythen yes, provided its for your tablet. Some amazon tablets you can't downgrade firmware. Using ADB sideload most certainly checks for signatures.
[Fire Android Development] TheGoliath:
There should be a signature included in those binary builds. Thus it should be possible. [MENTION=4267571]sd_shadow[/MENTION] ?
[Fire Android Development] DragonFire1024:
Yes. They are signed with platform and or test keys which why we can flash a rom on the Fire 7. Now this might change. Amazon left a few 'system' apps on these tablets, 7, HD 8 and HD 10, that is supposed to remove the check for those keys. I haven't tried it yet, but I doubt it would work on anything but OTA.
[Fire Android Development] TheGoliath:
So am I theoretically able to flash my whole fire again? Cause as I've stated above, I've "bricked" it
[Fire Android Development] DB126:
Theoretically humans can breathing underwater.

Let's say you have a signed binary. How do you propose installing it on a "bricked" device? Even if stock recovery were fully functional the homegrown franken-flash would never make it through integrity checks. A locked bootloader and crippled fastboot environment severely limit recovery options.
[Fire Android Development] TheGoliath:
Yes. But i should make it through the integrity checks if I flash the stock update binary provided by Amazon what I want the whole time. So the integrity should be given and thus it should work imo. So *theoretically* I only need to examine the correct hex and then start to flash

Cheers
[Fire Android Development] DB126:
Unfortunately, that's not the way it works in practice in the context of a "bricked" 5th/7th gen Amazon device. Perhaps there is a unique element to your specific situation that I am not fully appreciating.
[Fire Android Development] k4y0z:
[MENTION=6922463]TheGoliath[/MENTION] If your fastboot is still working, and just your recovery is broken, you could try flashing through fastboot

fastboot flash recovery recovery.img

I don't remember if that feature was disabled by amazon though.

Obviously it should be an amazon-signed recovery.

If that doesn't work, I don't see why the method mentioned in post 1 wouldn't work to flash the recovery, you'd just have to insert the correct address for the recovery-partition.
[Fire Android Development] TheGoliath:
Yeah. So fastboot still works. But I've already tried flashing the recovery but the bootloader has been crippled as it has been pointed out already by many people here in this thread. [MENTION=4267571]sd_shadow[/MENTION] so if my fastboot works, why shouldn't the recovery reflash work? Cause I should be able to locate the recovery partition and find out the hex for that. Then proceed with the steps above and it normally should he shiny again. Or am I wrong?
[Fire Android Development] DragonFire1024:
You could try

fastboot flashing update (update.ZIP)

Not sure how to convert the Amazon.bin update file to a zip though.

---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------

Would be fastboot flashing i believe. Just make sure to download the latest platform-tools. Then type

fastboot help