yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] bibikalka:
While playing with AFTV2 tools quite a bit, I thought it'd be convenient to have some way to identify what bootloader version one has (given bricking implications & all). Doing checksums on the full TEE1 & UBOOT partitions is not very useful, because the empty area in the partitions may have junk, and that would impact the checksum. So something slightly different is needed.

Here is what I propose, one can read the first few bytes of TEE1 & UBOOT partitions, and then look at them with a hex editor. Fairly low tech, but there you go ... Unfortunately, "hexdump" is not present by default on Fire, so a few more manipulations are required. First, run this with adb (can also be read with AFTV2 tools):

adb shell
su
mkdir /sdcard/tmp/
dd if=/dev/block/mmcblk0p4 of=/sdcard/tmp/04_uboot.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/tmp/09_tee1.img
cd /sdcard/tmp
md5 *.img
exit
exit
adb pull /sdcard/tmp

Then, with a hex editor (such as Frhed), look at the first few bytes of these images on your PC. On linux it's even easier, just do "cat -c 8 *.img | hexdump". You should see something like the following:

04_uboot.img: UBOOT: 88 16 88 58 [COLOR="Red"]b4 33 06 00[/COLOR] 4c 4b 00 00 "LK"
09_tee1.img: TEE1: 88 16 88 58 [COLOR="Red"]00 3c 10 00[/COLOR] 54 45 45 00 "TEE"

The 4 bytes in red are key to identify the version. Please see the table below for the data I've compiled so far. Let's add to it as more versions become available/known (if your combination is not listed, please post here):

UBOOT
d8 27 06 00 Unreleased, 5.0.0, (Build date Saturday, August 1, 2015, 10:39 PM GMT)
b4 33 06 00 5.2.2_053820 5.0.1
54 3f 06 00 5.2.2_055120 5.0.1
e4 3b 06 00 5.4.1_112720 5.1.1
38 34 06 00 5.4.2_168620 5.1.2
78 34 06 00 5.4.4_271020 5.1.4
b8 3c 06 00 5.5.2_153420 5.3.1.0

TEE1
00 3c 10 00 Unreleased, 5.0.0, (Build date Saturday, August 1, 2015, 10:39 PM GMT)
00 3c 10 00 5.2.2_053820 5.0.1
00 3c 10 00 5.2.2_055120 5.0.1
00 3c 10 00 5.4.1_112720 5.1.1
00 3c 10 00 5.4.2_168620 5.1.2
00 3c 10 00 5.4.4_271020 5.1.4
90 84 11 00 5.5.2_153420 5.3.1.0

[MENTION=6058831]DoLooper[/MENTION], [MENTION=5515628]kirito9[/MENTION], [MENTION=4267571]sd_shadow[/MENTION], [MENTION=5728225]Kramar111[/MENTION], [MENTION=3411776]zeroepoch[/MENTION], [MENTION=4381075]hwmod[/MENTION], [MENTION=4246643]Tomsgt[/MENTION]
[Fire Android Development] Kramar111:
unknown 5.0.1

UBOOT
54 3f 06 00 5.2.2_055120 5.0.1

TEE1
00 3c 10 00 5.2.2_055120 5.0.1
[Fire Android Development] fmc000:
Fire originally with 5.1.3 - downgraded to 5.1.2 . uboot and tee1 are consistent with 5.1.2 .
[Fire Android Development] bibikalka:
Indeed, when you downgraded, the bootloaders got overwritten and so you see 5.1.2 ! But luckily, this combination does not brick.
[Fire Android Development] DB126:
Hence the 'special' procedure for upgrading FireOS while leaving the current bootloader intact. A standard sideload/OTA update refreshes bootloader, kernel, rom, etc.
[Fire Android Development] steve8x8:
In a strict sense, the procedure doesn't leave the bootloader intact - it first writes the newer version (which is part of the stock ROM) to later replace it back with the original one. And this "later" may be crucial - if in-between something bad happens (bad battery level, bad cable, power outage on the PC side), game over.

What's the ratio of successful vs. bricking here?

