yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] mikey williams:
Some success with AEX 7.3. I've clean Flashed with Pico gapps 10 and Magisk and now installed a number of apps. No reboots or WiFi drops for a couple of days. And the rom is very snappy. I haven't used camera or Bluetooth.

I have mesh WiFi (deco 4) and it suggests that older devices might have problems with what they call fast roaming. So I switched it off and disabled mesh for the Samsung s2. Maybe that accounts for the greater stability. Will now install some more apps and see what happens.
[Galaxy Tab S2 Android Development] bmwdroid:
@mikey williams good to know bout AEX.

You've tried LOS 17.1 already?

Fyi The only way I could my T810 get to start was to use download mode button combo.

No reaction to any other button or combo before that and I feared it had died.

Still had 40% capacity when finally starting but didn't show anything either when attached to charger or PC.
[Galaxy Tab S2 Android Development] mikey williams:
It's now been running perfectly for 3 days with no WiFi drops or random reboots. So I'll be sticking with this rom. It does everything I need and is pretty snappy. My thanks to the developers.
[Galaxy Tab S2 Android Development] 93starletgt:
AEX 7.3 is running perfectly on my T710. No rebots, no WiFi drops. Is there any way I could install it on my T713?
[Galaxy Tab S2 Android Development] mikey williams:
Now been running for a couple of months. No problems at all.

Great stuff 👍

I guess security updates might be useful but otherwise excellent.

Thanks again to the developer.
[Galaxy Tab S2 Android Development] sergiofo:
Where did you get 7.3?
[Galaxy Tab S2 Android Development] mikey williams:
There was a link given here a couple of months back, around post #137
[Galaxy Tab S2 Android Development] templario1492:
Could you send me the link of the latest version of A9 please
[Galaxy Tab S2 Android Development] templario1492:
7.3 or 6.4????
[Galaxy Tab S2 Android Development] mikey williams:
7.3
[Galaxy Tab S2 Android Development] pigcake:
Is there a 7.3 version for the 710?
[Galaxy Tab S2 Android Development] durv:
Can I get a link to 7.3 for gts28wifi? It would be very much appreciated.
[Galaxy Tab S2 Android Development] d4ri88:
Is there a 7.3 Version for the T-815?
[Galaxy Tab S2 Android Development] keyap:
Anyone got a link to the final 6.7 (Android 9) build for the T710?

I can find some Oct 2019 versions on page 1, but later posts suggest there's more recent ones

Thanks
[Galaxy Tab S2 Android Development] cittaslow:
I want to download this rom for my T710. But on the download page it gives an error after pressing the download button. (OOPS! Mirror not found.) How can I download it?

Edit: Sorry, my bad. It worked after a few hours.
[Samsung Galaxy A6 Questions & Answers] DARKSIDERS_2012:
Hello friends, I've been trying to fix a giant problem with my son's cell phone for three days ... He asked me to rotate it, but I brickee it, I comment on what happens and what I did:

specs:

Glaxy A6 + (SM-A605GN)

1-install TWRP by ODIN (Correct installation)

2-Install TWRP files "force_encryption_disabler, RMM State Bypass and non-verity-opt-encrypt (I think here is my mistake, since I do not know the functions of these files, in my time of Flasheo does not exist) I take it out of this tutorial: androidinfotech.com/root-samsung-galaxy-a6-plus-2018-sm-a605f-fn-gn-pie/[/url])

Error 3-First; I didn't have access to the internal memory in the TWRP, so I followed this tutorial youtube.com/watch?v=bqyVQCGlyqs[/url]) to change the partition system so I could access the internal memory correctly

4- Install the Magisk correctly through the TWRP

5- Restart (And my hell began) ...

a- TWRP informs me that I did not have OS installed on reboot

b- When restarting the screen it tells me: Set guarantee bit: Kernel (in yellow)

c- Try to install the Firmware Stock by Odin, but I can't, it doesn't throw me an error, but it doesn't install anything at all, IT KEEPS ME THE TWRP INTACT

d-Download a Modified ROM, the installation by TWRP and it was installed correctly, but the SIM card does not work (I assume it is because it has a different modem) and I get an error for almost everything L

