yashsingh1/xdaforums huggingface dataset:
[HTC One Max] ody.zady:
Hi, on my MAX, the SD card didn't unmount constantly.

But my 32g SD card was unformat for three times since I bought One Max for 7 month.

these three unformat all happened with default ROM.

lost my data many three times.

Not sure if it was similar to your problem?
[HTC One Max] wcooper0077:
the problem is my sd card wont stay mounted it unmounts like three or four times then just stays that way
[G3 Q&A, Help & Troubleshooting] Herby213:
Hi guys, I don't quite now how to explain this, but I'll give it my best. I've had my g3 for almost two weeks now and I've started to notice very faint vertical lines on the screen when on a white background, I can see them right now while writing this. It also happens in the settings screen. I'm not certain if there's something wrong or if it's always been this way and I hadn't noticed. Has anyone else noticed this? I wouldn't even say the line have a colour, it's just an alternate of darkish and white lines. I could just be looking too close, but I'm not certain.

Also I have noticed a slight black blur when using knock code, like when you would touch an old lap top screen, although a lot fainter. It only happens in one little section of the screen, but I noticed it when using the white stock wallpaper. It only seems to happen when I tap for knock code and I have noticed it when I apply slight pressure to that area. I have been delicate with the touch screen since, but I don't believe I used much pressure in the first place.

Hope I explained it well enough. Anybody else noticed anything similar? Am I being paranoid and these things normal?
[G3 Q&A, Help & Troubleshooting] Nitemare3219:
There is large discussion on the "lines." I see them too, but think it is a result of the resolution itself. Nobody can say/prove what it is AFAIK.

If I press real hard on the screen in certain spots, it seems like I can replicate the second thing you're talking about. If yours does it when just lightly tapping, I'd exchange it.

Sent from my LG G3
[G3 Q&A, Help & Troubleshooting] Herby213:
Hi,

Thanks for replying. I'm glad that the 'lines' aren't just in my imagination. Can you point me in the direction of the discussion on the lines?

I bought the phone online, but took into the store today to compare it to their demo model. It definitely doesn't have the same issue when I tap it. The salesperson wasn't sure what it was but she's going to send it in for repair/replacement. It sucks... now I'm going to have to wait till I get it back. The shop said they would have replaced it on the spot if I hadn't bought it online but from the store too.

Hopefully they get it back to me quick.

I hope no one else has this problem.
[G3 Q&A, Help & Troubleshooting] WIIstpM:
I think it's not the resolution itself, it's more about the software or kernel or something, LG implemented an oversharping thing which makes texts appear too sharp, but it's not only about texts, it's about the overall display! Notice when you scroll through LG Health page, you can see the lines moving, or changing in visibility, etc..
[G3 Q&A, Help & Troubleshooting] CodyMetal:
I have the same issue on my phone. There are very faint vertical lines most apparent on white and green colors and they seem to be rainbow colored. I have seen this issue with the at&t, t-mobile, and sprint versions of the G3 which my friends have.

It's not caused by the over sharpening effect because even after I flashed a fix for it, it still appears.

Almost as if it's like one of those 3d card/poster effects.
[G3 Q&A, Help & Troubleshooting] Odeen_c:
Hi guys,

is there any news on any fix on this?
[G3 Q&A, Help & Troubleshooting] sblantipodi:
I have the same problem. Should I RMA my phone?
[Galaxy S III Q&A, Help & Troubleshooting] robadubdj:
Hi guys, i am a noob to all this so exuse me if this is a stupid question.

I have just rooted my Samsung Galaxy S3 GT i9300, I am currently running CM 11 and KitKat.

I was just wandering what the best kernel for me to use would be ? From reading a few threads it seems that this is something i should try to change following rooting.

If anyone has any advice on kernels or what else i should be doing following a root it would be much appreciated .

Thanks :cowboy:
[Galaxy S III Q&A, Help & Troubleshooting] Darkened_Sky:
sorry but "best rom/kernel/whatever... questions" are not allowed. you should try out some kernels for yourself (you can find all in android and original android development threads) and choose the best one which satisfy your needs. it is also the best way for yourself to learn what is important for an android device.

something you have to do after root: efs backup!!!

