Develop Bugs

[RELEASE] Froyo DXJPA one-step flash package

Okay people, its done!
This is the procedure and firmware package for a single-step flash to DXJPA using Odin:
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install-froyo.html
If you flash using that procedure, you should get a 'stock' DXJPA phone will all DX-series CSCs. Unfortunately, it *will* do a factory reset / wipe data.
DXJPA is the official Froyo for the Southeast Asian region: Singapore, Indonesia, Malaysia, Thailand, Vietnam, Philippines.
DXJPA is tricky because it really needs PIT 513 (it's the only ROM, as far as I know), probably because the /system partition size needs to be very big for the carrier customizations.
I've basically combined the missing parts from DXJPA with the files from the original DXJG4 and used the correct PIT.

Bro, thanks. now downloading from multiupload site. going to try flashing directly through odin1.7 with pit513 directly and will report back to see if successful or not.
btw, time to change your signature?
p/s: is it okay to use your k7 kernel on this rom?
edit: looking at the downloaded file from Richtofen, the modem.bin is missing. hmm....
edit2: after reviewing, i am using your package to flash.

No bro, you should use my download link. All the other packages have the wrong dbdata and the CSC wont work properly - unless u do the 2 step from DXJG4 to DXJPA.

Hey bro. Did you find any significant changes between this ROM compare to ADJP5 like does it work better with your kernel? Just curious.
Thanks!

danzgrace said:
Hey bro. Did you find any significant changes between this ROM compare to ADJP5 like does it work better with your kernel? Just curious.
Thanks!
Click to expand...
Click to collapse
ADJP5 is from another region. The DX series is for Southeast Asia. And yup, it works with my kernel too - all Froyo ROMs work.

hardcore said:
No bro, you should use my download link. All the other packages have the wrong dbdata and the CSC wont work properly - unless u do the 2 step from DXJG4 to DXJPA.
Click to expand...
Click to collapse
yeah, i notice a huge difference in the dbdata.rfs as well as the cache.rfs. The cache.rfs should be containing all the bloatware apps i presume.
now flashing, almost done now.
give me sometime, and i will do the batterymod if anyone is interested.

Someone needs to work on customizing this ROM so we can save more space.

hmm, seems to get stuck at bootup screen, but no black screen yet. will wait a bit longer, and get into recovery to wipe cache, do a factory reset.
edit: just booted up. haha...

need a fast server
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.

hardcore, posted this in the other thread. posting here again:-
is it possible to convert this to cwm package (like how doc rambone does with his jpa/jpo roms) so that it can be flashed without wiping out all the data and settings?

s88 said:
need a fast server
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.
Click to expand...
Click to collapse
Is that error from blogspot, or from Google Docs?
BTW, please let me know if you can't download the file. Google Docs should be super fast but I'm not sure if they'll block it after a while...

g00ndu said:
give me sometime, and i will do the batterymod if anyone is interested.
Click to expand...
Click to collapse
Sure I'm interested! Version D please.

hardcore said:
Sure I'm interested! Version D please.
Click to expand...
Click to collapse
Check the battery mod thread.. Wrote a new tutorial..

Downloading... Can't update my galaxy s asian version from kies.

Google Docs, i try again and is able to download now
hardcore said:
Is that error from blogspot, or from Google Docs?
BTW, please let me know if you can't download the file. Google Docs should be super fast but I'm not sure if they'll block it after a while...
Click to expand...
Click to collapse

Thanks Hardcore. Hope someone will cook a custom based on this firmware for us!
PS - I cant download either

you can use mediafire.com

epicurean said:
Thanks Hardcore. Hope someone will cook a custom based on this firmware for us!
PS - I cant download either
Click to expand...
Click to collapse
If you can't download, try again in a while.
In the meantime I will try to upload it to multiupload but that also takes a long time!

Installed!! Working fine..

hardcore said:
If you can't download, try again in a while.
In the meantime I will try to upload it to multiupload but that also takes a long time!
Click to expand...
Click to collapse
I'm going to upload to my server in a while and will post the link here after its done, won't have any limitations

[Q] Using DSIXDA Kitchen

After repacking my rom it won't boot past the bootanimation. I'm trying to do a logcat like the q&a said but I can't figure out how to do so. Can someone help me out?

I got it to boot up

Would someone mind telling me how to change the build in software to your roms name?

Edit build.prop (look toward the bottom that should have what you are looking for)
Specific line is: ro.modversion
Sent from my PC36100 using XDA App

If you are really "using" dsixdas kitchen you would have noticed the option on the first menu page that says "change rom name".

lovethyEVO said:
If you are really "using" dsixdas kitchen you would have noticed the option on the first menu page that says "change rom name".
Click to expand...
Click to collapse
if you had been using previous versions of dsixdas kitchen you would have noticed that the "change rom name" option never worked lol. Has it been fixed yet? I just edit the build.prop file myself because the option in the kitchen never worked for me...

deathsled said:
if you had been using previous versions of dsixdas kitchen you would have noticed that the "change rom name" option never worked lol. Has it been fixed yet? I just edit the build.prop file myself because the option in the kitchen never worked for me...
Click to expand...
Click to collapse
Always worked fine for me. All the way down to 0.105 when I first started using it. He's released a bunch since then but I have never had a problem with anything in the kitchen except for the updater script verification but that was fixed a while back too.

Well maybe it does work, but doesn't change what people REALLY want changed. I think most people are wanting that option to change what appears in the About -> Software screen which it doesn't I dont think...

deathsled said:
Well maybe it does work, but doesn't change what people REALLY want changed. I think most people are wanting that option to change what appears in the About -> Software screen which it doesn't I dont think...
Click to expand...
Click to collapse
My recent rom finalized with dsixda and used the change rom name option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

captblaze said:
Edit build.prop (look toward the bottom that should have what you are looking for)
Specific line is: ro.modversion
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I appreciate it.
lovethyEVO said:
If you are really "using" dsixdas kitchen you would have noticed the option on the first menu page that says "change rom name".
Click to expand...
Click to collapse
I did notice that option but it didn't change what I wanted change.
deathsled said:
if you had been using previous versions of dsixdas kitchen you would have noticed that the "change rom name" option never worked lol. Has it been fixed yet? I just edit the build.prop file myself because the option in the kitchen never worked for me...
Click to expand...
Click to collapse
Correct and yea a lot of bugs have been worked out.
deathsled said:
Well maybe it does work, but doesn't change what people REALLY want changed. I think most people are wanting that option to change what appears in the About -> Software screen which it doesn't I dont think...
Click to expand...
Click to collapse
I wanted to change the build number
lovethyEVO said:
My recent rom finalized with dsixda and used the change rom name option.
Click to expand...
Click to collapse
I know how to change the software with the kitchen I don't want that changed if you ever used myn's rom or some others their rom name is under build. That is where I wan't my rom name I want the software name to stay at 3.70

nuggyunlimited said:
I know how to change the software with the kitchen I don't want that changed if you ever used myn's rom or some others their rom name is under build. That is where I wan't my rom name I want the software name to stay at 3.70
Click to expand...
Click to collapse
I see now.
In that sense then yes you have to edit the build.prop yourself as previously stated and the kitchen does not allow you to change this value.
I personally don't care what it's listed under (rom name under software number) but we all have our ocd tendencies and this could probably be one of yours. Good luck.

lovethyEVO said:
I see now.
In that sense then yes you have to edit the build.prop yourself as previously stated and the kitchen does not allow you to change this value.
I personally don't care what it's listed under (rom name under software number) but we all have our ocd tendencies and this could probably be one of yours. Good luck.
Click to expand...
Click to collapse
Lol it is one of mine. It's been bugging me for two days straight

nuggyunlimited said:
Lol it is one of mine. It's been bugging me for two days straight
Click to expand...
Click to collapse
Testing it and so far I was able to change the value under software number in the build.prop on the phone with root explorer and the change took effect on reboot.
Should save you some time especially if you have already built the rom.
Just change the value on the phone until it is what you like and export the build.prop file out of your phone and into your rom zip.

lovethyEVO said:
Testing it and so far I was able to change the value under software number in the build.prop on the phone with root explorer and the change took effect on reboot.
Should save you some time especially if you have already built the rom.
Just change the value on the phone until it is what you like and export the build.prop file out of your phone and into your rom zip.
Click to expand...
Click to collapse
Appreciate it

No problem.

For the evo build.prop the line you want to edit is
ro.build.description

lovethyEVO said:
For the evo build.prop the line you want to edit is
ro.build.description
Click to expand...
Click to collapse
Appreciate it man I'm having another problem my room wont go pass the splash screen now I was reading DSIXDA thread and it says to do a logcat but I can't figure out how. I'm using RUU 3.70 deodexed I didn't even theme anything I just put the ruu on the root and flashed it and it's stuck at the splashscreen. Any suggestions? I did zipalign it also

nuggyunlimited said:
Appreciate it man I'm having another problem my room wont go pass the splash screen now I was reading DSIXDA thread and it says to do a logcat but I can't figure out how. I'm using RUU 3.70 deodexed I didn't even theme anything I just put the ruu on the root and flashed it and it's stuck at the splashscreen. Any suggestions? I did zipalign it also
Click to expand...
Click to collapse
It depends on what you did to the rom. Since you didn't theme it you either added or deleted some files from the zip that are preventing it from booting.
I found that out the hard way. The last rom I made (3.70) which is the one I use now is basically bone stock 3.70 except for a handful of changes that don't allow it to freeze on boot during a fresh install.
If you have made any changes to any apps try replacing them with the stock ones and then doing another install.

lovethyEVO said:
It depends on what you did to the rom. Since you didn't theme it you either added or deleted some files from the zip that are preventing it from booting.
I found that out the hard way. The last rom I made (3.70) which is the one I use now is basically bone stock 3.70 except for a handful of changes that don't allow it to freeze on boot during a fresh install.
If you have made any changes to any apps try replacing them with the stock ones and then doing another install.
Click to expand...
Click to collapse
I really didn't remove anything this is all a2sd and data app command I added and I added them using the kitchen it never messed anything up before. The base might have been a bad download I'll try downloading it again.

nuggyunlimited said:
I really didn't remove anything this is all a2sd and data app command I added and I added them using the kitchen it never messed anything up before. The base might have been a bad download I'll try downloading it again.
Click to expand...
Click to collapse
Have you built any bootable version from the source of the one that is not booting?
Where did you get the source for the rom you are building?
You can either grab the rom version zip from the dev forum (3.70 stock, rooted, deodexed for example) which is basically bare bones roms with root added and deodexed as an example.
Or, you could grab the ruu and grab the rom.zip file from it and then extract the needed .imgs to create a rom.
Most of this info is in the dsixda kitchen thread but basically if you haven't changed anything manually in the rom source then more than likely you did get a corrupted source.
Good luck.

[GUIDE] How to re-package firmwares for Odin [Windows and Linux]

This will demonstrate repackaging a 1 file firmware to a 3 files firmware.
By following this guide, any firmware can be repackaged as re-partition ready firmware that can be used directly with any pit file.
Any boot.bin and Sbl.bin can be removed/deleted/excluded during firmware repackaging.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Before you read any further:
1: By following this guide, you agree that you are following it on your own risk.
2: If the firmware(s) you have repackaged is/are not working, then it's because you did not follow the very simple and easy steps as you should.
If you can't live with the above then please don't follow this guide, but if it's no problem for you then follow me to see how easy it can be.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Tools:
Customized cygwin (Windows users): Download MD5: 0e63785289d8fedaa3719e4ac615fd63 (Thanks to dsixda).
Empty dbdata.rfs file: Download MD5: bc7a6eff20660a5f2e6ba76f6653f54b
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Note:
If you are a Linux user then you only need to download the empty dbdata.rfs archive and can move directly to Re-packaging the firmware
Click to expand...
Click to collapse
Installing cygwin:
1. Extract the cygwin archive and run the setup file
Click to expand...
Click to collapse
2. Choose Install from Local Directory
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3. Choose where to install cygwin, to make it easy for you then let it be installed on C-drive
Click to expand...
Click to collapse
Click to expand...
Click to collapse
4. Brows to the Local Package Directory, it's under cygwin packages in the extracted archive directory, as shown below
Click to expand...
Click to collapse
Click to expand...
Click to collapse
5. You will be greeted by warning, hit OK
Click to expand...
Click to collapse
Click to expand...
Click to collapse
6. Click on the arrows as shown below until all packages change status to Install and hit Next
Click to expand...
Click to collapse
Click to expand...
Click to collapse
7. Complete the installation, no more changes are required and you might get a Windows error when installation is complete, just hit Cancel
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Re-packaging the firmware:
1. Make a and rename a folder/directory and extract the firmware tar package to that folder or simply open using a compression utility like 7zip or winrar then highlight and drag the files to the new folder. It's easier to make the directory on drive C if you are a windows user.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2. Extract the Empty_dbdata.rfs_file archive and copy the extracted dbdata.rfs to the same folder
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Note:
I have created a directory on drive C which I called ROM and in the same example I'm repackaging a JS5 firmware, so if you have created a directory with different name, path/location or firmware name then you need to change the following commands to suit your changes.
Click to expand...
Click to collapse
3. Start cygwin from the shortcut on your Desktop, Linux users can use the terminal and change to the firmware directory.
Click to expand...
Click to collapse
Changing to the extracted firmware directory:
cd c:/ROM
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Creating a PDA.tar.md5:
Creating a PDA.tar file (Please read the note regarding this command at the end of this guide)*
tar -c param.lfs zImage factoryfs.rfs dbdata.rfs >> PDA_JS5.tar
Click to expand...
Click to collapse
Creating an MD5 hash
md5sum -t PDA_JS5.tar >> PDA_JS5.tar
Click to expand...
Click to collapse
Moving the MD5 hash information to the tar file
mv PDA_JS5.tar PDA_JS5.tar.md5
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Creating a Phone.tar.md5:
Creating a Phone.tar
tar -c modem.bin >> PHONE_JPY.tar
Click to expand...
Click to collapse
Creating an MD5 hash
md5sum -t PHONE_JPY.tar >> PHONE_JPY.tar
Click to expand...
Click to collapse
Moving the MD5 hash information to the tar file
mv PHONE_JPY.tar PHONE_JPY.tar.md5
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Creating a CSC.tar.md5
Creating CSC.tar
tar -c cache.rfs >> CSC_XENJS3.tar
Click to expand...
Click to collapse
Creating an MD5 hash
md5sum -t CSC_XENJS3.tar >> CSC_XENJS3.tar
Click to expand...
Click to collapse
Moving the MD5 hash information to the tar file
mv CSC_XENJS3.tar CSC_XENJS3.tar.md5
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Note:
All command for packaging and creating a single tar.md5 file(3 commands) can be executed as one single command as follows with PDA as example:
Code:
[B]tar -c param.lfs zImage factoryfs.rfs dbdata.rfs >> PDA_JS5.tar ; md5sum -t PDA_JS5.tar >> PDA_JS5.tar ; mv PDA_JS5.tar PDA_JS5.tar.md5[/B]
and so on..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
We have by now repackaged a firmware of 1 tar file to 3 tar.md5 files, these files are now ready to be tested before flashing or sharing.
Note:
One reason for a failing MD5 checksum of a file is renaming it after it has been repackaged as a tar.md5, so don't rename the repackaged files.
Click to expand...
Click to collapse
Testing the tar.md5 files (Windows):
Start Odin and load PDA, PHONE and the CSC files without connecting the phone to any USB port and hit Start and look at the massage panel of Odin and see if your packages are valid, if they are not then you haven't repackaged the files right, and you need to start over.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Sharing the repackaged firmware:
I have many times seen our members upload and share firmwares that are not compressed, this is not good for two reasons:
1. The file could be corrupt when downloaded, and there is no fun in flashing a corrupt firmware, this can be avoided when extracting a compressed firmware. A corrupt archive cannot be extracted, and thereby you will know that your downloaded firmware is corrupt.
2. A tar file is not a compressed file, it's only a package that contains file(s). Please take a look and see how all the extracted files are almost equal in size to the tar.md5 files
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you compress your files before uploading them, then file(s) size, upload time for you and the download time for them you are sharing your file(s) with will be cut in half, take a look to see what I mean
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Conclusion:
Click to expand...
Click to collapse
We have by now learned how to repackage firmware(s), use them and share them without worrying about re-partitioning.
We can now repackage and remove boot.bin and Sbl.bin in any leaked or official firmware that is already split in 3 files, that may disable Download and Recovery modes of our devices.
Good luck repackaging, flashing and sharing your firmwares..
Click to expand...
Click to collapse
*Note:
The first file in the command will be the first file to be added to the tar file and the first to be flashed. I'm using this command in this particular order according to the pit files and the device partitions which are:
Click to expand...
Click to collapse
START
boot.bin
.pit
efs.rfs
sbl.bin
sbl.bin
param.lfs
zImage
zImage
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
END
Click to expand...
Click to collapse

reserved...

I believe 7zip can make tar files, but NOT able to use when flashing.
Sent from my GT-I9000 using XDA App

DamianGto said:
True.
You take any random tar file and open it and put the file in it you want.
Then it works.
I did it alot before i setup a linux system.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Click to expand...
Click to collapse
I use peazip or IZarc to create tar files in windows.

ragin said:
I use peazip or IZarc to create tar files in windows.
Click to expand...
Click to collapse
nice.
never tryed them.
But we can say now there is zero reason to install cygwin just to pack tar files.

Ramad, thank you for the guide .. Interesting to read and will definitely try it.
Could you maybe also make a guide how to deodex and zip align a rom ? I saw you posted quite a few deodexed and zipaligned roms ( i am using your xwjs5 deodexed rom).
I would like to be able to deodex/zipalign / add root my self .. I have asked this question before , but the only answer I get is : google is your friend :-( ..I have x-ultimate 2.2.2 , but that clearly isn't enough ..

Bandis710 said:
Ramad, thank you for the guide .. Interesting to read and will definitely try it.
Could you maybe also make a guide how to deodex and zip align a rom ? I saw you posted quite a few deodexed and zipaligned roms ( i am using your xwjs5 deodexed rom).
I would like to be able to deodex/zipalign / add root my self .. I have asked this question before , but the only answer I get is : google is your friend :-( ..I have x-ultimate 2.2.2 , but that clearly isn't enough ..
Click to expand...
Click to collapse
xUltimate is to deodex, apk manager can be used for zipaligned. Both can be run in batch mode.
Sent from my GT-I9000 using XDA App

Bandis710 said:
Ramad, thank you for the guide .. Interesting to read and will definitely try it.
Could you maybe also make a guide how to deodex and zip align a rom ? I saw you posted quite a few deodexed and zipaligned roms ( i am using your xwjs5 deodexed rom).
I would like to be able to deodex/zipalign / add root my self .. I have asked this question before , but the only answer I get is : google is your friend :-( ..I have x-ultimate 2.2.2 , but that clearly isn't enough ..
Click to expand...
Click to collapse
I have answered a part of your question here at post #43: http://forum.xda-developers.com/showthread.php?p=11585682#post11585682 . That took a lot time to write, the whole process may wait till I have more time in the future.

ragin said:
I think most people really don't completely understand what you mean when you say something. I think that's the problem here.
Like in the post quoted, you have asked people to read in other places to get a better understanding of things. But you don't specify any links. How & where should I search in order to better understand things?
Click to expand...
Click to collapse
This guide could be a very good.
I do like the pictures to show the steep.
But some of them is unneeded and you can make it better and use a faster and simpler way that works good.
Some that read this Maby think Im to hard and hate this guide and the person that wrote it. You cant be more wrong.
But if you make a guide or program do have some development pride and make it with high quality. If op do change things so the steep is better and all errors in the text is fixed then i have no problem to recomend this guide to people that ask this kind of questions.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**

Thanks for this, had been looking for something like this
There's always more than one way to skin a cat, some more troublesome etc. But let's not dampen the sharing spirit of fellow xda members
Now let's concentrate on making this guide better for everyone.

DamianGto said:
.
This guide could be a very good.
I do like the pictures to show the steep.
But some of them is unneeded and you can make it better and use a faster and simpler way that works good.
Some that read this Maby think Im to hard and hate this guide and the person that wrote it. You cant be more wrong.
But if you make a guide or program do have some development pride and make it with high quality. If op do change things so the steep is better and all errors in the text is fixed then i have no problem to recomend this guide to people that ask this kind of questions.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**
Click to expand...
Click to collapse
Everything OP says in the first post is correct & working. I have been using a similar method myself when I started making ROMs for my ConvergeROM. Well, there is a simpler way available that does all this using a script. You can find it HERE - http://forum.xda-developers.com/showthread.php?t=943588

@Ramad,
You can add a reference about adding costum kernels into the PDA made. You just have to find the correct zImage & replace it in the PDA.

A very good guide! Thank you very much Ramad. Would be just nice if there were such a guide some weeks ago
Now I found out myself to create my own ROMs and packages. And...I also do it with cygwin. It the only way for me it worked without any errors.
I wish more people here at xda would share there knownledge. Since a while more and more people start to make secrets of their work.
Thank you very much!

BlockbusterF said:
A very good guide! Thank you very much Ramad. Would be just nice if there were such a guide some weeks ago
Now I found out myself to create my own ROMs and packages. And...I also do it with cygwin. It the only way for me it worked without any errors.
I wish more people here at xda would share there knownledge. Since a while more and more people start to make secrets of their work.
Thank you very much!
Click to expand...
Click to collapse
My few PDAs were done with peazip. Wonderful tar application under Windows.

Guys, this is a very helpful post. Personally I've been using Cygwin to tar up ROMs for a while now and although I don't agree with all the steps Ramad has included (eg. you don't really need to MD5 the files in my opinion for one), or all the information (eg. I agree with DamianGTOs comment about what low level packages include), the instructions do work and it's the first time I've seen someone trying to provide instructions on this so thanks go to Ramad for that. This is the second thread I've come across recently that's been a battlefield between Ramad and DamianGTO and with respect guys, it really puts people off a thread if it turns into a battleground like this. For the sake of the community is there any chance you could tone it down a bit please?

@bdl1969
You don't have to use checksum option, I would like to advice using it.
I did not see anyone raise there hands against md5 checksum, like here : http://forum.xda-developers.com/showpost.php?p=7940762&postcount=1
And here: http://forum.xda-developers.com/showthread.php?t=802909/QUOTE
And many other many other firmware releases leaked by Richthofen, because it's Richthofen writting...
Richthofen said:
Usually Odin3 images are provided in a single integrated .tar package which contain all of the necessary files. This way the CSC cannot be selected separately.
That is why I splitted the release in three different parts (CODE, MODEM, CSC).
Since Odin3 has flashfile checksum support I also added md5 hash tail to the .tar files. This way is more secure because Odin will not allow flashing corrupted images. Flashing takes a bit longer thou because the checksums are checked in the beginning of the update process.
Click to expand...
Click to collapse
I did not call the packages High package, Medium package or Low package, but Low Level...was referring to format, however, as it appears to me that we have a problem with the guy calling a bird..."birdie" not with the word it self, and how a word is that is going to effect taring and flashing firmwares is yet not obvious to me!! But I Have removed these words as Low Level, because I have no desire to have these irrelevant discussions.

Maby i spell weird sometimes. I blame my phone and English is not my native language.
But fact still remains.
I have asked him to make the guide more clear what user he is targeting.
I also give advice to make some steep easier for the novice users.
I also sad that this could be a very good guide. But if you put up your work you must understand that people can correct things thats wrong or make a suggestion to make it better.
But op have from the start decided that all thing a say is wrong.
That's why i say this guide is not good and has errors and lie in it.
It has been very easy to correct the part that's wrong and add a little notice that tell people they can use a simpler way.
**DamianGTO Ultimate kernel. 350MB Ram. 600HZ. all ext2. Steam Rom. Js5**

@ DamianGTO: After reading the thread over, it seems the steps laid out by the OP are working for many people. I believe it is your intention to streamline / update the guide. This is the wrong place. If you have suggestions for the OP, please do it via PM and no longer in this thread. The language barrier may have made things worse here than they really need to be. I think if you could clearly delineate to the OP (via a well constructed PM to him), I'm sure he would appreciate the help, and credit you for your suggestions.
To sum up. Please move your discussion to PM. If the OP chooses not to respond, please leave him and this thread alone. The guide seems to work for many as it stands.
Thank you for your consideration and cooperation on this matter.

overground said:
@ damiangto: After reading the thread over, it seems the steps laid out by the op are working for many people. I believe it is your intention to streamline / update the guide. This is the wrong place. If you have suggestions for the op, please do it via pm and no longer in this thread. The language barrier may have made things worse here than they really need to be. I think if you could clearly delineate to the op (via a well constructed pm to him), i'm sure he would appreciate the help, and credit you for your suggestions.
To sum up. Please move your discussion to pm. If the op chooses not to respond, please leave him and this thread alone. The guide seems to work for many as it stands.
Thank you for your consideration and cooperation on this matter.
Click to expand...
Click to collapse
+1000000000

Great guide and tutorial! Exactly what I was looking for! Now can anyone advise on the steps to create a flashable zip file on CWM instead of Odin? Any tips would be greatly appreciated.

[Q] could someone help me in Bluetooth.apk?

I did some modifications to Bluetooth share in /system/app/Bluetooth.
But after that I pushed the app via adb...then a lot of error messages that said (Bluetooth Share Stopped).
Then I removed the modified Bluetooth app and pushed the stock one via adb and rebooted the device but the error message still appears although I make
1) wipe cache+dalvik
2) reflash the kernel
Why the error message still appears although I used the stock unmodified app.
Where is the problem?
Could someone help me with this problem?
Here are some logs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk

samep said:
Check your ROM zip for symlink. Different Bluetooth Sharing apk may require different different libbluetooth_jbi.so if linked to /system/app/Bluetooth/lib/arm folder from /system/lib/libbluetooth_jni.so For that reason, you have to watch for 0 bit lib files when pulling application from another ROM flashed on phone. (It may been a symlink if true).
Did you try verifying permissions and ownership and clearing data for Bluetooth Sharing and reboot?
Got a backup? If not, try dirty flashing ROM. You may just have to start over. Consider making a backup before making changes.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
How to verify permission and ownership from terminal?
Yes I have a backup but I want to know more about the problem.
I have some logcat about the problem.
It may help to figure out what happened
And

Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk

samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Thank you very much @samep
Yes that works like a charm.
Recreate the symlink solve my problem.

samep said:
Could be mismatch of apk and lib. Did you replace both and set a new link?
It's easy to set with a root browser.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
can u give me a easy throughput as a newbie ?

hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443

hessamx said:
can u give me a easy throughput as a newbie ?
Click to expand...
Click to collapse
Mr. JAVI said:
I think the members moved on to oyher endeavors. Not much activity on the Sprint Note 4. However, I used this method posted by Lawyer-06 to port some system apps and CSC files from my stock rooted rom to a customer rom I was having issues with.
https://forum.xda-developers.com/showpost.php?p=60831252&postcount=3443
Click to expand...
Click to collapse
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk

samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
thanks for replying but i have log cat and its said cant find some files can u help me ?
E/AndroidRuntime(11055): Process: com.android.bluetooth, PID: 11055
E/AndroidRuntime(11055): java.lang.RuntimeException: Unable to instantiate application com.android.bluetooth.btservice.AdapterApp: java.lang.ClassNotFoundException: Didn't find class "com.android.bluetooth.btservice.AdapterApp" on path: DexPathList[[zip file "/system/framework/javax.obex.jar", zip file "/data/app/com.android.bluetooth-2/base.apk"],nativeLibraryDirectories=[/data/app/com.android.bluetooth-2/lib/arm64, /data/app/com.android.bluetooth-2/base.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]
Click to expand...
Click to collapse

hessamx said:
thanks for replying but i have log cat and its said cant find some files can u help me ?
Click to expand...
Click to collapse
Sorry. Gotta say I'm not experienced with resolving an issue like this. Not sure what you're doing when getting this logcat? References to zipped files? Should they be zipped?
What I would do in a situation like this and ensure I've done everything properly. Could be a simple mistake.
Otherwise, no idea if this helps you or not but a little searching found this blog:
https://javarevisited.blogspot.com/2011/08/classnotfoundexception-in-java-example.html?m=1
If Java tutorials makes sense to you, there's some suggested fixes to look into. Maybe it helps? Best wishes you resolve this and learn enough to help the next guy.
Sent from my PH-1 using Tapatalk

samep said:
Nice tutorial share. Thanks for helping.
What may be missing is linking the lib so the application works. It's a matter of checking original file as installed on phone before replacing and duplicating with a root browser. Long press the lib file, scroll through options, select link to this folder (maybe last option) and then browsing and selecting same folder location as seen from original link. Hint: the lib linking and appearance in its location will look the same when linked properly.
In the case of this thread, unzipping the ROM and reading the install scripts for proper linking may have been done to link the files after installing. The Bluetooth application simply needed to know where to get it's vital resources to work with. There are exceptions where replacing apk and lib, setting permissions, clearing data and rebooting aren't enough. Developers may write install scripts into patch zip accordingly as needed to get this done without a ROM update. Or even alternately in an aroma installer. Or those that test ROMs to support a developer may need to do this manually in that support capacity. Then again, it could be user in another country or region needing to make changes for themselves in order to use a developed ROM.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.

Mr. JAVI said:
I just want to say, thank you samep. I really appreciate your input on this subject. Your way of explaining this is well put and your points are valid. Bluetooth issues is something I have not had in any custom rom as of yet. However, I like to be prepared and knowledge is power.
Thought I'd give a little of my personal background followed by a few questions. I have no formal education with computers or Android. Although, I have not been a member on XDA for very long, I have been on this site for many years. Having lost my previous N4,
the only n910ps for sale were on the latest update 5DQ15. The fused 5 aboot prevents downgrading to previous firmwares. No chance of downgrading the boot or modem without SW REV CHECK Odin fail. Fortunately, 6.0 MM roms can still be flashed. With every single custom rom I flashed, my hotspot settings disappeared, except stock rooted deodexed roms. in which the hotspot setting remained. I remember reading a post somewhere on XDA stating that it was in CSC others.xml so I copied the entire CSC in stock rooted rom to external sd then flashed the custom rom and with the tutorial in the link above I replaced the custom roms CSC's with the stock rooted CSC's. Rebooted to TWRP wiped dalvik /chache and booted the phone. My Hotspot now appeared in the custom rom settings. However, I am not questioning your information. In fact, I remember reading an XDA thread about custom rom development that specifically backs up what you stated. More to it than simple copy and past, Its just I didnt know any other way. Although this worked for me with setting option , I know the phones Bluetooth connection is a bit more intricate than a simple CSC others.xml.
Which brings me to my question and I quote "Long press the lib file, scroll through options, select link to this folder (maybe last option)" What root browser do you recommend. This option is not provided as an option when I long press with my current root file manager. Yea, I know ES file manager has been kick of Google PS but Im still using it . LOL.. I wish to thank you ince again for your very informative posts.
Click to expand...
Click to collapse
I can appreciate your background and effort and even the experiences you share. Best wishes for your success.
I used to use script manager pro for a root browser. When I started working with developers in XDA, they pointed me to Root Explorer by speedsoftware (link below). I use it exclusively since and find it as capable as the other. I had gotten this one years earlier as a free promotional app on Amazon Prime through their Android app store. I was ecstatic when the developers of Root Explorer asked for my license key to transfer it to Google Play! Really? I asked, not expecting satisfaction, and they complied stating they've done it for others as well. It's their discretion and pleasure to do so. The app is still in Google Play; I get my updates there now.
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
But I haven't done much at all since leaving the Note 4 and Sprint. I forget so much when not using it. Sad but true and being honest. I miss those days but always wanted better data coverage and a faster phone. But even that's a work in progress.
Sent from my PH-1 using Tapatalk

[MOD][N][UNLOCKED]Disable the new N (show just the text one)

Change Verified Boot Screen
The idea is to make the new N boot verified boot screen look like the one of MM/LL.
The main goal here is not to disable the bootloader unlock warning completely!
Its just the N one is annoying the ppl more it seems
Before using this mod:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After using this mod:
Reason where this request is coming from:
kessaras said:
Didn't you notice a 30mb around difference in size?
They added full screen splash with crap.
1st without splash.
2nd with splash
Click to expand...
Click to collapse
lol.. yea.
I analyzed the bootloader stack of N and the change is that from N on this "verifiedboot" message is splitted:
before (LL, MM) it was just in aboot (and it is still here as a fallback) and the new one with the "visit link" stuff is called from a partition named raw_resources.
now what happens when you restore:
as the raw_resources partition is not part of the TWRP bootloader backup it will not be restored and so after u flashed MM and then restore a backup of N with TWRP it will still have the
raw_resources of MM.
The test scenario 1
If my theory is correct that would means:
If you flash just the raw_resources of N now (because you see the text-only boot screen after TWRP restore) it should display the N verifiedboot boot screen again. would be great if you could try that.
that also means that when u have the N verifiedboot boot screen and flash the raw_resources partition of MM it will be the old boot screen again. would be great if you could try this as well.
The test scenario 2
once the above is tested and so my theory is verified the correct way on fixing this will be changing the relevant parts of raw_resources.bin accordingly instead of using the one of MM
in the downloads section you find a test with a modified N raw_resources (zeroed out 0x113A up to 0x123D).
The test results
kessaras said:
1. test using backup worked. so i test old raw. worked.
2. test raw from h811 worked.
3. test with this raw in download section worked.
4. test with old bootloader and new raw (from N-LG) worked , i had old bootloader with new splash.
all worked !
Click to expand...
Click to collapse
WARNING: There is a risk to flash this... if it is not working as expected which may result in a soft brick. its very unlikely as this partition is not that sensitive but... u have been warned
Recommended installation
Download (click) the LG-G4_N-bootloader_discreet_verifiedbootmsg.zip and LG-G4_N-bootloader_discreet_verifiedbootmsg.zip.md5
boot into TWRP and push both files in the same directory
Flash LG-G4_N-bootloader_discreet_verifiedbootmsg.zip
Reboot & Enjoy
Manual Installation
As usual doing a full backup before starting with DLM Backup - Option B is absolutely recommended!
Download (click) the modified N raw_resources image
boot into TWRP
Push the image to the device: adb push raw_resources_simpleverifiedbootmsg.bin /tmp/raw.img
Flash the image: adb shell "dd if=/tmp/raw.img of=/dev/block/bootdevice/by-name/raw_resources"
Enjoy
All-in-one installation
if you'd prefer to flash a ZIP instead:
@kessaras has created a flashable ZIP containing this modification in his v29 firmware package.
Beware: This will flash the full N bootloader stack ! Not the above modification only. Thats usually nothing bad with this but if you use another then v29 you may not like the result..
I understood that the following does contain the full v29 / N firmware
Download
Credits
@kessaras for his brave testing
.
XDA:DevDB Information
disable the N verifiedboot splash, Tool/Utility for the LG G4
Contributors
steadfasterX, @kessaras
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2017-09-01
Created 2017-08-31
Last Updated 2019-07-12

reserved
i will also modify my flashable firmwares and use the old raw_resources.
Thank you for finding out where that splash was !
Great work as always !

Thx for your hard work!!
Anyone already tested? Does this work? Currently on holiday without access to PC with adb. Thx
Gesendet von meinem LG-H815 mit Tapatalk

popy2006 said:
Thx for your hard work!!
Anyone already tested? Does this work? Currently on holiday without access to PC with adb. Thx
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
it sais in the op.......... me ........ !!!
am i not enough as a tester ? ;p it pains my heart , you hurt my feelings

kessaras said:
it sais in the op.......... me ........ !!!
am i not enough as a tester ? ;p it pains my heart , you hurt my feelings
Click to expand...
Click to collapse
well ... does it work as described??
have you tested my described ideas?
and if so: which of the above test scenarios and with what results?
sfx

steadfasterX said:
well ... does it work as described??
have you tested my described ideas?
and if so: which of the above test scenarios and with what results?
sfx
Click to expand...
Click to collapse
That's the information missing [emoji3]
Gesendet von meinem LG-H815 mit Tapatalk

steadfasterX said:
well ... does it work as described??
have you tested my described ideas?
and if so: which of the above test scenarios and with what results?
sfx
Click to expand...
Click to collapse
both are working.
and test .3: use the old raw is also working !
all tested and working
popy2006 said:
That's the information missing [emoji3]
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
mate if there was a bug we would have already fixed it. im a perfectionist too. i hate bugs.
@steadfasterX you can link them to my ahf to use the <..._no_splash>.zip 29A if they hate that splash. Already uploaded since earlier this morning.
https://www.androidfilehost.com/?fid=745425885120759121

kessaras said:
both are working.
and test .3: use the old raw is also working !
all tested and working
mate if there was a bug we would have already fixed it. im a perfectionist too. i hate bugs.
@steadfasterX you can link them to my ahf to use the <..._no_splash>.zip 29A if they hate that splash. Already uploaded since earlier this morning.
https://www.androidfilehost.com/?fid=745425885120759121
Click to expand...
Click to collapse
hey awesome! great that this hack works !!
so just to be totally sure that we talk about the same:
you have flashed the raw_resources_simpleverifiedbootmsg.bin file attached here in the download section???
thanks again for testing!
sfx

steadfasterX said:
hey awesome! great that this hack works !!
so just to be totally sure that we talk about the same:
you have flashed the raw_resources_simpleverifiedbootmsg.bin file attached here in the download section???
thanks again for testing!
sfx
Click to expand...
Click to collapse
1. test using backup worked. so i test old raw. worked.
2. test raw from h811 worked.
3. test with this raw in download section worked.
4. test with old bootloader and new raw (from N-LG) worked , i had old bootloader with new splash.
all worked !

kessaras said:
1. test using backup worked. so i test old raw. worked.
2. test raw from h811 worked.
3. test with this raw in download section worked.
4. test with old bootloader and new raw (from N-LG) worked , i had old bootloader with new splash.
all worked !
Click to expand...
Click to collapse
amazing! :highfive:
ofc I will refer to your all-in-one variant as well.
EDIT:
OP updated
.

my bootscreen looks like in the picture "After using this mod:".
Have just flashed first the @kessaras v29a stock zip file.
So have i'll done something wrong?
Another question: Is it possible to get back the LG logo bootscreen with the little "BL unlocked" text in the left upper corner?
The orange text is annoying.
thx
pOpY

popy2006 said:
my bootscreen looks like in the picture "After using this mod:".
Have just flashed first the @kessaras v29a stock zip file.
So have i'll done something wrong?
Another question: Is it possible to get back the LG logo bootscreen with the little "BL unlocked" text in the left upper corner?
The orange text is annoying.
thx
pOpY
Click to expand...
Click to collapse
Kessaras has my change added to his zip so no need to do this here again when you used the linked all in one zip in my OP.
Well regarding the text at top I'm not sure tbh. This could be harder to implement as this requires a change in aboot which is much more risky ofc... On the other hand.. I could remove it there completely..
sfX
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Kessaras has my change added to his zip so no need to do this here again when you used the linked all in one zip in my OP.
Well regarding the text at top I'm not sure tbh. This could be harder to implement as this requires a change in aboot which is much more risky ofc...
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I have just installed the v29 G4 H-ROM over MM and I still have the old Bootloader unlocked message, on the top left corner.

polfrank said:
I have just installed the v29 G4 H-ROM over MM and I still have the old Bootloader unlocked message, on the top left corner.
Click to expand...
Click to collapse
Yes. The boot screen changes only when you flash the N bootloader stack.
sfX
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Kessaras has my change added to his zip so no need to do this here again when you used the linked all in one zip in my OP.
Well regarding the text at top I'm not sure tbh. This could be harder to implement as this requires a change in aboot which is much more risky ofc... On the other hand.. I could remove it there completely..
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I have flashed Kessaras "LG-H815_Stock_Nougat.zip" on about 21.08.2017.
This thread/mod is newer!?
I havent flashed anything from this thread but have the centered orange text from the second picture!?
I have no clue why?
Ok, changing aboot is risky, so we should avoid this but completly removing or replacing that orange text would be nice.
Do you have a working jtag? If so it isnt that risky, because you can restore a working aboot, right?
thx for keeping the G4 development alive
pOpY

popy2006 said:
I have flashed Kessaras "LG-H815_Stock_Nougat.zip" on about 21.08.2017.
This thread/mod is newer!?
I havent flashed anything from this thread but have the centered orange text from the second picture!?
I have no clue why?
Ok, changing aboot is risky, so we should avoid this but completly removing or replacing that orange text would be nice.
Do you have a working jtag? If so it isnt that risky, because you can restore a working aboot, right?
thx for keeping the G4 development alive
pOpY
Click to expand...
Click to collapse
not sure about what u flashed.
It may has different partitions inside then the newer ones.. I personally have no N installed so i cannot tell what has happened but you could do me a favor when exec this in Android:
adb shell
su
md5sum /dev/block/bootdevice/by-name/aboot
md5sum /dev/block/bootdevice/by-name/raw_resources
please paste the output of the above.
EDIT:
forget the above. when you have flashed the bootloader ZIP of kessaras the following happens:
aboot get replaced (the orange text version is added)
raw_resources gets NOT replaced (thats why the orange fallback version of aboot gets displayed)
you get the new annoying screen only when you flashed raw_resources which will happen when you flash e.g. the modded F500 kdz etc.
thx
sfX

Remove it completely!

steadfasterX said:
not sure about what u flashed.
It may has different partitions inside then the newer ones.. I personally have no N installed so i cannot tell what has happened but you could do me a favor when exec this in Android:
adb shell
su
md5sum /dev/block/bootdevice/by-name/aboot
md5sum /dev/block/bootdevice/by-name/raw_resources
please paste the output of the above.
EDIT:
forget the above. when you have flashed the bootloader ZIP of kessaras the following happens:
aboot get replaced (the orange text version is added)
raw_resources gets NOT replaced (thats why the orange fallback version of aboot gets displayed)
you get the new annoying screen only when you flashed raw_resources which will happen when you flash e.g. the modded F500 kdz etc.
thx
sfX
Click to expand...
Click to collapse
The message is not removed. The message will always be there we like it or not and removing a warning message of the manufacturer is against policy normally.
What we removed was the splash image with a triangle inside , big fonts for the warning and the advertisement to visit a link.
Edit:
Maybe we can do a smaller size for those fonts. That can be done

kessaras said:
The message is not removed. The message will always be there we like it or not and removing a warning message of the manufacturer is against policy normally.
What we removed was the splash image with a triangle inside , big fonts for the warning and the advertisement to visit a link.
Edit:
Maybe we can do a smaller size for those fonts. That can be done
Click to expand...
Click to collapse
font stuff and such require to rework aboot or better bc less risky a reworked raw resources.
but removing completely is likely more easy then that.
I work on an unofficial unlock so.. removing a message like this is my smallest legal problem.....
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
not sure about what u flashed.
It may has different partitions inside then the newer ones.. I personally have no N installed so i cannot tell what has happened but you could do me a favor when exec this in Android:
adb shell
su
md5sum /dev/block/bootdevice/by-name/aboot
md5sum /dev/block/bootdevice/by-name/raw_resources
please paste the output of the above.
EDIT:
forget the above. when you have flashed the bootloader ZIP of kessaras the following happens:
aboot get replaced (the orange text version is added)
raw_resources gets NOT replaced (thats why the orange fallback version of aboot gets displayed)
you get the new annoying screen only when you flashed raw_resources which will happen when you flash e.g. the modded F500 kdz etc.
thx
sfX
Click to expand...
Click to collapse
thx, that makes sense.
So the orange text is the smallest "warning" i can go for now
Would be nice if you find a solution to completly remove it.
pOpY