I want to go back to the Stock ROM but ODIN does nothing ... Please I need your help.

I can access Download and TWRP mode.

discuss the translation ...
[Samsung Galaxy A6 Questions & Answers] DARKSIDERS_2012:
Friends, any ideas ?? ... any help is appreciated.
[Samsung Galaxy A6 Questions & Answers] tutul2336:
As you already flashed twrp, so i think you know how to go download mode. Just see any youtube video how to flash stock rom on s8/s9. Download your latest firmwere from sammobile or samfrew and flash. Procedure is same as s8 or s9.
[Samsung Galaxy A6 Questions & Answers] DARKSIDERS_2012:
Friend, that's the problem, ODIN doesn't let me install the Stock Rom, at the end of the flash process with Odin, the phone remains intact (with the TWRP intact)
[Samsung Galaxy A6 Questions & Answers] tutul2336:
What kind of error? or it flashes perfectly? Give us something.. Photo of odin and your phone's download mode screen...
[Samsung Galaxy A6 Questions & Answers] GuestX01058:
When you first time booted twrp, you needed to click on wipe > format data. This will decrypt your phone (and it wipe your internat storage) then you can flash rmm and no verity. After that, click on reboot > recovery and then reboot > system (or flash magisk). Recommended to flash latest rmm and no verity. :)
[Thinkpad Tablet Accessories] OldTacoman:
Hi

I purchased a Tab4 10plus with a bluetooth keyboard case. One of the plastic clips that holds the case to the table broke the second time I used it. I have gone over the Lenovo website carefully and can't figure out how to file a warranty claim. Does anyone have information on how to file a claim? The website seems to be structured to discourage claims.

Thanks

John
[Thinkpad Tablet Accessories] OldTacoman:
Finally got hold of support for the keyboard case. They offered to sell me a replacement at full price. Claimed it was abused and that was the best they could do. I intend to send it back for a refund. This will be the only and the last Lenovo product that I purchase.
[Thinkpad Tablet Accessories] lkthomas:
I have the keyboard case for 6 months, that plastic clip wouldn't break easily, but I think you could buy a replacement unit for around 10 bucks, why not search on eBay ?
[Samsung Galaxy Note 8 Questions and Answers] munirshah77:
Hi. I bought a used note 8 n950f exonos on orea and updated it to pie with the latest september update. I want to install twrp recovery, root it and use custom roms but latest bootloader won't let me install it. When I try to install twrp using odin, I get the error "only official binaries are allowed to be flashed". When I try to flash an older stock firmware using odin, I get error "sw rev check fail bootloader device 7 binary 3". I have OEM unlock enable and USB Debugging enabled as well. Is there any way to install twrp recovery? Desperately waiting for your help
[Samsung Gear S3] CaptGrumpy:
I kinda feel the fool. :eek:I deleted the background images from my gear s3 frontier. Is there anyway to replace them, or to add other backgrounds?

TIA!
[Touch GSM ROM Development] dsixda:
Universal Page Pool Changer - for Elf/Elfin only

This tool provides support for both Elf/Elfin and 1.1x/2.2x/3.xx ROMs, so it is a true universal Page Pool Changer. It will write to the appropriate area in memory, reboot your device and then read back the new value. This method is much faster than changing the page pool in the ROM file by hand, which requires re-flashing the entire ROM.

To use this: Unzip the attachment, connect your device to ActiveSync and then run pp.bat.

USE AT YOUR OWN RISK. BETA VERSION ONLY SO FAR. ENSURE YOU HAVE THE

USPL

INSTALLED!

This program would not have been possible without people like Swiftblade, tabi13, ayyu3m, htctouchp, Noonski and other cookers providing the offsets/strings to write to as well as testing it.

Posts for this Universal Testing PP Changer starts here:

http://xdaforums.com/showpost.php?p=2585064&postcount=123

UPDATE: Now working with all 3.xx ROMs, INCLUDING 3.xx ROMs with ULDR removed.

STILL TO DO: 2.xx ROMs with ULDR removed

SCREENSHOT #1 - Changing Page Pool:

SCREENSHOT #2 - Reading back the new value after reboot (reboot time is partly dependent on the new page pool size):

I will need feedback for the following:

1) Elf with 2.2x ROM

2) Elfin with 2.2x ROM

3) Elf with 1.1x ROM

4) Elfin with 1.1x ROM (NOTE: don't flash a 1.1x shipped ROM on your Elfin! Use just the OS ROM)

5) Elfin with 2.81 ROM*

6) Elf with 3.xx ROM

7) Elfin with 3.xx ROM

*It looks like Elfins that come installed with a 2.81 stock ROM do not contain the Page Pool values at the expected locations. If you however flash the dumped 2.81 ROM to a non-2.81 Elfin, the PP is read correctly on the non-2.81 Elfin.
[Touch GSM ROM Development] Ameet:
cool walkthrough brother.. cool.. keep it up.. hope to see a nice pagepool changing software someday by some programmer ;)
[Touch GSM ROM Development] !Aman!:
thanks for such an explanatory post bro :)

i've one question though. i modified the PP of my ROM to 16 MB and after flashing just when i got the prompt for screen alignment, i got some errors showing some exe's not able to run namely replog.exe, tskschedule.exe and 3-4 others. i didnt modify anything else in the ROM.
[Touch GSM ROM Development] Ameet:
how is the he value calculated? i want a 6mb pp for which i dont know what the hex value would be.. is there a calculator or something? so i wont have to ask each time ;)
[Touch GSM ROM Development] Swiftblade:
Hi htctouchp.. did you change the "03 15" at both occurrences in the .nbh files. The patterns should only appear twice, if not somethings is very wrong.. just curious.. you use os.nb or .nbh file?
[Touch GSM ROM Development] !Aman!:
actually i tried this just 5 mins before ur post, in the manner explained by dutty(and ameet), first edited the S000 of nk.exe and then modified the os.nb and while editing the os.nb, i found this pattern just once, not twice.
[Touch GSM ROM Development] Swiftblade:
Some numbers in hex:

"00" = 0

"01" = 1

"02" = 2

"03" = 3

"04" = 4

"05" = 5

"06" = 6

"07" = 7

"08" = 8

"09" = 9

"0A" = 10

"0B" = 11

"0C" = 12

"0D" = 13

"0E" = 14

"0F" = 15

"10" = 16

"11" = 16+1 = 17

"12" = 16+2 = 18

"13 = 16+3 + 19

.....
[Touch GSM ROM Development] Ameet:
cool.. so for 4mb pp, i have "04 16"

for 6mb pp, i should have "06 16"

and for 8mb pp, i should have "08 16"

rite? :) thanks for the prompt reply brother
[Touch GSM ROM Development] Swiftblade:
hi htctouchp... the string pattern in Kaiser is different from ELFin and that explained why you found it once. So you probably edited some .exe program instead of pagepool.

Search the string pattern as given above and try it again. Should work and forget about nk.exe, just do it on the .NBH file straightaway and re-flash it back to your device. Cheers.
[Touch GSM ROM Development] !Aman!:
no bro...i meant i only used that method..but the string which i used was the same as the one mentioned by u.
[Touch GSM ROM Development] Swiftblade:
What ROM are you using? 1,17.xxx or 2.20.xxx ??

If you are using the 2.20.xxx rom and editing the .NBH file, the addresses found should be at 0X438DC and 0X353637... try searching again...
[Touch GSM ROM Development] !Aman!:
yup, the strings are at these very addresses mentioned by u bro and i use 2.20.xxx ROM
[Touch GSM ROM Development] pkoper:
Excellent.... have been waiting for this. Good job!
[Touch GSM ROM Development] zeflash:
THANK YOU!

thank you!

Finally I am able to get new ROMs with proper 4MB pagepool on my puny Elf!!!

Tried the trick on Ameet's 4.01 UC rom, and it worked.
[Touch GSM ROM Development] Swiftblade:
We are here to share and it's good to know that it is of help to you bros.... Enjoy the true pagepool... keke c",)

How did it go? Manage to solve the problem? I re-look your problem and it might not be related to the pagepool changing.