for more information read stickies
[Galaxy S III Q&A, Help & Troubleshooting] robadubdj:
Ok are you able to give me a few that i should try out that will be compatible with the above ?
[Galaxy S III Q&A, Help & Troubleshooting] Behemoth1702:
This one is pretty popular, giving your great access to a lot of settings and governors/IO schedulers.

Boeffla Kernel for CM

I currently use zzmove governor on "battery yank" setting, it's great to see CPU cores being shut down when not used. ROW is my favorite IO scheduler because the phone feels very repsonsive, although writing operations really slow down the phone for me during normal use. Still like it.

Google "i9300 kernels" and take a good look for what you want.
[Galaxy S III Q&A, Help & Troubleshooting] :
AGNi Kernel is what i'm running and is super blazing fast!

Modded my Stock v4.3 to look like kitkat:)
[Nexus 5 Q&A, Help & Troubleshooting] biripada:
Hi All,

It is know that IP exclusion is almost impossible using Android VPN Service API in NON ROOTED Device.

But I have rooted device . So I first connect VPN ( openvpn ).

After than from ADB ROOT SHELL - I run following command

./route add -net <<DESTINATION_IP>> netmask 255.255.255.255 gw 192.168.1.1

For example if I run following command

./route add -net 141.101.120.15 netmask 255.255.255.255 gw 192.168.1.1

All traffic to whatismyip DOT com/ go directly ( Not passing through VPN )

Hence whatismyip.com reports my Local ISP IP in Its home page.

By these way I could exclude IPs from VPN path. This is working fine in ICS and Jelly without any issue.

But this same procedure not working in KITKAT. I tested both in 4.4.2 and 4.4.4

If I modify route, traffic still goes through VPN path. Whatismyip.com displaying VPN Server IP in its home page.

My KITKAT routing table shows following same as ICS and jelly. Command is successfully executed in routing table..But just not working..

Can anybody please point out what changes I need to make for KITKAT.

Thank you

----Fresh Routing Table -----

ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324

192.168.1.1 dev wlan0 scope link

----- After VPN Connected------

ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324
172.22.1.4/30 dev tun0 proto kernel scope link src 172.22.1.6
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324

192.168.1.1 dev wlan0 scope link

------ After whatismyip dot com [141.101.120.15] exclusion ------

ip route
default via 192.168.1.1 dev wlan0
default via 192.168.1.1 dev wlan0 metric 324

[B]141.101.120.15 via 192.168.1.1 dev wlan0[/B]

172.22.1.4/30 dev tun1 proto kernel scope link src 172.22.1.6
192.168.1.0/24 dev wlan0 scope link
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 324
192.168.1.1 dev wlan0 scope link
[Upgrading, Modifying and Unlocking] Ingvarr:
The attached utility will allow to extract .NB0 OS image from ASUS P525 "galaxy.cap" complete rom update packages, and also to update CRC on modified NB0 ROM image, to pass the flasher validity check and flash the modified ROM. Also it will allow to unpack compressed kernel partition.

The application dynamically linked to Visual C runtime libraries. They used by myriads of applications, and most likely you already have them on your system installed. If you are not (on a clean PC for example) and P525ROMTool complains about lack of needed libraries,- download and install this - http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE

For you technical people, the utility source is included too. You can see the basic layout, and that ASUS used Adler32 algorithm to calculate the checksum on ROMs (with slight modification that base sum was initialized to zero instead of one).

The basic procedure for cooking your own custom P525 rom is:

1) P525ROMTool -d galaxy.cap

This will extract the ROMGalaxy.NB0 OS-only image. For custom ROMs I recommend working with NB0 OS images only - no danger of corrupting bootloader & IPL this way.

2) prepare_imgfs ROMGalaxy.NB0 -nosplit

3) DelFile / AddFile

Iam not sure if you can truly fully rebuild the ROM and not to break anything (ROM tools were made for HTC platform, not for ASUS). So I recommend using DelFile/AddFile method at least for the start.

There are a lot of different ROM editing tools around, but I can not give you exact directions what is better and in which conditions - ASUS ROM cooking is less charted area then for HTCs.

I assume you know what you actually need to change on file basis for your ROM customization. If you dont know what I am talking about, this is not for you (read disclaimer at the end of the post, and think over it).

4) make_imgfs ROMGalaxy.NB0 -nosplit

