yashsingh1/xdaforums huggingface dataset:
[8.9" Kindle Fire HD Android Development] ipipipipip:
Hi Jack, since last update I got some additional pieces working. Specifically: sound (and that was a brain-teaser for a long time) and LTE modem are working now. UEFI boot with u-boot implementation is functional.

Indeed 7-inch tablet may be brought-up with quite a low effort: lcd panel is slightly different, but there is a driver for it already in kernel, touch screen is also different. Apart from that rest of the stuff should work quite the same, that is usb, uart, wifi, bt, audio, backlight, keys, emmc, hdmi, with minor DeviceTree adjustments.

Same for u-boot: for basic functionality only a few pin-assignment changes are needed.
[8.9" Kindle Fire HD Android Development] Joonatnoon:
Hi,

For a relative arch Linux beginner, what resources would you point one to to be able to implement this on an OG kindle fire HD 8.9?

I'm decently comfortable on the command line, but once it starts getting deep in the kernel, I am a little more cautious..

Many thanks,

Jeff
[8.9" Kindle Fire HD Android Development] ipipipipip:
It depends on what you want to achieve. This kernel will happily work on any kindle fire 8.9 2012. LTE version just has an additional board with a modem on it, (and needs another Bluetooth firmware).

At some point, I created a bit more user-friendly image of Manjaro with LXQt suitable for dual-boot, but without hardware acceleration, it was too sluggish for any real use.

If you want to have some fun and do something useful at the same time, I'd suggest adding support for this device in postmarket os project.

The starting point is here https://wiki.postmarketos.org/wiki/Porting_to_a_new_device

If you encounter any difficulties, feel free to ask :)
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
Thanks for all this. I hope to port the 7 inch version (soho) to postmarketOS (am surprised you didn't want to get jem running it so you can have a nice touch interface).

Have you seen the attempts to get mainline drivers that interface with PowerVR SGX 5xx graphics firmware? Seems like one day there might be 3D working...

https://github.com/openpvrsgx-devgroup/linux_openpvrsgx

One more question - have all the changes you described been pulled upstream, so I can just fork from mainline, or are some important ones still not yet in, so I should fork your repo?

Thanks again for all your efforts - I am very excited as to how this will benefit soho development.
[8.9" Kindle Fire HD Android Development] ipipipipip:
I did get it run postmarket, but it was somewhat clumsy and not properly integrated into a build tree. Also, it seemed a bit clumsy to update-rebuild-flash-reboot firmware image after a change contrary to rebuilding some users-pace parts just on the device.

If only there was a non-android userspace driver for sgx544sc that is in 4470, inb4: ti still uses sgx544 in their new chips, but it is different.

Would be nice to have 3d, but I'm afraid that without major testing and bug fixing (on source code driver level, which is closed) It will be buggy as hell.

Nope :angel: . Clone my repo.
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
Hello again,

I've been trying to get a downstream kernel postmarketOS running on soho, and had noted the bootloader refused to load my kernel (just went to fastboot) unless I hexedited some zeroes (and some other data) at the beginning of my boot image (a technique required for the one custom rom available for it), after which it bootlooped. I see jem too requires some boot image manipulation to get cm11 on it (https://github.com/LineageOS/android_device_amazon_jem/blob/cm-11.0/boot.mk) - how did you get your kernel booting? I don't know much about the boot process, but I imagine there is some sort of signature verification Amazon cooked in that the hex data added at the beginning confuses.

Can I pm you?

Thanks,

Jack
[8.9" Kindle Fire HD Android Development] ipipipipip:
Hi, yes boot image is signed and verified, but at least on Jem there is a vulnerability in stock u-boot that allows to bypass the signature check and execute arbitrary code.

Not sure how it is done on soho, but, at a first glance, the exploit looks kinda the same (even addresses are the same).

https://github.com/TeamWin/android_device_amazon_soho/blob/cm-12.0/exploit.mk

On jem there is an image size check missing when loading boot image into ram. The boot.img header contains image size to be loaded, and thus if you load a large enough chunk you will overwrite current stack frame (and what's important - return address), thus after data is loaded bootloader will jump to user-specified address. The trick is to load your executable code (second bootloader in my case) into ram (put it somewhere at a known place in boot partition) and use that address to overwrite the stack.

One problem was that main boot partition is too small (8MiB) to contain a patch to overwrite the stack, thus initially it was placed somewhere at the beginning of system partition (with hopes and prayers that it will not corrupt ext4). But then I resized those partitions to 16MiB which is enough to fit everything.

If you don't want to bother with modifying bootloader, just retrofit those boot image creation makefiles.
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
Thanks - so how did you modify your boot image when you were tinkering with pmOS? Did you just replace the stock u-boot so no exploit was necessary? I thought x-loader would refuse to load any u-boot not signed with Amazon's keys? Sorry, you stated you put your second bootloader at an address in the boot partition. I'm just curious as to how exactly one does that when building pmOS.

Thanks,

Jack
[8.9" Kindle Fire HD Android Development] ipipipipip:
Who knows, there is actually no sane way to create simply flashable boot.img without resizing boot partition first, that I highly suggest you to do. Make a backup of all partitions and gpt table, practice a bit on a spare sdcard, boot twrp, remove boot partition, and what's after it, then recreate those with sizes as need (and don't forget to restore partition names, that's important). Also would be handy to increase system partition size on the way, by sacrificing userdata size.
[8.9" Kindle Fire HD Android Development] ipipipipip:
But, if you have working third party ROM, and don't expect to fiddle with bootloader, chances are you may get away with just dd-ing a few values and 2nd loader over boot.img postmarket builds (there is a package stage in linux-xxx target in postmarket's APKBUILD where you can put this code), and hope that magic value (stack smashing value) will not be overwritten while installing firmware
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
Thanks for this info. I've managed, through your help and others, to get a boot pmOS (on a downstream kernel). I'm in the process of merging my work, and the question is being asked of the boot hack, which I am hoping to get merged into postmarketos-mkinitfs package (not in an APKBUILD for soho) - are there any other devices that use a similar hack? If the answer is yes, I think it makes sense to include them in the same portion of code for future pmOS jem attempts - I know you didn't want to merge all your code, and that's ok, but could I make a request for one part of it? Please may I ask what exact shell commands you needed to run to amend jem's boot.img so that tricking the signature check takes place? For what it is worth, for soho I adapted the boot hack in the rom makefile to the below:

SOHO_HEADER_DATA='\x50\x03\x00\x00\x00\x25\xe4\x00'
SOHO_HEADER_SIZE=848
SOHO_HEADER_OFFSET=52
tempfile=$(mktemp)
dd if=/dev/zero of="${tempfile}" bs=$SOHO_HEADER_SIZE count=1
printf "%b" $SOHO_HEADER_DATA | dd of="${tempfile}" bs=$SOHO_HEADER_OFFSET seek=1 conv=notrunc
cat "${outfile/initramfs-/boot.img-}" >> "${tempfile}"
mv "${tempfile}" "${outfile/initramfs-/boot.img-}"

(I didn't need to resize my boot partition as I believe the hidden bootloader is stored in the recovery partition.) Anyway, thanks for all the help. I'm going to work a bit more on polishing my downstream port before turning my attention upstream, and copying most of your dts and relevant commits :)
[8.9" Kindle Fire HD Android Development] ipipipipip:
Nice (y), as for other devices: fire hd 2012 7" (IIRC it is called tate) is likely using the same hack, and that's it, it was an amazons bug so no other devices affected. You may assume that the commands for jem are exactly the same.

BTW, may I have a look at a merge request for postmarketos-mkinitfs, when you create it? I dug a bit, trying to find a nice clean method of wrapping boot.img after mkinitfs creates it, but didn't found any. The closest thing that exists are a few device-specific "sign" steps, which are almost exactly what we need, except that, I don't want to add more ugly device-specific checks in build scripts. Some generic field that names the tool for signing and a separate package that does that device-specific signature would've been the best IMO.

I guess It's time to rebase jem to a latest kernel, with a cleanup, coz a few things are broken now and need additional rework.
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
The Kindle Fire 2 (otter2) also appears to require a similar exploit. Merge request is here: https://gitlab.com/postmarketOS/pmaports/-/merge_requests/1995

Rebasing jem sounds exciting!
[8.9" Kindle Fire HD Android Development] Jack_Kekzoz:
I don't know if you've read the MR comments, but lead dev Ollie has just said what you said re device specific code. Time to rewrite then...
[LeEco Le 2 Questions & Answers] galets:
I built lineageos myself a while ago, and now I want to return back to stock lineageos. It gives me "can not flash on top of incompatible data". I'm pretty sure data is fine and going to work. Does anyone know what I need to tweak in it so that it does flash?

Just to be clear here, wiping the data and starting from scratch is not an option

*UPDATE* found one method. Edit following file : `META-INF/com/google/android/updater-script` commenting out following line with "#" such as:

# run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
[LeEco Le 2 Questions & Answers] SGH-i200:
How do edited this file inside the ZIP archive before flashing? Extract the file via 7zip on Windows?

Edit: I deleted the two lines that included the text "Can't install this package on top of incompatible data. Please try another package or run a factory reset" directly in the 7zip internal text editor and was able to flash the ZIP afterwards via TWRP! :)
[Moto E5 Questions & Answers] sleep_dealer:
I'm rooted on Oreo 8.0, Moto e5 play [james]

Tried a bunch of call recording apps in the Play store but no dice.

Anyone have better luck?
[Moto E5 Questions & Answers] Skrappy187:
How did you get root?
[Samsung Galaxy J7 Questions & Answers] padillaizzy:
When I attempt to turn on my Wi-Fi it won't turn on, any suggestions?
[Samsung Galaxy J7 Questions & Answers] Vipxpert:
Yeah ! Sometime I got that too ! I don't know why ! :/
[LG V20 Themes, Apps, and Mods] oto5:
flashable zip for recovery just flash it and enjoy your screenshots! :cool:

it works on my H990DS it should work on any V20!!

(its my first thread)

https://www.androidfilehost.com/?fid=5862345805528068265 <<updated link

let me know if it works
[LG V20 Themes, Apps, and Mods] BROKEN1981:
No, sorry but I don't trust it
[LG V20 Themes, Apps, and Mods] oto5:
I update the link

Than you can make it, just move LGNextcapture and LGQmemoplus in /system/priv-app/ (or make a backup and trust me :D )
[LG V20 Themes, Apps, and Mods] faeterov:
Works ok, thanks, I was missing this feature from my galaxy note 4.
[LG V20 Themes, Apps, and Mods] quinciebee:
I thought the link was superrrrrr suspect at first, but I tried it out and I was pleasantly surprised. It works perfectly and I now have scrolling screenshots on my V20. I know a lot of people have been looking for this feature, but may be apprehensive to try this particular download. Anyway, thank you [MENTION=9350438]oto5[/MENTION] for the update, and thank you [MENTION=4513677]rwilco12[/MENTION] for verifying the safety of the download.
[LG V20 Themes, Apps, and Mods] jcsx:
Not working

I tried flashing it and manually installing it. Either way didn't work. The quick memo app never worked. Always stopped when opening it.
[LG V20 Themes, Apps, and Mods] faeterov:
Did you flash from twtp?
[LG V20 Themes, Apps, and Mods] oto5:
1. backup

2. try to remove those folders with root file manager

/system/priv-app/LGQmemoplus

/system/priv-app/LGNextcapture(if there is one)

/system/vendor/overlay/com.lge.qmemoplus

3. flash it with recovery

OR

i make another zip for you it flashes lib file from LGnextcapture.apk into /system/lib/

https://www.androidfilehost.com/?fid=3700668719832236097
[LG V20 Themes, Apps, and Mods] oto5:
sorry for the first link and thank you to try it
[LG V20 Themes, Apps, and Mods] Koont:
Or y'all can try fooview. I've been using it's long screenshot over a year. Thanks Dev. for this mod
[LG V20 Themes, Apps, and Mods] jcsx:
Yeah. That's the one I have installed

---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------

I tried those and didn't work. Thanks for your help
[LG V20 Themes, Apps, and Mods] faeterov:
Im quoting the other thread with an installation method someone found, hope it helps uou.
[LG V20 Themes, Apps, and Mods] jcsx:
Thanks. Now the long screenshot is working but the quickmemo is not working yet. I will download another app like evernote to replace quickmemo+.
[LG V20 Themes, Apps, and Mods] Andy Chi:
I confirm this works on the T-Mobile H918 super v Rom 10u. Works excellent. Thanks OTO5!!!!
[LG V20 Themes, Apps, and Mods] dangkhoa02106:
My V20 T-mobile H918 Alpha Omega rom can activate Capture+ for extended screen shot. I just flash the zip file by TWRP. Thank you so much. But right now LG Quick memo is force close. :o
[LG V20 Themes, Apps, and Mods] faeterov:
It's working on superv20 4.1 on an H990DS (before I was using superv20 3.1).
[LG V20 Themes, Apps, and Mods] theUsualSuspexx:
So has anyone got this to work with quick memo?
[LG V20 Themes, Apps, and Mods] faeterov:
It works quickmemo+ on my H990DS
[LG V20 Themes, Apps, and Mods] harysviewty:
I think Oreo update has this feature built-in?
[LG V20 Themes, Apps, and Mods] Jc_master:
Yes it does.
[LG V20 Themes, Apps, and Mods] gandyprakoso:
how to use this? im using extreme syndicate (stock based nougat rom), i had flash the zip file, try take screenshot with button (power+vol down) no long screenshot option or such? thx
[LG V20 Themes, Apps, and Mods] oto5:
When you will press one of those buttons it gona ask you for long or standart screenshot, try it in google chrome cuz it doesnot work in every app
[LG V20 Themes, Apps, and Mods] Hadi99:
Just flashed this via twrp; extended screemshots work, but the quickmemo app crashes. Any waybto fix this?

(H990DS, Android 7.0 superv20rom)
[LG V20 Themes, Apps, and Mods] oto5:
1)copy your stock qmemo apk from system/priv-app/ to internal memory

2)decompile the apk file(you can use online decompiler)

3)decompile the qmemo.apk too from the zip file

4)open androidManifiest.xml in notepad++ from both decompiled folders

5)on nonstock androidmanifiest find 2 lines they allow qmemo to work with lgnextcapture

6)copy those 2 lines to stock androidmanifiest at the same place/line they were.

7)recompile the folder(make again apk file)

8)flash the zip file and replace the flashed qmemo with your recompiled file