I suspect one or two things: UC and/or SQM removed from your Rom... ?? And again I may be very wrong.... Cheers.
[Touch GSM ROM Development] Ameet:
even i can find only one instance of the hex string if i try to edit the nbh or nb file directly.. but i have the sqm removed from my rom, is that why?
[Touch GSM ROM Development] Swiftblade:
They are 2 separate issues. I'm saying that if SQM module in WM6.1 is not removed properly, it can cause some of the .dlls not loading as mentioned by Aman.

Ameet bro... you mean you can only find one instance of the hex string in your roms? Only possibility of that happening is when the nk.exe in the XIP was removed during porting.... Now this get me thinking, maybe we need to hex edit only once, i.e. the higher offset at 0X353637....ummh...:confused:

The one instance of hex string is at the higher offset address in your case?
[Touch GSM ROM Development] Ameet:
yes it is the highest offset.. but i tried this trick on a rom in which i had already hex edited the sooo in nk.exe and then after cooking i could find only one instance.. but the trick of directly editing nb file didnt work for me (or maybe i did something wrong, which i'll try again) but the nk.exe trick and then nb files worked like a charm for me
[Touch GSM ROM Development] zeflash:
Well, I found 2 instances of the hex chain in your 4.01 rom (nbh direct edit). You might want to check again ;)
[Touch GSM ROM Development] dsixda:
0, 12 and 16 are the best for Elfins, if you're talking about time it takes to start up a program (and not necessarily the available RAM). I set my Task Manager to terminate the process upon closing, so I don't care about available RAM.

I'm not sure about the optimal value for Elfs though. Just experiment with the values.. the "Reboot Time" benchmark should give you an estimate.

I get good times at 12MB for Blue Elves, but then 0MB is best for my Rogers stock ROM.
[Touch GSM ROM Development] insaned:
I'm right now updating the rom to the blue elves 5 veersion, to try it out, I'll see how it goes...

So you liked the default PP with blue elves then?

thks, for the help and for all the other usefull programs you provided! ;)
[Touch GSM ROM Development] andrei.nica:
small bugs

while running the program from xp on my elf I receive a message that "msvcr71.dll" cannot be found. googled it, downloaded - all ok, except for when setting 16 MB PP on my Elf, Pdaviet ROM - after a lot of device rebooting occurs. so I change back to 12 MB - all ok till now - great tool, guys!
[Touch GSM ROM Development] dsixda:
You're welcome!

Yeah I liked the default 12MB on Blue Elves best :)
[Touch GSM ROM Development] dsixda:
Not sure about the error you got, but for Elfs, try not to go higher than 12MB.. I'm not sure if it will work properly since they don't have a lot of memory compared to Elfins. For Elfins however it is ok.
[Touch GSM ROM Development] hehehi:
hi snior,, how to check our pp value on elf?

thx
[Touch GSM ROM Development] dsixda:
Just run the program and it will tell you the current PP value.
[Touch GSM ROM Development] grox:
What is the best PP for the UCE ROM version 14.01?
[Touch GSM ROM Development] dsixda:
UCE is fast enough, isn't it :D

You should try to experiment and compare the boot times.

For Elfin, I prefer the default 12MB most of the time. Depends on the ROM.. if it is a quick ROM already then try 0MB. If it is a slow ROM with a lot of memory usage requirements, then go for 12MB or even 8MB.
[Touch GSM ROM Development] kokotas:
PP Patcher(for cooks) - [BETA2]

I'm not good in programming but here is a simple pp patcher!And when I say simple, I mean REAL simple!

All it does is hexediting certain bytes!

Not able to search for hex string pattern, but able to edit it if the address is known!

For example for the 2.2x Roms the pattern's (03 15 A0 03 02 15 A0 13...) address is known:

For the OS.nb

1st address:

first byte 03 @ 0x0436BC

2nd address:

first byte 03 @ 0x035327C

For the RUU_Signed.nbh(

ONLY OS!

NOT WITH ANYTHING ELSE LIKE IPL,SPL,SPLASHSCREEN,etc!)

1st address:

first byte 03 @ 0x0438DC

2nd address:

first byte 03 @ 0x0353637

So I hope you get the way it works.

I have included it in the Hybrid kitchen, but better have it as a standalone tool too!

Any feedbacks are most welcome!

It could be implemented into the final step of any kitchen if you have a favorite pp size that you always use

and you know the correct offsets to edit.

