Develop Bugs

LG Fathom / VS750 kitchen and tools

Hi guys, here's some stuff for you to play and cook custom roms for your beloved(?) fathom.
I'm sorry for the delay but I really couldn't release those tools before.
Please note that I don't have a tool to decrypt other roms. To decrypt those vs750 roms, I had to hack the flash procedure, using an ARM disassembler attached on the flashing tool during a flash. It took me almost 2 weeks to find out a way to get decrypted files without bricking the phone, so hopefully you'll enjoy this and will build great Fathom roms.
Special thanks to trueg for experimenting/testing these tools.
So what do you need ?
- the last lg kitchen (available here)
- a decrypted rom (v5 or v7 available the the bottom of the kitchen's 1st post)
OR
- a full vs750 v7 kitchen (everything ready to cook)
mirror : bad upload, back soon
*****************************
Full vs750 v7 Kitchen info :
- SYS is already extracted (in 21000 folder)
- XIP is already modified to work with erviuskitchen (no more dsm files)
- OEM is stock v7, nothing more, nothing less
Build Procedure :
- Add your packages to EXT folder as usual
- Launch erviuskitchen.exe
- Select vs750, 21000 for ext, sys, xip
- Choose the packages you want to add/remove
- Check 6.5 aku and build rom
- Launch start.bat
- Select vs750 (9)
- Hit "u" to build rom.bin (you must use "vs750" as the beginning of the file name)
- flash it as described below
*****************************
Now the steps to flash the phone :
1- Install drivers
- LGUnitedMobileDriver_S4981CAN33AP22_ML_WHQL_Ver_3.3
- LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0
- LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0
You should easily find them (or more recent version) using your favorite search engine.
2- Install the flash tool
The only one that I know of being able to flash decrypted roms is LGNPST. Sorry, you'll have to search for it on the web (shouldn't be too difficult to find).
If using lgnpst, you'll also need to register this dll (using regsvr32 vs750.dll in a dos command prompt)
3- Connect the phone
To be able to connect the vs750 to lgnpst, you have to be in composite mode (on the phone, go to "settings/connections/Switch usb" then select "VzAccess Manager", click "save" and finally wait for it to reboot.
It's possible to flash this phone in emergency mode (if anything goes wrong and the fathom doesn't boot), but if you do so, you might lose your nv (and MEID info). To boot in emergency mode, shutdown your phone, unplug it, then press the "5" key on the keyboard and while keeping it down, plug the usb cable.
Don't do it unless necessary.
4- Save NV (just to be able to recover in case of problems)
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe, it should detect your phone (filename on the top right panel should be "VS750.dll").
- Click on "phone settings", wait a few secondes for a new window to appear
- Click on read button
- It will create a VS750_COMx.nvs in C:\LG Electronics\LGNPST
- Close the windows and click on "click here to continue".
5- Flash the Rom
- Put your phone in composite mode
- Plug the phone to your pc
- Launch LGNPST.exe
- Go in provision Tab (should be selected by default)
- Select Upgrade
- BIN file : "c:\VS750\BIN\VS750XXX5.BIN"
- Check SCR File, then select "C:\VS750\SCR\VS750VZ7_04.scr"
- Check PRL, Nam1 (uncheck nam2), select "C:\VS750\PRL\58006 - EVDO OEM Factory Default.prl"
- Don't check Eri file
- Click on "start"
- Keep fingers crossed for approximately 10min. The phone will reboot a few times, this is normal.
- Enjoy your 1st VS750 custom rom
Also note that for lgnpst to accept your rom, its name will need to start with "vs750".
And don't worry, there is almost no risk of really bricking the phone (especially if you saved the nvs).

I can confirm that you don't need to be too concerned about bricking your phone. As long as you can boot in to emergency mode and you have a backup of your NV data (made with LGNPST - it's very important that you do this - heck make two copies) you can recover it from an unbootable state.
TrueG

Would you be able to provide a pre-configured pack for the Fathom? I am trying my best to figure out how to get the kitchen working, but I haven't gotten it to fully work.
Thanks in advance.