im not sure 100% but it should work
[LG V20 Themes, Apps, and Mods] gandyprakoso:
yes it not work in some apps. working apps example is whatsapp
[LG V20 Themes, Apps, and Mods] minhduongtrung:
Does anyone know how to make it work on LOS 17.1?
[Upgrading, Modifying and Unlocking] ponmarcn:
Hi there

i am new here and i understand something but not all....

I have a Frenche Htc cruise with SFR sim and personalization....

probably is locked i don't know i cannot even see parameters for MMS, Internet etc.

My problems: i cannot use french language, i want gps usable

second problems: i can't understand all the procedure:

- how to backup rom image ?

- if i backup the rom all parameters (i.e. mms internet etc) can be saved and restored ??

- I understand how to flash it (instructions found here) what will be the best rom available in english ?

- how to restore parameters for surfing, mms etc ?

- how to do soft reset ?

- how to do a hard reset and what conseguencies ont the data ?

- how to make GPOS working ? where to load italy maps ?

where find and how to install a gps software ? (i have garmin maps is it possible to use them ?)

well if somebody can give me fool proof instructions and help i will really appreciate or i will have to sell this new phone because i understand french so bad......

thanks
[OnePlus 5T  Questions & Answers] 2fishbones:
Hi!

Whenever someone texts me on the Messenger app, I receive a notification. The ambient display portion of this notification usually shows the actual message received, but suddenly it changed to showing "Messenger is running. Tap for more information or to stop the app", rendering it completely useless, and quite annoying having to unlock the phone each time to see what people write.