5) P525ROMTool -s ROMGalaxy.NB0

it will ask about changed checksum. Enter "y" to update it. You can run P525"ROMTool -s ROMGalaxy.NB0" again to be sure that checksum was updated properly - it should'nt ask to change it second time.

6) Flash ROMGalaxy.NB0 via bootloader (copy it to SD card root, press "camera" fully, press reset).

Techincally, you can make the .cap file to flash via "autorun" loader, hovewer, I must warn you that .cap file will flash not only OS image, but also the IPL+bootloader. If something goes wrong, bootloader can be corrupted and device will be bricked.

If you flash ROMGalaxy.NB0, it will not flash over bootloader+IPL, so its a lot safer - if something goes wrong, you still must be able to flash emergency rom via bootloader.

Take note that any activity that involves the ROM updating is dangerous. Even if you understand everything, there is some risk. If you have only basic understanding of ROM mechanics, risk increases tenfold - you better consider before screwing up perfectly working and expensive device.

You have been warned.
[Upgrading, Modifying and Unlocking] jackleung:
Ingvarr, thanks a million time. I love yr WM5 Storage and I think I will love this tool also. I will start building my rom based on Sorg's build 6 since it does provide some very useful tools for us.
[Upgrading, Modifying and Unlocking] PestKilleR:
Ingvarr thank you for your cool tools.

But when I DIY my ROM, I can't make make_imgfs.exe work correctly. It returns some symbols I can't understand.

Even I run make_imgfs.exe just after finish running prepare_imgfs.exe, it returns the err.

Could you help me with this?
[Upgrading, Modifying and Unlocking] Ingvarr:
make_imgfs ROMGalaxy.NB0 -nosplit

NOT "nk.nba"

It writes the modified filesystem back in the original image, so it should remain the same. You dont want to mix the ASUS and HTC ROMs and then flash it to your device, trust me :)

I recommend you to read HTC ROM Tools instructions and forum threads and be sure you've got right how it works, before you screw something up ;)
[Upgrading, Modifying and Unlocking] creazy2000:
sir,

Bad news，it can't work with CHS ROM （ROMgalaxy.nb0） checksum error！～～～
[Upgrading, Modifying and Unlocking] Ingvarr:
Does it correctly verify the checksum on original ROM?

I will try to look over it, maybe I've missed something.

Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
[Upgrading, Modifying and Unlocking] harlemyin:
i have tried it too.

i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
[Upgrading, Modifying and Unlocking] Ingvarr:
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?

I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit ;)
[Upgrading, Modifying and Unlocking] harlemyin:
yes

and it happens by official P525_V3320_WWE2nd too

checksum in official P525_V3320_WWE2nd is 79AB7436

ur SW changed it to EF722461----not modified NB0

u can download official P525_V3320_WWE2nd with www.asus.com or

ftp://dlsvr02.asus.com/pub/ASUS/IA/P525/P525_V3320_WWE2nd.zip
[Upgrading, Modifying and Unlocking] Ingvarr:
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...

This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?

I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.

Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
[Upgrading, Modifying and Unlocking] harlemyin:
sorry

our mistake

i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.

and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader

everything is fine, when *.nb0 is extracted with ur P525ROMTool

i think creazy2000 just made the same mistake like me.
[Upgrading, Modifying and Unlocking] harlemyin:
o

thanks a lot.
[Upgrading, Modifying and Unlocking] jackleung:
Thanks. The tool works perfectly on my P525.
[Upgrading, Modifying and Unlocking] creazy2000:
I make a mistake, thanks!
[Upgrading, Modifying and Unlocking] creazy2000:
Oh, I know !

I make a mistake !

thanks
[Upgrading, Modifying and Unlocking] Night Runner:
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
[Upgrading, Modifying and Unlocking] jmfa59:
P525_V3320_WWE2

I have P525_V3.29.0 WWE3

Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer

Thanks all
[Upgrading, Modifying and Unlocking] Ingvarr:
Everything about complete process is in the first post. What is you dont understand from here?
[Upgrading, Modifying and Unlocking] Ingvarr:
WWE means "world wide english".

First is 3.32, therefore, its newer.
[Upgrading, Modifying and Unlocking] jmfa59:
Ingvarr