Unfortunately, nobody seems to have followed the path [MENTION=4551511]Vlasp[/MENTION] had suggested a year ago: to trim down stock ROMs to explicitly exclude bootloader files and install instructions (and possibly add su, and disable ota and ads). I understand that with FF we're no longer limited to signed ROMs, so this should be feasible, and scriptable for future ROM versions, no? (If I could extend days to 36 hours...)
[Fire Android Development] DB126:
True. Didn't expect a literal interpretation but appreciate the clarification and associated cautions for others.

This has been done for other Amazon devices (eg: 3rd gen HDX) but garnished little user interest as an alternative to custom ROMs. The misunderstanding/misuse of custom stock builds actually created bigger headaches and a few unfortunate bricks. Eventually the images stopped being maintained.

Still searching for those elusive hours! :). Same can be said for developers who struggle to maintain what is already out there. Witness the cracks in several custom ROMs that have not seen recent updates.
[Fire Android Development] Jrhotrod:
Great and easy way to identify bootloader version. Disappointed to find that I was on 5.3.1 bootloader, but at least I know now :)
[Fire Android Development] steve8x8:
Quick update (although useless since reading off the timestamps would require root which isn't available yet for 5.3.2.1 and higher - that's why I won't merge this into the checker tool yet):

fireOS-5.0.0/images/preloader.img: 20150728-232738
fireOS-5.0.1/images/preloader_prod.img: 20150730-164940
fireOS-5.1.1/images/preloader_prod.img: 20150923-180133
fireOS-5.0.1/images/preloader.img: 20150930-051243
fireOS-5.1.1/images/preloader.img: 20151202-052945
fireOS-5.1.2/images/preloader_prod.img: 20160120-094719
fireOS-5.1.4/images/preloader_prod.img: 20160217-183554
fireOS-5.1.2/images/preloader.img: 20160227-021828
fireOS-5.1.4/images/preloader.img: 20160506-045524
fireOS-5.3.1.0/images/preloader_prod.img: 20160603-023745
fireOS-5.3.2.0/images/preloader_prod.img: 20160603-023745
fireOS-5.3.1.0/images/preloader.img: 20160624-191357
fireOS-5.3.2.1/images/preloader_prod.img: 20161102-031807
fireOS-5.3.2.0/images/preloader.img: 20161104-214024
fireOS-5.3.2.1/images/preloader.img: 20161201-113631
fireOS-5.3.3.0/images/preloader_prod.img: 20170116-085533
fireOS-5.3.3.0/images/preloader.img: 20170328-012523

---------- Post added at 01:58 PM ---------- Previous post was at 01:11 PM ----------

Um, by the way, there had been reports that 5.1.3 had been rooted without downgrading to 5.1.2, if I remember correctly.

If that's your last FireOS version, may I ask you to run the bootloader tool and report back the result? Same for 5.1.2.1... Thanks
[Fire Android Development] jpearn:
After an adventure in updating to 5.3.3.0 I have :

uboot : b0 99 0e 00

tee : not recognisable

The tablet boots, I can reload TWRP if needed but if I flash the previous bootloader I had 541 it bricks and I have to recover using the linux ISO. It looks like my tee1 partition is corrupted. Any advice on how to proceed would be good ! Thanks.
[Fire Android Development] BeeWall:
Reflash the partition with DD?

Download the firmware update, rename it to *.zip from *.bin, and there should be something called TEE.img or something similar. Then push it to the device with "adb push /path/to/TEE.img /sdcard" Then, on the tablet or in adb shell, run 'dd if=/sdcard/TEE.img of=/dev/block/mmcblk0p9'
[Fire Android Development] jpearn:
I thought this however I noted in the other gapps / root thread that it should be dd if=453_tee1.img of=/dev/block/mmcblk0p3

I'm on Ariel Fire 7 4th, so I guess the partitions are different ?
[Fire Android Development] BeeWall:
Yes, they would be different. Make sure to use a TEE from the correct device, not one from this model.
[Fire Android Development] DB126:
This thread pertains to the 5th gen Fire 7 (Ford) not the 4th gen HD 7 (Ariel).
[Fire Android Development] steve8x8:
Identifying the bootloader version is one thing, being able to decide whether a downgrade would result in a brick is another...

Is there a way, on a Fire 7 (5th), to extract the anti-r* "stepping numbers" from bootloader files/partitions that get compared with entries in RPMB (which is only accessible by the bootloader, but not the kernel)? This might save a lot of guesswork and bricks.

In lk.bin, there's "androidboot.rpmb_state=%d" right next to "androidboot.unlocked_kernel=true" and "androidboot.unlocked_kernel=false". Access seems to happen via device numbers.

OTOH, preloader_prod.img contains strings like "[RPMB] Invalid magic, re-creating..." and "[RPMB] RPMB provisioning disabled" or even a message about a skipped, invalid anti-r* state.

Too bad it seems to be impossible to watch the device boot at such an early stage. Half a MB of ARM code is not what I'd want to trace manually... extracting the preloader from its MTK wrapper seems to be the easiest part...
[Fire Android Development] Kramar111:
https://xdaforums.com/amazon-fire/development/bootloader-unlock-ideas-t3289721/post65585385 and some previous/next post
[Fire Android Development] steve8x8:
Thanks for the pointer to one of the missing links! Being able to track the messages down might limit the amount of machine code to be parsed...
[Fire Android Development] 2WR3505:
uboot - 88 16 88 58 B8 3C 06 00 4C 4B 00 00 00 00 00

tee1 - 88 16 88 58 90 84 11 00 54 45 45 00 00 00 00

5.3.1, lol. whats a good rom for this amazon fire 5th gen?
[Fire Android Development] m00head:
[ROM][AOSP] Fire Nexus ROM - LMY49M [22 JULY 2017] - XDA Developers

https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714

[ROM] Lineage-12.1 [12 SEP 2017] - XDA Developers

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447
[Fire Android Development] 2WR3505:
Thanks, i went with the nexus rom, it runs nicely :)
[T-Mobile LG G4] orells:
Hey y'all i need help. :crying:

So yesterday I unlocked the bootloader and flashed stock MM 20i from Autoprime onto my friends device. All was well until he got root happy and started flashing mods. He installed Viper, which I believe is compatible but not sure, and a camera mod which clearly states it's for h815 :mad: http://xdaforums.com/g4/themes-apps/root-marshmallow-6-0-60fps-camera-mod-t3271174

I got the phone back from the jackass today and i've tried wiping and re-flashing from TWRP and have done a refurbish using LGUP to no avail. Speaker is still silent as a morgue and the camera is Ray Charles (r.i.p.)

After every flash attempt the phone boots fine and moves through initial setup without any issues.

How can I repair this?
[T-Mobile LG G4] raptorddd:
read the micromod777 in developing for h811 section rom 20o.... they talk about no sound and camera bugs.. i think i read thers a fix...
[T-Mobile LG G4] orells:
Thanks for the point in the right direction. All i had to do was use LGup and use "refurbish" to flash a stock 20o kdz and then use "upgrade" to flash a stock 20i kdz and all went back to normal.
[Redmi Note 2 Q&A, Help & Troubleshooting] Clangers:
I am new to xda so apologies for simple question. I am currently running MIUI 8 Global Beta 6.7.21

Can I install a custom rom in place of this? If so what is the easiest method?

Thanks
[Redmi Note 2 Q&A, Help & Troubleshooting] PytSkee:
Yes, you can install different ROM's. Search up WinDroid on XDA, download it, install TWRP 3 and pick out whichever ROM you prefer.
[Redmi Note 2 Q&A, Help & Troubleshooting] kiko9895:
First, you need to root your phone, try King Root or installing the Chinese ROM which comes with built-in root, you can do this from the updater without needing root.

Then install Flashify from the play store and dowload TWRP recovery for Redmi Note 2 from this forum. Flash the recovery with the Flashify app, it's pretty straightforward.