-EDIT- I need to go back to school and learn to read - I saw LGNPST written 3 times, but only 1 was the program. The other 2 were component addons for it, all 3 having version numbers attached to the filename (hence my confusion lol).
@Pizzaboy: I'll help out with getting a filepack together. Which version of windows are you working with? Win7/WinXP, 32bit/64bit
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit

I run 7, both 32 and 64. My main dev is a 64bit system, and my porta-dev is a 32bit.
I've tried following the directions on the kitchen page, but I can't seem to get the XIP to work. It throws errors when I have to start pushing buttons.

da_reeseboy said:
@Trueg: Which version of windows are you working with? Win7/WinXP, 32bit/64bit
Click to expand...
Click to collapse
XP 32bit
TrueG

I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.

da_reeseboy said:
I guess I'll start with a WinXP 32 bit pc, and once I have it working right there I'll move on to a Win7 machine.
...my weekend is planned lol.
Click to expand...
Click to collapse
If you get something working on XP, i'll be able to get it working on 7.
I'm mostly lost on getting the V5 ROM set to work in the kitchen. I've never done a ROM before, and most of the tutorials are either really long and confusing, or really short and confusing...

Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?

da_reeseboy said:
Are you just trying to flash a rom after going thru the kitchen or are you trying to build on a different sys version from the one in whichever decrypted rom you are using?
Click to expand...
Click to collapse
When i hit step 9 in the Kitchen walkthrough, I push "realloc p" and it throws errors. Then when I get to the kitchen, it can't see the XIP and won't let me build a ROM.

@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.

spocky12 said:
@pizzaboy192 : I think the errors you're getting are a "normal" behavior of xipport. I don't understand why the xip is not generated though.
Anyway, I've just uploaded a complete vs750 v7 kitchen. Just follow the instructions on 1st post to build the rom.
Click to expand...
Click to collapse
could you make a v5 one too? V7 has too many bugs to make it a base personally.

Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.

spocky12 said:
Sorry, what I uploaded was based on my previous work on a rom and is fully tested (I won't upload a kitchen not tested to successfully build and flash a rom). Not sure I will have time to do the same on v5 in the next few days.
Click to expand...
Click to collapse
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?

pizzaboy192 said:
I"m not going to complain. Maybe we can actually fix the broken files in the ROM.
How would we go about using other WM files from the COM3+ builds in the kitchen? Would this make it possible to bake in fun features? Would it also be possible to bake-out OEM features like the stupid Arcsoft stuff?
Click to expand...
Click to collapse
Totally possible, we just need to have a working base to start from.
Thanks Spocky for the uploads.

I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.

pizzaboy192 said:
I'd love to start with a V5 base so that I don't have to remove all the Arcsoft junk. I'd just have to replace a set of reg keys and bake in a few files. Seems like it would make more sense. Plus it'd get rid of that cheap android-esque homescreen.
Click to expand...
Click to collapse
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.

da_reeseboy said:
I totally understand that. I'm running into errors with the v5 build too, so I just want to be able to successfully build and flash something to my phone to start. Once I have that (pulling the wheelchair out of the closet and blowing the dust off, getting rolling again in an ervius kitchen) I can start changing things.
Its kinda depressing to me to run into errors and not remember what causes them... a sign that its been way too long.
Click to expand...
Click to collapse
I wonder if we could hybridize this... Take the OEM stuff from the V5 rom and the XIP from V7... would it work?

It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.

da_reeseboy said:
It'd be pretty easy to do, both are running the same basic windows mobile platform. I personally would like to compare the drivers used to see if there are any newer versions in v7.
Click to expand...
Click to collapse
I'm waiting for files to copy on my netbook and I'll see what happens and if the ROM builds.
I'd be a little cautious of drivers, as there's some reason that there were so many issues with the 3G connection dropping on the V7 rom, I'd want to pin it on the WWAN drivers...

2016 version (new fingerprint scanner, combined sim/sd)

Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile

Nice! Can you provide a dump from /system and /boot maybe?

BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?

Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask

BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted

Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.

flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?

I will do
Edit: OK, see if there will be an answer.

Thank you flo1k!

I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?

ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)

FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising

Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished

FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?

Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....

FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.

The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.

I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work

These are great news!
"Which ones do you need?"
Probably all of them

Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!

how i remove startup verizon logo ? urgent

hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4

remember i have not .zip file in media folder

Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.

-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?

Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.

-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again

Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms

-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc

Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/

-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom

Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.

-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible

Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.

-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow

-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?

Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461

-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719

Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.

NOST - Improved Version of OST LA 6.0.4 (v0.6, 02. Mar 2019)

"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon

I tried this is working,nice tool.
Thanks dev.

Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs

Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?

Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?

THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.

Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.

THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.

Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.

hey there! wonderful tool to have. Thank u so much

Not working in my laptop say a software need a to update

Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.

THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?

ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).

THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it

How to flash it's says this...

Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?

KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.

Can you please upload Oreo December update stock and patched boot image. TIA

Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.

Question Problems with the connectivity on Poco F3 LineageOS + Magisk

I using my Poco F3 since a few month with lineageOS and I'm quite happy. The only problem: Wify and mobile data. Most of the time there is an exclamation mark in the topline on the icons for wify and mobile data.
I tried all the normal stuff:
– reboot the mobile phone (which sometimes really works)
– reboot thr router
– check the settings
– swap the sim cards (because sometimes I was only able to call somebody with one of the sim cards
With the last update of lineageOS it seems that the sim cards work again properly for calls, but not for mobile data.
Despite the exclamation marks surfing und emails works fine. I just can't synchronise my calendar via DAVdroid.
Any hint is appreciated.

are you using the recommended firmware version?
i had some issues with sounds with newer firmware versions

Good question.
I didn't change the firmware. How can I check, which version is runing on my device?

Idk how you'd check the firmware version but you could install the latest firmware for your region regardless.
Or if LineageOS recommends a specific FW version, install that instead.
Xiaomifirmware.com is one place where you can find official MIUI ROM versions and Firmware (/vendor).
You can just install it in Recovery, install itself takes a couple of seconds since Firmware is around 100 MB.

Isn't there an official site to download the firmware?

RunnersHai said:
Isn't there an official site to download the firmware?
Click to expand...
Click to collapse
xiaomifirmwareupdater.com is a reputable source for official Xiaomi FW and ROMs.
Xiaomi do have a website where you can DL ROMs but it's bad.

Perfect, thx a lot. I will try,if it works. Keep fingers crossed ;-D

Sorry, I don't get any further. I only find complete Roms with 3.1 GB and more. But not a vendor with the code POCO F3 Global - V13.0.3.0.SKHMIXM as mentioned on the website of Lineageos.org (https://wiki.lineageos.org/devices/alioth/fw_update). Even the direct link downloads a complete Rom.
And can I install the vendor with my linux computer or should I switch windows and the mi-tool as mentioned on some websites?
Thanks for your help.

Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.

RunnersHai said:
Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.
Click to expand...
Click to collapse
You're right. I checked out that website and those links are indeed full Recovery MIUI ROMs, not just firmware.
Those instructions show you how to manually flash just the firmware from a ROM.zip
However, you don't need to do that. Here is a link to just the firmware for that exact ROM:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
v13.0.3 seems rather old to me, but if it's their recommendation, then I guess go ahead. After all you simply want these problems to go away.
How to flash:
Simply boot into Recovery and do ADB Sideload
"adb sideload firmware.zip"
If you want to use the Payload Dumper anyway:
In your Linux Machine, open the Payload Dumper folder,
right-click an empty space in the folder, click "Open in Terminal",
type "payload-dumper-go -o . " and drag & drop the MIUI_ROM.zip into the Terminal (this will autofill the path to that ROM),
Hit Enter.
Then, open the created folder where all the extracted partition-images are. Open that folder in Terminal, and do the fastboot commands listed on the LineageOS-website that you linked to me.

Great thanks a lot for your help. New stuff to learn – that's great.
Unfortunately I figured out that the reason for the problems could be a wrong setting in my AFWall+. I will double check that and if it's not the reason, I will follow your instructions. Thanks a lot for your work – awesome.

heres the firmware archive,no need for full rom and fastboot commands
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com