Any help or explanation is deeply appreciated!
[Huawei Mediapad M3 Questions & Answers] Xalya:
i have a problem with updating my firmware on my mediapad M3.

i have downloaded the firmware with Firmware finder on the device, and i find BTV-W09C100B307 FullOTA-MF. firmware finder says i should be able to install it.

i copied the files to dload after i downloaded the files and restart, but it just say: "Software install failed". am i doing something wrong?

my unit has BTW-W09C100B302, but im fairly certain i have installed BTW-W09C100B303 but it is not displaying that, i have security patch 6 now 2017, b302 should not have that. i wonder if i could find B304 and B306 i could use incremental OTAs, with firmwarefinder i can DL B305 and B307, but i cant find b304 or b306, unless those don't exists?
[Huawei Mediapad M3 Questions & Answers] nawo69:
I'm on BTW-W09C100B302 with 1 Jan 2018 security patch but 303, 305 and 307 all fail to install also
[Huawei Mediapad M3 Questions & Answers] Xalya:
using FullOTA B303, id 108302 in firmware finder i managed to finally make so i showed B303 in the device, now i get update using the normal built in updater. updating atm and i hope it will work.

edit: i did unpack the B303 update first, else it did not work.

and the updating after using the built in updater worked, B307 now and security update juni 2018.
[Verizon Samsung Galaxy S8+ Questions & Answers] Kyles89:
Samsung Galaxy S8+