Then you just need to download your custom ROM of choice and reboot to the recovery. Before flashing a custom ROM, backup is recommended. Just follow the instructions given in the ROM topic and you're good to go.
[Redmi Note 2 Q&A, Help & Troubleshooting] Clangers:
Thanks for your help, now up an running with CM12.1 and loving it compared to stock MIUI.
[Redmi Note 2 Q&A, Help & Troubleshooting] kiko9895:
Glad I could help. :)
[OnePlus X Themes and Apps] nithinsureshak:
Hey guys. I'm new here. My newly rooted OnePlus X 's stock camera app got accidently uninstalled before creating a backup. I know there is a thread with link to two files on Google drive. Tried that but then again the camera app won't open(isn't respondin/opening) and sometimes says parsing issue. Need Help guys
[OnePlus X Themes and Apps] Mahesh8348:
Hi,

don't worry bro, u can re-flash stock recovery and flash stock firmware . Again if you want root root it again.
[OnePlus X Themes and Apps] nithinsureshak:
Thanks Mahesh . But won't that erase all the data in my phone ? And the warranty too as id be unlocking the bootloader . Can't we install the apk somehow ?
[OnePlus X Themes and Apps] Kéno40:
Never use direct root option. Do the full procedure with unlocking BL, install TWRP and then you can safely tweak your phone.

You should do it now if it's not already done.