Thanks Buddy,

can you explain WW2 and WWE3 it seems that the latter is newer but the version V3.29 is older or is ment for different country
[Upgrading, Modifying and Unlocking] Ingvarr:
i dont know what last number means, may be some internal index.

3.32 is clearly the newer, and its appeared a lot later.
[Upgrading, Modifying and Unlocking] jmfa59:
Thanks a lot
[Upgrading, Modifying and Unlocking] sorg:
now everyone can create his own ROM and make his device better.. may be ;)

So, now i can create ROM only for my own needs. no need include so much variations :)

good luck in creation!
[Upgrading, Modifying and Unlocking] jackleung:
Hi Sorg, your custom tools, tricks and patch (Torch, smartphone mode, fixed to PhoneAlarm .... etc) to P525 are still very important to us . And that's why I build my own rom based on your rom. So, please continue your support to P525 community and share whatever brilliant ideas and tricks to us. ;)
[Upgrading, Modifying and Unlocking] Ingvarr:
Now the cooking is possible, but still cumbersome.

It would be better at least to try to do a port of Bepe Rom Kitchen - that should allow to ease cooking process a lot. Also potentially that should allow also to integrate latest AKUs, and every willing person just will do a custom ROM packages - but everybody will be able to choose any set of packages for own rom.

Hovewer I guess its better to wait for release of P535 ROM (with AKU 3.2) to look for common ground and see if maybe they used Microsoft (modernized) Bluetooth stack there. I suspect that custom Broadcomm stack can make isolating device-specific parts more difficult.
[Upgrading, Modifying and Unlocking] jackleung:
It's true. And my not so perfect approach is writing a Dos batch file to streamline the process now (see attached based on using Sorg's build 06 rom).

BTW, do any of you notice the free/used sectors reported by Addfiles.exe is not getting updated even the files is successfully added to the rom (see below)???

C:\Sorg>Addfile.exe VCWave.dll

Total Sectors: 3ffc0

Used Sectors : 16a71

Free Sectors : 2954f

C:\Sorg>Addfile.exe VocabSetting.exe

Total Sectors: 3ffc0

Used Sectors : 16a71

Free Sectors : 2954f

C:\Sorg>Addfile.exe VoiceCommander.exe

Total Sectors: 3ffc0

Used Sectors : 16a71

Free Sectors : 2954f

C:\Sorg>Addfile.exe VSRDLL.dll

Total Sectors: 3ffc0

Used Sectors : 16a71

Free Sectors : 2954f
[Upgrading, Modifying and Unlocking] Ingvarr:
For me, the number of sectors update correctly.

However, I've used ASUS WWE rom for testing, not Sorg's:

C:\>addfile rgucomp.exe
Total Sectors: 3ffc0
Used Sectors : 1093a
Free Sectors : 2f686

C:\>addfile rgucomp.exe
Total Sectors: 3ffc0
Used Sectors : 10983
Free Sectors : 2f63d
[Upgrading, Modifying and Unlocking] sorg:
535 ROM has the same widcomm stack.

535 has no phone keyboard, another WiFi Card (b/g instead b) and 256MB of ROM instead 128MB..

ROM from 535 doesn't work straight on 525. After some tweaks, windows started , but only devices working are display and touch screen. no keyboard, no wifi(of course!), no bt, no gsm.. nothing :)

ROM has a lot of modules and it's impossible simple move them from one ROM to another. need rebase all modules..

I think, ROM from 535 isn't so similar to get it as reference to cook AKU 3.2 ROM for 525.. also, there is already AKU3.3 for some devices available with even closer functionality to 525 than 535 to 525..
[Upgrading, Modifying and Unlocking] Ingvarr:
Oh, I hoped that P525 & P535 had more common platform, but nvm...

Well, then I guess then its up "usual" way as with Bepe's Rom Kitchen - just to separate the device-dependent part and AKU (independent) part.

If its properly done we can then just use any AKU packages for Rom Kitchen that float around (I think the latest proper is 3.2).

If needed, modules can be rebased. I think there is an utility around that guess module relocations, provided you have same module from different ROM versions/languages. Also, modules can be moved without rebasing - but, rebasing will be needed in case of address "collision" if two modules will end up in same area.
[Upgrading, Modifying and Unlocking] jackleung:
Hi Ingvarr, does it mean yr P525 Rom Tool work for P535 also??
[Upgrading, Modifying and Unlocking] sorg:
imgfs can handle only one of three parts - OS part.