Version Info

Model SM-G955U [SS]

PDA FA70_G955UQU4ARE1

PHONE G955USQU4CRE1

P_S/N UNKNOWN

H/W REV1.0

CAL.ID 2017.04.18

UN (NOT SURE IF TO GIVE THIS NUMBER)

MEMORY 64GB

Ran ODIN v3.12.7 and rom that came with it. now stuck in Factory Binary, trying to flash back to factory, any help? Ive tried several roms and either get fails. or sometimes gets abl.elf

in upload mode

[ UPLOAD MODE ]

User press powerkey 7 sec (it does nothing)

--------------------

DDR Vendor :Samsung

SOC_HW_REVISION : 2.1

last_ns :0xff

Generaring Summary

>>General Info

>>DDR Info

>>DCVS Info

>>RPM

>>Trust2one

>>Hypervisor

>>APSS

>>MOdem

Done!

in Downloading custom rom

CARRIER: vzw

RPMB fuse blown

RPMB PROVISIONED

CURRENT BINARY: Samsung Official

SYSTEM STATUS : oFFICIAL

FRP LOCK: OFF

QUALCOMM SECUREBOOT: ENABLE

RP SWREV: B4(2,1,1,1,1) K3 S4

SECURE DOWNLOAD: ENABLE

DID : 205E53BE31CB