But in your case, maybe if the flash go OK with that, then wipe caches & it should be OK (you shouldn't loose your data).

Or, you can first try to open the camera app info and erase data and cache, but your problem can be with lib so it won't work...
[OnePlus X Themes and Apps] Mahesh8348:
No your warranty still acceptable (Bootloader unlocked oneplus accept) . but you loose your apps and apps data , internal storage still remain . if you want install another camera go head and install google camera and others .
[OnePlus X Themes and Apps] nithinsureshak:
Okay. Then how should I unlock the bootloader and install twrp ?
[OnePlus X Themes and Apps] nithinsureshak:
Thanks Mahesh. I don't mind losing some app and data. How to unlock the BL and install TWRP on my OP X?

Thanks
[OnePlus X Themes and Apps] Mahesh8348:
First. Without root how would you unistalled camera app

Please go through the link and follow instructions .

https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/

Link for unroot and back to stock rom (OOS)

https://theunlockr.com/2016/02/17/how-to-unroot-the-oneplus-x/
[OnePlus X Themes and Apps] nithinsureshak:
My phone is already rooted. But I just didn't unlock my BL and install any TWRP software.
[OnePlus X Themes and Apps] Mahesh8348:
can't install twrp without unlocking the bootloader . How would you root without unlocking bootloader?
[OnePlus X Themes and Apps] nithinsureshak:
I installed KingRoot app and ran it. It rooted my phone. Then I replaced it with super SU
[OnePlus X Themes and Apps] nithinsureshak:
I rooted my phone using KingRoot and replaced it with SiperSU
[OnePlus X Themes and Apps] nithinsureshak:
I rooted my phone using KingRoo! and replaced it with SiperSU
[OnePlus X Themes and Apps] Mahesh8348:
ok. factory reset u r phone , unlock the bootloader , flash twrp, and flash SuperSU thats fine .

please follow the steps in the guidance .
[OnePlus X Themes and Apps] nithinsureshak:
If I factory reset will I lose my root ? And will I get my lost app ?
[OnePlus X Themes and Apps] Mahesh8348:
No problem bro.. u can flash twrp and super su as link i provided . That is better way to flash and root your phone. through twrp u can back up and u can do what ever u want with your phone . i suggest this way.
[OnePlus X Themes and Apps] Kéno40:
Unlocking BL will erase your data and apps.
[OnePlus X Themes and Apps] Tiongkia:
Yes. Data will be gone.

The trick use flashy tools to flash twrp when bl is locked. Go TWRP backup. Then unlock bl. After that all dat gone, use twrp restore back. I did before.
[Android Apps and Games] saschb2b:
Chat 4 GO

https://play.google.com/store/apps/details?id=com.wertarbyte.chat4go
​

It's a location based chat system for people who play Pokemon GO and are missing the communication feature known from Ingress.

We wanted to make this a cross plattform exprience so we created a nodejs react website and embedded that into a webview activity for android.

No registration needed. Just login via google or facebook and chat on!

This is our first application for android so every feedback is welcome.

Also available in browser: https://chat4go.com

Current features:

Login via google or facebook

Automated chatrooms creation with your gps location (reverse geocoding)

Emoticon support

URL support

Show unread messages next to chatroom name in menu

Show online user count next to chatroom name in appbar

Current Bugs:

Facebook login is broken

Empty chatroom list from time to time

GPS will sometimes not trigger in app (web is fine)

Features on our todo list:

Private chatrooms

Public chatrooms

Friendlist

Emoticon picker

Multi language support

You tell us
[G3 Q&A, Help & Troubleshooting] Ainz_Ooal_Gown:
Every AOSP/CM rom i try has this problem where when i'm playing music on my wired headphones and a notification happens or i like something on Facebook, it completely interrupts my music and makes some sound come out of the speaker. Everyone around me can hear it when this happens and the only solution i can find is turning notifications off or turning down the notification volume, where as in a stock based rom it only lowers the media volume and plays notification and doesn't interrupt can someone help me replicate this in AOSP/CM roms?
[G3 Q&A, Help & Troubleshooting] Ainz_Ooal_Gown:
so no one?
[P3600 ROM Development] tiburone:
I've made a search, and i didn´t find anything about this:

Anytime we install a new rom the imei changes, I'm i correct?

Anyway to go back to old imei? The imei changes and the programs with serials don't answer anymore. I can't ask for new serials anytime i make some changes. The sellers are already saying i'm crazy!!!

Is that possible to keep the same Imei every time we change rom.

Thank you. Help will be apreciated
[P3600 ROM Development] jmermel:
IMEI change

I believe that mun_rus rom holds the IMEI
[P3600 ROM Development] Olipro:
the IMEI does not change, the last 2 digits which indicate the firmware revision change... these are NOT part of the physical IMEI
[P3600 ROM Development] tiburone:
How do you explain, everytime a change rom, the program tells me it's not registered? I have to ask for new serials to access the program.

What can i do to avoid that?
[P3600 ROM Development] tiburone:
any help. please!?
[P3600 ROM Development] Antzzz:
Are you certain that the programs are using the IMEI as the key for the serial number check?

In my experience most Windows Mobile programs use the device name as the key - as they are usually designed to run on phone and non-phone devices (which don't have a IMEI).

So after you re-install the program try changing the device name to the same as it was previously and then enter your original serial number.
[P3600 ROM Development] tiburone:
Thank you antzzz. I'll try that:)
[P3600 ROM Development] zeph:
which program?
[P3600 ROM Development] sickboy555:
some programs use the user name or the device ID itself.

The device ID can change according to the ROM.

I have fist hand experience with this in TomTom Traffic - flashing every WM6 ROM except mUn's TE changed the device ID from the original WM5 one.
[P3600 ROM Development] tiburone:
any chance to avoid that? Or restore the previous ID?
[P3600 ROM Development] sickboy555:
no- the device ID is set by the ROM and some iteraction with the phone.

You have to go back to a ROM with the same ID. For Me mUns TE for WM6 had the same Device ID as WM5 which came with the phone.

All other WM6 ROMs give another device ID (and I heard that some give a new ID randomly after hard reset! Awful bug.
[P3600 ROM Development] dan-htc-touch:
how does one read their device id so i could know if it changed after a flash?
[General Accessories] NikosKont:
So I'm about to get the Samsung Galaxy A5 (2016 version) and I want to get a case. I have found a couple that I like, but I don't know about their quality. I hope you can suggest some reliable cases
[General Accessories] frumy:
I'm wanna too a reliable case :)
[General Accessories] Femmetechstic:
My dad has a Spigen case he got from Amazon (I think), he seems quite happy with it :)
[General Questions and Answers] raikas25:
Recently got this rooted galaxy s6 edge with a problem, when I turn on wifi and connect to my home network it keeps restarting till I do factory reset and cache wipe, but the problem still didin't fix. I've tried using odin but the phone completely just kept restarting. Any help would be fine :) Thanks in advance
[Android Apps and Games] dario456:
Dramatic graphics and my favourite running game play. Just going to try it now.
[Android Apps and Games] gruncirius:
New version 1.01

WHAT'S NEW

---- Reduced starting speed

---- Fixed balance
[Android Apps and Games] gruncirius:
New version 1.03

---- NEW Menu

---- The ability to disable Ads

---- Reduced starting speed

---- New comfortable dynamic camera

---- Fixed balance
[Android Apps and Games] gruncirius:
Update to version 1.0.4

[IMG="New Icon"]http://cs5-2.4pda.to/8695719.png[/IMG]

On Google Play​

https://play.google.com/store/apps/details?id=com.bullzuggames.aliceruner

WHAT'S NEW

---- Fixed balance

---- Some blocks fixed

---- Highscores system

---- NEW Menu​
[Android Apps and Games] Eyhen:
Highscores are awesome, but the game shows only 5 scores. Do you want to increase it?
[Android Apps and Games] gruncirius:
Yes. Highscores will be extended in the next update.
[Android Apps and Games] Fereze:
looks nice

nice game with awesome graphic
[Android Apps and Games] gruncirius:
Thank you :)
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
After unlocking bootloader my device shows screen like scanlines on boot - recovery - droidboot
[Zenfone 5 Q&A, Help & Troubleshooting] TechNova:
I guess u flashed a wrong boot img..