there is also "kernel1" and "kernel2" parts.. I don't know real names, so just named them so. For kernel1 i already made builder.. kernel2 still not clear for me.

try to find coredll.dll and asusmisc.dll files in OS ROM and you will know what i mean ;)
[Upgrading, Modifying and Unlocking] sorg:
btw latest AKU is 3.3 as i mentioned above.. not 3.2
[Upgrading, Modifying and Unlocking] Ingvarr:
These are bulit directly in NK.exe I think.

There are 3 partitions, as in usual MSFLASH-based WM5 devices (first sector is usual MBR, second sector contains MSFLASH signature).

partition 1) XIP-updater "compact" NK.exe. Its usually present, but not used, since no known device actually use the XIP update, preferring to overwrite whole ROM instead.

partition 2) NK.exe (kernel) for usual boot. On P525 its compressed (see SPRX signature), as on many other devices (ie Mitacs). Good thing you dont actually need to alter it, even for AKU updates - this is kernel&device dependent part. But it _can_ be altered, just needs to be unpacked first.

partition 3) TrueDOC file system. All other files go there and its that primarily altered & built.

Bepe ROM kitchen takes "base" NB0 as device-dependent template for make_imgfs, as usual.

I know latest AKU is 3.3 but I havent seen ROM Kitchen _packages_ for 3.3 yet.
[Upgrading, Modifying and Unlocking] Ingvarr:
Hmm, modularization seem to went nice.

I've just used DSMTool on all .dsm files in Dump - and I've obtained nice set of packages, and "drivers" package among them. Now just to check what package is what and separate AKU OS, AKU LOC and OEM sets...

Iam wondering, does buildimgfs actually work with P525? Sector values it writes at the end is somewhat suspicious...

But its vital for ROM kitchen process.

Edit: Ok, done, I have uploaded the OEM part on xda ftp - Uploads/ASUS P525/ROM Kitchen/ASUS_P525_OEM_WWE_332.rar.

I've placed the custom initflashfiles and AKU reg stamp and CreateOS.exe seem to reconstruct the original(AKU 2.3) ROM quite close to original.

OEM packages are easely identified by ASUS certificate instead of Microsoft one.

Though, two packages are somewhat ambigous - I see them both in P525 "OEM" part and in third-party AKU packages.

These are:

c9a4171d-b932-713c-4d22-4c71a0b83ddf (ASUS) <=> 5cc9ab9f-47a2-d09f-fb06-ffc00b55ac44 (AKU LOC)

and

034e7cf6-8a37-40ad-85bd-6851b921866a (ASUS) <=> 034e7cf6-8a37-40ad-85bd-6851b921866a (AKU OS)

For correct reconstruction only one from each pair should be left. I am wondering which ones...
[Upgrading, Modifying and Unlocking] sorg:
AKU3.3 can be extracted from ROM of this topic:

http://xdaforums.com/showthread.php?t=284509

your descriptions for parts 1 and 2 are incorrect.

part 1: NK.exe and low-level AKU dependent(!) libraries like codedll.dll, busenum.dll, trueffs.dll and others. you can extract all them by dumprom utility

part2: XPRS partition. i don't know any tools to handle this. From one place i found that it should be compressed block of RAM. But actually, i think it contains some libraries because library asusmisc.dll couldn't be found neither in DOC not in NK partitions. Currently, i don't know any utility to handle this partition to look what is inside..

besides description, if you want make AKU 3.x ROM then you have to replace some files in part 1. coredll.dll is the key component and AKU dependent. And it's better to update all libs in NK because they could compiled with some new structures from AKU 3.x. You can look at exported functions of coredll.dll and will find there are many new exports.

Another problem is that both parts 1 and 2 includes all libraries as modules and when you will replace AKU, you most likely have to re-base all of them.

Well, if you want replace to AKU 3.2 from 535 then no need rebase part1' libs because addresses are the same.

But u think, it's better to take AKU 3.3 from topic i mentioned.

ASUS ROM has 2 packages from ASUS as you showed before.. both have to be transferred to new ROM.