AFTER RUNNING ODIN AND FAILING THERES ANEW RED LINE

SW REV CHECK FAIL : [ABL]FUSED 4 > BINARY 1
[Verizon Samsung Galaxy S8+ Questions & Answers] Smithfolk4:
I am not an expert, but it sounds like you are trying to flash a bootloader that is an older version than the version 4 on your phone. I don't think you can downgrade the BL version. The fifth character from the end is the BL version. (e.g. G955USQU4CRE1) Also, you may need a newer version of ODIN.
[Verizon Samsung Galaxy S8+ Questions & Answers] Kyles89:
so could i just google a "verison 4 BL for s8+" or something along those lines?
[Verizon Samsung Galaxy S8+ Questions & Answers] Smithfolk4:
Yes. There are a lot of software versions available. If you use Updato you can search by model number and service provider (listed as region on Updato. I was able to find one with a version 4 bootloader. Similar to your version, but CRE9 at the end. It is an oreo version. Your phone is a model SM-G-955U when you search there. It might take a long time to download. I have sometimes had luck speeding things up by trying to restart the download. Sometimes it just takes a long time. Be careful when you are flashing if you have any desire to go back to a previous version. I am not sure of the limitations.

Another thing you could try that might be easier for you is to go to the JRKruse ROM thread here - https://xdaforums.com/verizon-galaxy-s8+/development/rom-t3771206 and use the instructions he has there to install the ROM. There is another rooted ROM that he has that may also work for you. He has instructions on what to do.
[Verizon Samsung Galaxy S8+ Questions & Answers] Noob at everything:
Hello, my galaxy s8 is stuck in rpmb provisioned and its boot looping, I can get to download mode, it doesn't say things such as fuse blown etc. How can I get out of the boot loop? Help is appreciated.
[Verizon Samsung Galaxy S8+ Questions & Answers] Alicxxx:
Did you find a fix? Im having a very similar problem. I don't see any stock roms with a v4 bootloader. The most recent seems to be a v3.
[Verizon Samsung Galaxy S8+ Questions & Answers] Alicxxx:
Fixed it the way Smithfolk said. I was using the combination rom FA70_G955USQU4ARE1 with a V4 bootloader. I used odin v3.13.1 and flashed verizion G955USQU4CRE9 from Sammobile including the bootloader and it fixed my phone.