eg:Speaking for a Kitchen based on bepe's Extended kitchen, having OEMXIPKERNEL from 2.2x ROM and choosing 8MB for ELFIN & 4MB for ELF

Having the hexalter.exe in your tools dir

add in your script after the creation of the OS.nb :

..
..\TOOLS\ImgfsToNb imgfs-new.bin OS.nb.payload OS-new.nb -bigstoragemove
..\TOOLS\hexalter OS-new.nb 0x0436BC=2,21 0x0436C0=4,22 0x035327C=2,21 0x0353280=4,22
..

and your final OS.nb is already patched with the PP_size you prefer!

Regards!
[Touch GSM ROM Development] ayyu3m:
nice. no more need to go into hex editor

:D thankx a lot man. this will come in handy very much
[Touch GSM ROM Development] dsixda:
Awesome work. This is a very good tool and will prevent mistakes...
[Touch GSM ROM Development] ayyu3m:
WORKINGS LIKE A CHARM!! JUS TESTED :D

Thankx Man!
[Touch GSM ROM Development] vaxoie:
When I'm change PP on my Elf to 4mb (old 2mb) I'm lost contacts on my People page in manila TF2D. Only for statistic , no problem ;)

Very nice program, thanks.
[Touch GSM ROM Development] flaviocc:
Hi,

The application can not see my PP, the error of missing dll.

And asked to reinstall the app. It happened with rom 3.1 and 3.1.1 Onyx.

Tks,
[Touch GSM ROM Development] !Aman!:
The PP HEX string is changed now if someone is working with the latest 3.07 ROM as his Base ROM for OEMXipkernel. the new Hex string is as follows:

03 15 A0 03 02 15 A0 13 00 10 83 E5 [B][color=blue]62[/color][/B] C2 FF EB

The offsets have changed in new the kernel, so the current PP changer needs to be modified for 3.07.XX ROMs with new offsets.

Also, if the cooks are using old (2.2X) os.nb.payload for cooking the new OEMXipkernel, then the first HEX string would be same as the previous 2.2X. And if version 3.07 os.nb.payload is used for cooking then the PP depends upon the new HEX string and new offsets.
[Touch GSM ROM Development] dsixda:
Thanks a lot Aman, I will try to fix the PP changer later.
[Touch GSM ROM Development] dsixda:
Universal Page Pool Changer now updated for 3.xx ROMs!!!

http://xdaforums.com/showpost.php?p=2274573&postcount=2

Please note, however, it will only work with 3.xx cooked ROMs that were built with a 3.xx ROM's OS.nb.payload. (e.g. My Onyx 4.0 Beta 1 most likely will NOT work, but future ones will, because I will build them properly next time ;) )
[Touch GSM ROM Development] !Aman!:
what if we only change the 2nd Hex string and leave the 1st one as such? doesn't it change the PP?
[Touch GSM ROM Development] dsixda:
The program will give an error if the 3.xx is built with the 2.xx payload. I don't know how it would affect it (or if it would work as expected) with that combination.
[Touch GSM ROM Development] ayyu3m:
i tried changing one set as u suggested bro

but it doesnt work..and pagepool remains the same
[Touch GSM ROM Development] dsixda:
How do you know it remains the same?
[Touch GSM ROM Development] !Aman!:
oh..i was thinking that only 2nd HEX string should control the PP coz thats where the XIP (hence the kernel nk.exe) is.
[Touch GSM ROM Development] dsixda:
I think we should just give an error if the 2.xx payload is used in a 3.xx ROM. It's bad cooking practise anyway ;-)
[Touch GSM ROM Development] !Aman!:
yeah, but it would have been a lot better if changing the 2nd Hex string only did the job.
[Touch GSM ROM Development] dsixda:
We'll need to confirm if that really works... best way to tell is to change PP to 1MB and see if it slows down really bad ;-)
[Touch GSM ROM Development] !Aman!:
why not just observe the program memory?
[Touch GSM ROM Development] dsixda:
Oh yeah.. nevermind. Pardon the brain cramp, I should go to bed now.
[Touch GSM ROM Development] alx75:
Yup Very Correct:p Cos Just Use Your New PPC IT WORKS
[Touch GSM ROM Development] !Aman!:
are u sure u did it properly? i just tested it by changing only the 2nd offset PP value in my ROM which i've cooked using payload 2.2x and new OEMxipkernel, and i can see that the PP changed successfully :D