try to connect the fone in that state and flash a stock boot image via adb fastboot....
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
this is not about boot.img. With locked bootloader my phone works normal
[Zenfone 5 Q&A, Help & Troubleshooting] leonardohenrique10:
Download this: http://xdaforums.com/attachment.php?attachmentid=3383056&d=1435562997

Extract in fastboot folder

Enter in Fastboot mode

Connect your phone to USB

type: fastboot flash splashscreen splash.bin
[Zenfone 5 Q&A, Help & Troubleshooting] kihope12:
yes, he flash bad splash.bin
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
i think this is about my device model "z002". i tried bootloader unlocker app from asus. it makes splashscreen white but still same issue
[Zenfone 5 Q&A, Help & Troubleshooting] paktepu:
try unofficial unlocker
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
i took screenshots with unofficial unlocker
[Zenfone 5 Q&A, Help & Troubleshooting] paktepu:
i dont know if z002 is different from another z6. As i know they have same ifwi in z5 ifwi zip. Get the newest ifwi.zip for lock and if.bin for unlock.
[Zenfone 5 Q&A, Help & Troubleshooting] dmilz:
Would love to have the link from where you downloaded your z002 boot loader unlock tool.

Been searching for years on how to unlock bootloader for z002 ZenFone 6

Q0kHan
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
use any bootloader unlocker for zenfone 6 they all works but you have to flash jellybean fastboot first
[Zenfone 5 Q&A, Help & Troubleshooting] dmilz:
thanks . I wouldn't mind being spoon fed as to where i can

Download the jellybean firmware or jb fastboot.
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
Here
[Zenfone 5 Q&A, Help & Troubleshooting] dmilz:
thank you:D
[Zenfone 5 Q&A, Help & Troubleshooting] dmilz:
am back again, flashed jellybean fastboot.

after bootloader unlock phone shows only coloured lines when boot to fastboot, recovery even to system. any further help?:confused:
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
Do you read first post ? That is exactly same problem with me
[Zenfone 5 Q&A, Help & Troubleshooting] dmilz:
i see. We are on the same boat .

Hope a solution/workaround will be found.

Thanks for your time
[Zenfone 5 Q&A, Help & Troubleshooting] q0kHaN:
https://xdaforums.com/android/development/bootloader-zenfone-6-a601cg-bootloader-t3569976
[General Questions and Answers] mrgw98:
I have a rooted LG G4 on adroid 5.1. I am wanting to change my loading wheel to a gif but do not know how. Can anyone help? Also would anyone be willing to make an app to help others with this too to make it easier? Thanks in advance!
[Huawei Watch] imucarmen:
Everytime I wake my watch "OK Google" appears for a few seconds on the main watch face right below the 12 o' clock hour number. How do I disable this because it's annoying me. I've looked all over the wear app and the watch settings but can't find anything to disable it. I'm sure it's easy and I just keep overlooking it.