PS: i confirm changing the 2nd HEX string should be enough. Pls test it out guys.
[Touch GSM ROM Development] !Aman!:
nobody interested??? amazing :D!!
[Touch GSM ROM Development] dsixda:
HAha.. I could try but too lazy to go back to 2.2x cooking ;)

Ok how about this.. what if we use a 3.3x payload.. Do we only have to change the 2nd set of strings in order to really change the PP???

I mean maybe it is visibly noticeable that the memory has been adjusted for the new PP, but perhaps there are other things that weren't changed.. which may affect stability.
[Touch GSM ROM Development] !Aman!:
yeah only the 2nd HEX string needs to be changed, whatever the base ROM may be.
[Touch GSM ROM Development] dsixda:
Are you 100% sure? If your life depended on it? (I will buy a gun)
[Touch GSM ROM Development] dsixda:
Ok, the PP Changer has now been updated for ALL 3.xx ROMs.. thanks to htctouchp's findings.. as usual.
[Touch GSM ROM Development] Berfurd:
I just tried it on 4 Beta and I have IPL/SPL 3.07 on my Elfin. Works fine.
[Touch GSM ROM Development] dsixda:
Thanks for testing!
[Touch GSM ROM Development] Berfurd:
No problem!! :D
[Touch GSM ROM Development] !Aman!:
yeah i'm 100% sure, only the 2nd Hex string is responsible for PP. did u test it?
[Touch GSM ROM Development] dsixda:
I noticed a change in memory.. so it looked like it worked :)
[Touch GSM ROM Development] !Aman!:
good :). the PP changer can be simplified now, but i suggest u don't modify it as yet coz once we remove the ULDR partition from our ROMs the offsets will change again ;)
[Touch GSM ROM Development] dsixda:
It's already changed ;-)

Another thing I noticed ----

If you change the XIP from 19972 (the Elfin's XIP) to 19971 (the Opal one), and then build the ROM again, then one of the two 3.xx PP strings is missing.

EDIT: IF the ULDR causes the offsets to change again, it's not a big deal.. the script can check for that when I fix it later.
[Touch GSM ROM Development] !Aman!:
will have to change again, coz the 1st HEX string is going to disappear forever ;)

do u mean u used OEMXIPKernel form Opal?
[Touch GSM ROM Development] dsixda:
Yes I did.

I also noticed that changing the PP for XIP 19971 causes Manila 2D to not start up.

I think I'll go back to Elfin XIP 19972.
[Touch GSM ROM Development] dsixda:
PP Changer only looks at the 2nd hex string for 3.xx ROMs now.
[Touch GSM ROM Development] !Aman!:
using OEMXIPKernel from another device is never a good idea :). it has information specific to the phone.
[Touch GSM ROM Development] dsixda:
Not really, I used 19971/19971 SYS/XIP (Opal) for about a month without any stability problems. I ported the SYS though, so that it worked, but XIP was straight copy.

BTW (off-topic) do you know how to change the byte on 19972 so that it retains the real-time clock value? It looks like the address changed in the S000 file of the kernel.
[Touch GSM ROM Development] !Aman!:
2nd HEX string works for 2.2X based ROMs also. i have not checked the older ROMs though, but i'm sure it is same for them.
[Touch GSM ROM Development] !Aman!:
i know opal and elfin are almost same, but this part of the XIP is specific to the device hardware.

yeah i know, the kernel is changed now as per WM 6.1. u need to edit the hex byte at 0x45BDF now.
[Touch GSM ROM Development] dsixda:
Excellent, thanks.. I see 0A there. Did you decompile it?

I used XIP (straight copy) from other devices in previous ROMs, and it worked fine for me.
[Touch GSM ROM Development] !Aman!:
yeah, u have to disassemble to find out the correct code. there is no method otherwise to find out which is the correct offset. so change 0A to EA.
[Touch GSM ROM Development] !Aman!:
which other devices? kaiser, diamond etc? or just another Elfin's ROM?