Before reading any further
This thread is best viewed in a browser!
Mobile apps may parse the XDA formatting not correctly and may screw things up.
About
{
"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"
}
steadfasterX's All-in-one LG Tool (SALT)
SALT is able to communicate with your device while in download mode and provides these features:
Detects your:
ARB
device model
firmware version (short)
firmware version (full)
country of firmware
Secure device state
Battery Level
Is able to:
working completely without any LG dll (no more issues with replacing LGUP_xxxx.dll anymore!)
backup your device (predefined modes: full & basic and since v3.20 even a custom mode)
extract KDZ files
display your partitions (including what each partition is like bootloader etc!)
open a shell on the device*
ERASE (HOLY SH*** this is DANGEROUS!) one or multiple partitions
verify a taken backup (read all about this here)
self-update
In development (already working on LP firmware! NOT on MM or N! read the Note):
Flashing a folder (e.g. from a previous backup)
Flashing a KDZ
IMPORTANT NOTE: Do not use the underlying code backend (lglaf /partitions.py) to RESTORE image files (yet)!
Reason:
LG has changed the mechanism in MM and later for writing to a partition! It seems that the reason is that each write must be authenticated differently or at least another one for the fsync.
Explained in detail
Besides the writing this may also be an issue afterwards: filesize
for reference here is a dump of a lgup flashing
Requirements
mAid (fka as FWUL) (recommended)
No requirements as SALT and everything needed is included there!
Highly recommended: booting mAid from USB stick to avoid any connection issues.
Ensure you use the latest mAid release and start SALT by opening the LG folder on the desktop.
Now just click the update button once SALT is started to ensure you have the latest and greatest SALT version!
Linux:
I recommend mAid (fka FWUL) in general but SALT is made to be run on any Linux (if you can set it up).
Requirements to install before beginning:
yad, git, python3, python3-pyusb, python3-crypto, python-zstandard (python3), python-pip (python3) and pkexec/policykit
(instead of pkexec/polkit gksudo will work too but this has been removed from many distributions)
On mAid:
open the Folder "LG" from the desktop and start SALT
On Arch:
sudo pacman -Sy polkit git xterm python-pyusb python-crypto python-pip
yay -Sy yad python-zstandard (hint: you may need to install yay first)
sudo pip3 install cryptography
on Manjaro:
sudo pacman -Sy polkit yad git xterm python-pyusb python-crypto trizen python-pip python-zstandard
sudo pip3 install cryptography
on *buntu, Debian, Mint and on all derivates of those:
sudo apt install policykit-1 yad git xterm python3 python3-usb python3-pip
sudo pip3 install zstandard
sudo pip3 install cryptography
you may need to setup your udev rules as well: android-udev-rules thats another reason why I recommend mAid this is all implemented there out of the box..!!
Windows:
Windows users should use SALT in mAid which is highly recommended for many operations with Android devices. Also read & follow the above topic "mAid (fka FWUL) (recommended)".
Installation (not needed on mAid! Just open the LG folder and start SALT)
open a terminal
type:
git clone https://github.com/steadfasterX/SALT.git
cd SALT
bash install-desktop.sh
read the output and if required copy the SALT.desktop file manually to your Desktop.
double click the SALT icon or while in a terminal start SALT with: sudo ~/SALT/salt
When starting SALT the first time you will be prompted to install necessary backend tools.
Choose YES to install them!
Note:
Even when the downloads tab in this project will contain releases the most up-to-date code can be fetched via the above way only.
Nevertheless you can download the tar file from the Downloads tab but ensure that you're using the latest code by starting an update (Update button in SALT) afterwards.
Usage
Start the device in download mode and connect it to the PC.
Start SALT.
Usually the download mode should be fully ready in 20 - 60 seconds after you see the cycling arrow screen.
But some devices needs up to >= 90 seconds until SALT can detect your device.
If you still get trouble connecting boot the device in download mode and let it connected that way while rebooting mAid (fka FWUL) or your personal Linux.
Known Issues
A current list of all known issues can be found at the bugtracker
Support
Android + SALT Support: [matrix] || Telegram
mAid Support: [matrix] || Telegram
CI/CD/Automation: [matrix] || Telegram
Credits (without them no SALT)
SALT is based on:
YAD (yet another dialog) -> GUI
the awesome LGLAF code and reverse engineering by Peter Wu & friends
-> general communication with the device like: flash, dump, getinfo, erase, list partitions, ...
kdztools by Elliott Mitchell -> extracting KDZ files
MANY enhancements by steadfasterX -> bring all together plus much more
SALT's own sources:
SALT
Patched LGLAF
Patched kdztools
Special credits:
@runningnak3d for his incredible reverse engineering skills which makes SALT better and better each day it's great to have you in the community !
tuxuser for making LAF communication on Nougat possible and for his great support!
XDA:DevDB Information
SALT - teadfasterX's [A]ll-in-one [L]G [T]ool, Tool/Utility for the LG G4
Contributors
steadfasterX
Source Code: https://github.com/steadfasterX/salt
Version Information
Status: Stable
Created 2017-12-11
FAQ - Frequently Asked Questions
1) How can I get into the download mode?
Boot your phone into download mode--> the following guide is 100% working and bulletproof:
take out battery and unplug USB cable
plugin USB cable to your PC (while battery ist still out)
wait until you see the missing battery icon (question mark within a battery symbol)
press Volume up and while keeping it pressed put battery in (take care that you do not press the power button)
keep pressing Volume up until you see "Download mode"
If that does not work for you try it this way instead:
unplug USB cable
power down device or pull out battery
put battery back
press Volume up and while keeping it pressed plugin USB cable to your PC (take care that you do not press the power button)
keep pressing Volume up until you see "Download mode"
Your phones screen should look similar to this afterwards:
View attachment 4284063
2) Does SALT work on LOCKED devices ?
Oh what a great question YES it DOES.
But keep in mind.. even when you can flash/erase partitions with SALT this still requires either valid/untouched pure LG files or an unlocked device.
3) Can I unlock my LG G4 device with SALT?
Holy moly --- NO! YES! ( https://leech.binbash.rocks:8008/g4-links/ for the guide)
4) What is the meaning of ARB?
Anti-Roll-Back a stupid mechanism to brick your device. Read on here
5) Do I need a specific ARB version to work with SALT?
You can start and use SALT with any ARB version. Later when flashing is fully implemented you will be warned when your ARB is lower then then one you want to flash.
6) Which firmware versions does SALT support?
Any of lollipop, marshmallow and nougat
7) Which devices does SALT support?
In theory ANY LG device supported by the lglaf backend.
Confirmed devices are:
- G2
- G3
- G4 (H810, H811, H812, H815, H818, H819, VS986, LS991, F500)
- G5: unknown may only work with modifications like mentioned in the Release Notes for v3.20
- G6 (H871) only with modifications: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support"
- V10 (H900)
- V20 (H910) only with modifications: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support" OP -> topic "Support"
- yours -> report your device by uploading the debug log from the advanced menu and share the bpaste link!
- again: in theory any LG device will work with SALT . All newer devices (G5 and later) will just need the mentioned modification: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support" OP -> topic "Support"
.. this will change in one of the next versions as I will implement an automatic detection , of course!
8) SALT is prompting me after a backup for verification. I have many Warnings|Errors what does that all mean?
Read on here about he verification feature in SALT: MD5 verification
9) I have installed SALT already. Is it possible to just update it?
Of course thats one of the awesome features in SALT.
Since v3.7 SALT will check for a new version on startup automatically and prompt you to update if necessary.
If it ever fails just click the update button at the bottom.
10) I have installed SALT already. Is it possible to switch between STABLE and STREAM channels?
Note: STREAM (fka TESTING) may have issues, brick your device, let your phone or PC explode. so use it with care.
So if you wanna still switch the channels click the update button at the bottom first.
If you want to be on/switch to the STABLE channel choose Target mode = STABLE
Click update and restart SALT afterwards.
If you want to be on/switch to the STREAM channel choose: Target mode = TESTING
Click update and restart SALT afterwards.
11) I have a partition file with the extension: [ bin | image | img | mbn ]. How can I convert this?
The extension is not important. The way how you extract files - is. That's why I say all the time use SALT.
On Windows the file extension matters a lot which is not the case for Linux/Android.
So if you see a guide mentioning to use a "bin" file and you have the file but with an extension of "image" (or vice-versa) it does not matters.
There is no need to convert anything as they all are just raw image files.
12) I want to backup but SALT says I have too less space for that! How can I get more disk space in FWUL (or my VM)?
Read FAQ #5 in the FWUL thread (yes even when you are using Windows and do not run FWUL but any other Linux + SALT) and setup a shared folder with enough disk space as described.
Point to that new shared folder (ensure you do not use spaces in the foldername and that you have created a new folder in the start of the shared folder) when asked for a backup location in SALT.
13) I do *NOT* use FWUL because I have my own Linux running and you told me to install tmate. How?
Current instructions can be found here: https://tmate.io/
Ensure you create a SSH key as that is needed to start tmate later:
Code:
ssh-keygen -b 4096 -f ~/.ssh/tmate -N ''
(note: the characters '' are 2 single quotes)
Install tmate on Arch Linux / Arch variants like Manjaro, ..:
Code:
trizen -Sy tmate
or: yaourt -Sy tmate (yaourt is [U]DEPRECATED[/U]!)
Install tmate on Ubuntu / Ubuntu Variants like Kubuntu, Linux Mint, ... :
Code:
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:tmate.io/archive
sudo apt-get update
sudo apt-get install tmate
14)Is there a Windows version of SALT available or planned?
No. NEVER. Just use FWUL which has SALT already included and everything setup to manage your Android device.
If you have issues in running FWUL report them in the FWUL thread.
15)What is GPT compability (LG G4 only)?
I saw people often confused about that option and here is what it is and does:
1) This is only valid for the LG G4 models. If you have another one ignore it.
2) If you have a LG G4 and not UsU'd (so an official unlockable model) - just ignore it.
3) If you have a LG G4 and UsU'd your device (or planning to do so) this option is for you.
Background:
SALT checks the partition table (GPT) to find out what ROM model is compatible with an UsU'd device. The reason is quite easy: all G4 models have the same hardware (except the h818 but thats another story). Due to the incredible amount of country specific models not many ROMs exist for every model so I checked what's needed to bring a ROM meant for another model to an UsU'd device. I recognized quickly that the partition table is different on several models and even on a same model with another firmware (e.g. between LP and MM it changed for some models). The only thing we need on custom ROMs for the G4 is a correct sized system partition as that one differs for some. Another thing needed on some (mostly US models) is a carrier partition instead of a cust one. Basically that's all SALT checks at the end as if a ROM expects to mount the carrier partition it must be there.
TL;DR
The GPT compatibility shows what ROM you can install on an UsU'd device - if there is none for your specific model.
16) Is it possible to extract TOT files with SALT?
No but you can use this windows tool to extract TOTs: https://forum.xda-developers.com/showthread.php?t=2600575
17) I want to backup/extract my user data (internal storage) with SALT and my device is encrypted. Is that possible and can SALT unencrypt that data?
SALT is doing 1:1 copies of your partitions which is really 100% identical to what is on your phone. If your data is encrypted SALT will backup that in the current state which means encrypted because within the download mode your userdata partition does not get mounted. So what does that mean? Yes you can backup your userdata but .. you can NOT mount it afterwards as it is just encrypted data. afaik there are no tools available to unencrypt but I may be wrong (let me know if you are aware of any).
Does it makes sense to backup encrypted data? Depends on what you want to get. If you want to have a really full 1:1 copy of the current phone it might be useful if you are able to restore that data (e.g. via TWRP). Keep in mind though that encryption usually needs more partitions to be restored (e.g. persist or others) which contain information/keys,... as well.
TL;DR
You can but it is usually not very useful.
18) Isn't it possible to flash with SALT (yet)?
Well the flash mode is not enabled by default - while it can be enabled manually. The main issue here is that you can easily hard brick your device and I tried to find a way of making it possible to avoid that. Unfortunately and due to the wide range of models SALT supports this can't be guaranteed.
That is the first reason and the second is that LG limited/restricted the LAF protocol used for communicating with the device in later versions and so flashing will simply not work on these.
Fully supported are LAF protocol version: 1000001, 1000002. Anything later like 1000004 (e.g. Nougat on LG G4) will NOT work.
If you want to take the risk read on here
1000a) I have an issue not listed here - what should I do?
1000b) Is there a SALT logfile and how can I share it?
While your device is connected in download mode:
Advanced Menu -> SALT Debug log -> Upload button -> right click the link or open it in a browser and copy from there
Picture guide:
Changelog
Checkout FAQ #9 for howto update to this brand new release
Legend for the summary topics:
Fix/New (SALT): Fixes & Enhancements of the SALT main application - what you see and work with
Fix/New (lglaf): Fixes & Enhancements of the USB communication backend which SALT uses under the hood
Fix/New (kdztools): Fixes & Enhancements of the KDZ extraction backend which SALT uses under the hood
v3.22
Released: 2020-03-09
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github
Full changelog (kdztools): at github
Summary changelog:
ATTENTION FOR FWUL (v2.x, v3.x) users:
Upgrading to this Version WILL BREAK SALT without doing a FULL system upgrade (which can take hours, downloading multiple GB, may even break on low RAM systems)
Instead it is highly recommended to use the new mAid nightlies which are in RC phase already and so reasonable stable.
Fix (kdztools): some fixes for KDZ extractions
Fix (SALT): UsU and ARB detection in rare cases
Fix (SALT): no output for several lglaf based operations
Fix (SALT): backup (custom) progress bars
Fix (SALT): when a folder or filename contained a space SALT failed to parse and extract
Fix (SALT): several things around ARB and ARB detection
Fix (SALT): screwed part listing
Fix (SALT): log upload
New (SALT): added a pre-check after the user selected a directory: when the path exists and containing image files the user get prompted to either retry or continue.
HINT:
Newer devices using UFS storage (e.g. G5, G6, ..) still need to switch to the DEVELOP/TESTING branch (see FAQ)
Older releases
v3.21
Released: 2018-12-21
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github (this version compared with the previous release)
Full changelog (kdztools): at github (this version compared with the previous release)
Important Note:
From this release on the system requirement have changed!
You need to ensure you install the python module "zstandard" - read the OP for how or when using FWUL use the latest FWUL nightly which comes with everything pre-installed.
Summary changelog:
New (kdztools): KDZ extractions have been EXTREMELY enhanced. Means we can now even extract newer KDZ files up to the latest LG flagship (e.g. G7/V30).
This has been fully achieved by runningnak3d ! it's always a pleasure to work with him
Fix (kdztools): extraction failed when a KDZ had unallocated space (e.g. some H811 ones but also others)
Fix (SALT): python version for KDZ/DZ extraction
Fix (SALT): Browsing the mounted directory after using the Image mounter (advanced menu) will now use full permissions by default
New (SALT): mounting an image (advanced menu): previously when a user hasn't unmounted an image file he had to unmount it manually (terminal). now SALT offers a dialog to do so for the user instead.
New (SALT): from now on SALT can detect when a user tries to mount an image file from a vbox shared folder and denies mounting it
Fix (lglaf): Do not use "G4" as detected model (as there is no safe way to identify a model via the usb info)
Hint from a previous release: preparation for UFS devices (all newer LG models). Hint: you can use SALT now on newer devices but this requires a manual change in lglaf atm:
Code:
cd ~/programs/lglafng
git checkout develop
The above is NOT needed on non-UFS devices (like the G2,G3,G4, ...). If you are unsure open the advanced menu in SALT and check if the partition listing is working - if it is empty try the above otherwise you don't need to.
The above handling and UFS detection will be done automatically in a future release of SALT!
v3.20
Released: 2018-11-30
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): nothing has changed
Summary changelog:
Fix (SALT): when the size of a backup cannot be calculated SALT continues with the free disk space check nevertheless
Fix (SALT): "direct flashing" message optimized
Fix (SALT): permissions on logfiles and all 3rd party paths
Fix (SALT): User detection was wrong (pkexec) and so the resulting program paths as well
ATTENTION:
You may get prompted to re-download lglaf, sdat2img and kdztools due to the corrected paths. Just do so and it will be fixed next time you start SALT.
New (SALT): Introducing the CUSTOM backup mode! Now you can not just choose from the predefined BASIC and FULL mode but also can choose CUSTOM. This CUSTOM mode allows to choose from your existing partitions. Plus: while backing up a beautiful multi-progress bar is showing the progress.
New (SALT): preparation for UFS devices (all newer LG models). Hint: you can use SALT now on newer devices but this requires a manual change in lglaf atm:
Code:
cd ~/programs/lglafng
git checkout ufs-test
The above is NOT needed on non-UFS devices (like the G2,G3,G4, ...). If you are unsure open the advanced menu in SALT and check if the partition listing is working - if it is empty try the above otherwise you don't need to.
The above handling and UFS detection will be done automatically in a future release of SALT!
v3.19
Released: 2018-08-23
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): nothing changed
Summary changelog:
Fix (SALT): (G4 - UsU) fixed a bug where direct flashing was incorrectly shown regardless if it was possible or not
Fix (SALT): incorrectly shown laf download window
New (SALT): completely re-design of the installer (thx for the pkexec contribution ThePiGuy). all details for the new installer here: commit
New (SALT): prepare for multi model support in SALT (not G4 only anymore)
New (SALT): available SALT features and main window screen are now based on the detected LG model
v3.18
Released: 2018-08-10
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github (this version compared with the previous release)
Summary changelog:
Fix (SALT): Backup function now allows to use paths with spaces within its name
Fix (lglaf): Backup was not working since 3.17 (CR function was not implemented for the backup function)
v3.17
Released: 2018-07-31
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github (this version compared with the previous release)
Summary changelog:
New (SALT): Force Challenge/Response mode available for devices where the automatic detection fails (PERMISSION DENIED in SALT debug log)
How it works and where to find >click here<
New (SALT): provide feedback while detecting the ARB of a KDZ
New (SALT): completey re-worked "Convert an image (ZIP)" in the advanced menu. SALT is now able to mount any image file instead of just system (e.g. vendor,...)
New (SALT): some KDZ extract enhancements (like cleanup etc)
New (SALT): a lot of changes for the upcoming direct flashing function (not enabled by default)
Fix (SALT): ARB detection of KDZs in some cases
New (lglaf): added CR force-on, force-off (details)
Fix (lglaf): disable direct flashing on laf > 100001 again (was accidentally still enabled)
Fix (lglaf): When direct flashing failing raise a real error including a non zero returncode
v3.16
Released: 2018-05-06
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): Improved backup / Free disk space check
v3.15
Released: 2018-04-25
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): Select/Deselect button when extracting a KDZ
v3.14
Released: 2018-04-17
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
Fix(SALT): SALT was unusable in rare cases
v3.13
Released: 2018-03-22
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): Mount button after extracting a KDZ added
Fix(SALT): remove flashing warning when user skips device connection
Fix(SALT): several issues when directories containing spaces (I recommend to still avoid spaces in dir and filenames)
Fix(kdztools): rare issues when extracting some KDZ files
v3.12
Released: 2018-03-21
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
Fix(SALT, kdzmgr): several issues for extracting KDZ files
v3.11-0
Released: 2018-03-16
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): extracting a KDZ will now detect and show the ARB !
Fix(SALT): extracting KDZ in a path with space or special chars failed (empty partition list on extract)
v3.10-1
Released: 2018-03-13
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
Fix(SALT): UsU hashes on some devices can't be set correctly (country related)
Fix(SALT): UsU check for ARB <=2 implemented to avoid damage
v3.9-0
Released: 2018-03-09
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): binary checker for fastboot on start
New(SALT): improved error handling for binary checks on start
Fix(SALT): UsU hashes on some devices can't be set correctly
v3.8-2
Released: 2018-03-07
Full changelog (SALT): at github (this version compared with the previous release)
v3.7-12
Released: 2018-03-05
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): update checker for SALT on start
New(SALT): added a mount option for image files
NEW(SALT): checking LAF version and offering a compatible LAF if needed/recommended
NEW(SALT): complete re-design of UsU flashing verification using a hash table
NEW(SALT): added a fastboot flashing fallback on UsU flashing when partial success
Fix(SALT): a LOT of UsU stuff..
Fix(SALT): will not let open as much windows as before (e.g. closing advanced menu dialog on unlock click etc)
Fix(SALT): important UsU related fixes -> if you want to unlock by UsU do not use any previous version!
Fix(SALT): do not start UsU flashing on incompatible LAF versions
v3.6-5
Released: 2018-02-14
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): Upload/Paste your SALT logfile with a single click!
New(SALT): many important stuff related to UsU
Fix(SALT): SALT does not start in rare circumstances
v3.5-7
Released: 2018-02-05
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): Main GUI completely re-worked to fit on smaller screens
New(SALT): main screen now detect and display: LAF protocol, IMEI and serial (removed "Secure device" as its meaning is unknown anyways)
HINT: IMEI and serial will never be written into the logfile!
New(SALT): added the feature to extract/convert/mount system.dat files (from LP up to Oreo 8.1) - requested by @kessaras
New(SALT): KDZ extract HEAVILY improved (details)
Fix(SALT): UsU related stuff
Fix(SALT): modemst info
v3.1-1
Released: 2018-01-09
Full changelog (SALT): at github (this version compared with the previous release)
Summary changelog:
New(SALT): adding a GPT compatibility info for UsU ROM flashing
Fix(SALT): garbage on UsU check in log
v3.0-7
Released: 2018-01-08
Full changelog (SALT): at github (this version compared with the previous)
Summary changelog:
New(SALT): Full UsU support
New(SALT): Full Nougat bootloader support
Fix(SALT): several .. read the full changelog
v2.1-0
Released: 2018-01-05
Full changelog (SALT): at github (this version compared with the previous)
Summary changelog:
New(SALT): Backup now uses $HOME/salt_backup as default backup path
New(SALT): If backup path does not exists it will be auto-created now
Fix(SALT): Verify backup was broken (thx @cowsngrass or the report)
v2.0-7
Released: 2018-01-03
Full changelog (SALT): at github (this version compared with the previous)
Full changelog (lglaf): at github (all commits up to release date)
Full changelog (kdztools): at github (all commits up to release date)
Summary changelog:
New(lglaf, SALT): Backup now shows a progress bar instead of that creepy log output
New(SALT): adding a Retry button on SALT startup
New(lglaf, SALT): replaced legacy auth method with new chall/response
New(SALT): adding support for mbn firmware files
New(SALT): adding UsU (Unofficial steadfasterX Unlock) detection
Fix(lglaf): Timeout issues on some devices resulting in no detection
Fix(lglaf): Some devices even when using an older LAF protocol version required challenge/response
Fix(SALT): md5 verify on some devices
Fix(kdztools): when on master (so STABLE) branch kdz extract was not possible
and many more (check github changelogs above)
1.1-5
Released: 2017-12-15
Full changelog: at github (this version compared with the previous)
Summary changelog:
New feature: MD5 verification of backup
This feature may not be available on every device but SALT will check after a backup automatically if your device supports
md5 verification and offers you an option to do so.
Fix: ARB detection was wrong on H811
1.0-14
Released: 2017-12-11
Changelog:
first public release
Full changelog at github
Thank you, very nice tool.
Now it is very easy to backup all of my data (H818P, v29a firmware).
Btw, it is working on kubuntu, I just had to google for how to set up some dependencies.
Engelm said:
Thank you, very nice tool.
Now it is very easy to backup all of my data (H818P, v29a firmware).
Btw, it is working on kubuntu, I just had to google for how to set up some dependencies.
Click to expand...
Click to collapse
besides: sudo apt install yad git gksu python-pyusb python-crypto which dependencies else were needed?
I want to add them to the FAQ...
thx for reporting the working state!
If you don't mind: can you start SALT and grab the debug log just after starting SALT up?
you find it in the advanced menu. just copy everything and paste it in a PM would be nice..
Cheers
sfX
steadfasterX said:
besides: sudo apt install yad git gksudo python-pyusb python-crypto which dependencies else were needed?
I want to add them to the FAQ...
thx for reporting the working state!
If you don't mind: can you start SALT and grab the debug log just after starting SALT up?
you find it in the advanced menu. just copy everything and paste it in a PM would be nice..
Cheers
sfX
Click to expand...
Click to collapse
No other dependencies were needed, but I also use this OS for some development... so maybe something was already installed.
Maybe I could help if someone else has some dependencies missing.
Look like a great tool thank you very much for your time and effort!
I have LG G4 version LS991ZVD_03, can I ?
Satrio Yudho said:
I have LG G4 version LS991ZVD_03, can I ?
Click to expand...
Click to collapse
Read FAQ 5,6 and 7 https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864/post74811095
Sent from my LG-H815 using XDA Labs
SALT v1.1-5 released
1.1-5
Released: 2017-12-15
Full changelog: at github (this version compared with the previous)
Summy changelog:
New feature: MD5 verification of backup
This feature may not be available on every device but SALT will check after a backup automatically if your device supports
md5 verification and offers you an option to do so.
Fix: ARB detection was wrong on H811
Existing users can update with just a click:
open SALT (no need to have a connected device - just press the SKIP button when asked)
click at the most left button at the bottom
leave everything on its defaults in the next window and start the update.
close SALT and that's it
New feature - MD5 verification explained
Once you have taken a backup SALT will check if your device generally supports md5sum verification and if yes prompting you about this.
Choosing yes there is highly recommended to ensure that your files are really valid.
Once SALT has finished the verification you will see a summary window presenting you the results of the verification.
You can open details about each result by clicking the Details button:
As you can see in the above example I got 29 OKs, 18 WARNINGS but 0 ERRORS so what does that mean?
What OK means is simple: both the backup file and the partition on the device could be hashed and the verification matches.
A verification WARNING means that SALT is not able to generate a md5sum on your device. Even when the first generic check was successful some devices blocking some or even all partition for this verification.
So actually this means that the backup itself went well (the dump itself) but we cannot verify it against the device.
So should you be concerned about a WARNING ? No.
... but you should be concerned about ERRORS ofc. A verification ERROR means that both the backup file and the partition on the device could be hashed and the verification mismatches which is definitively an issue with the backup. If that happens take a fresh reboot into download mode again re-open SALT and start the backup again (ensure you have enough free disk space!).
and for fun:
you can just take a backup again in the same folder (nothing gets overwritten as SALT will not overwrite) and when prompted about the verification do not click but reboot your device into Android. once booted power down and open download mode again and wait some seconds until you can be sure that its fully started in download mode. then press the verification button to find which partitions have changed by a simple boot into android.
Cheers
steadfasterX
Can't backup H815 - no partion detected error code 0x8000010a (LAF_ERROR_ACCESS_DEN
Hi ,
I read about SALT and it seems to be great tool. unfortunately it do not work well for me. I've attempted to update my phone to nougat and I've try to create backup but it failed. Later on I've found out that no partition was detected on the phone. The following happened :
- SALT installed on UBUNTU 17.04 - with minor issues that were solved
- Phone detected automatically
- Phone can be rebooted by SALT
- Error during backup
Log file is attached bellow.
Phone was delivered with Android 5.1 Updated to Marshallow via LG Bridge No root nor boot loader unlocked. After upgrade to Marshallow shows Warning massage after boot "Current version is not available for user. Can't find matched cust for NT-code mmx/mnc[],subset[]" , This messages is one of the reasons for attempting to flash Nougat, second one is battery life.
I'm looking for the following help. Waht steps need to be taken to backup the device and update it to Nougat v29a.
Can you please help ?
2017-12-19 16:25:43: Starting SALT v1.1-5:STABLE!
****************************************************
2017-12-19 16:25:43: F_EGO: started
2017-12-19 16:25:43: F_EGO: /tmp/salt.lock created
2017-12-19 16:25:43: DEVCON before: 99
2017-12-19 16:25:43: F_CHKDEVCON: started
2017-12-19 16:25:44: F_CHKDEVCON: Device seems to be connected!
2017-12-19 16:25:44: RET: 0
2017-12-19 16:25:44: DEVCON after: 0
2017-12-19 16:25:44: F_GETINFO: started
2017-12-19 16:25:44: F_CDARB: started
2017-12-19 16:25:46: EMPTY ARB DETECTED:
2017-12-19 16:25:46: Please send this log and the SBL1 dump in /tmp/sbl1.err
2017-12-19 16:25:46: F_CDARB:
2017-12-19 16:25:46: F_CDARB: DEVARB=0, DEVARBEMPTY=1
2017-12-19 16:25:46: F_CDARB: ended
battery_level:100 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-19 16:25:46: F_GETINFO: ended
2017-12-19 16:25:46: parsing arb:0:1
2017-12-19 16:25:46: parsing battery_level:100
2017-12-19 16:25:46: parsing device_sw_version:H81520g
2017-12-19 16:25:46: parsing secure_device:S
2017-12-19 16:25:46: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-19 16:25:46: parsing model_name:LG-H815
2017-12-19 16:25:46: parsing target_country:COM
2017-12-19 16:25:53: F_BACKUP: started with these arguments:
2017-12-19 16:25:55: F_BACKUP: choosen backup type was 1, Full, 0 KB
2017-12-19 16:25:57: F_BACKUP: choosen target directory was /tmp
Traceback (most recent call last):
File "/root/programs/lglafng/extract-partitions.py", line 72, in <module>
main()
File "/root/programs/lglafng/extract-partitions.py", line 65, in main
with partitions.laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-19 16:26:07: F_MSGOK: started
2017-12-19 16:26:07: F_ADVMENU: started
2017-12-19 16:26:10: getlog script started
bodziak said:
Hi ,
I read about SALT and it seems to be great tool. unfortunately it do not work well for me. I've attempted to update my phone to nougat and I've try to create backup but it failed. Later on I've found out that no partition was detected on the phone. The following happened :
- SALT installed on UBUNTU 17.04 - with minor issues that were solved
- Phone detected automatically
- Phone can be rebooted by SALT
- Error during backup
Log file is attached bellow.
Phone was delivered with Android 5.1 Updated to Marshallow via LG Bridge No root nor boot loader unlocked. After upgrade to Marshallow shows Warning massage after boot "Current version is not available for user. Can't find matched cust for NT-code mmx/mnc[],subset[]" , This messages is one of the reasons for attempting to flash Nougat, second one is battery life.
I'm looking for the following help. Waht steps need to be taken to backup the device and update it to Nougat v29a.
Can you please help ?
2017-12-19 16:25:43: Starting SALT v1.1-5:STABLE!
****************************************************
2017-12-19 16:25:43: F_EGO: started
2017-12-19 16:25:43: F_EGO: /tmp/salt.lock created
2017-12-19 16:25:43: DEVCON before: 99
2017-12-19 16:25:43: F_CHKDEVCON: started
2017-12-19 16:25:44: F_CHKDEVCON: Device seems to be connected!
2017-12-19 16:25:44: RET: 0
2017-12-19 16:25:44: DEVCON after: 0
2017-12-19 16:25:44: F_GETINFO: started
2017-12-19 16:25:44: F_CDARB: started
2017-12-19 16:25:46: EMPTY ARB DETECTED:
2017-12-19 16:25:46: Please send this log and the SBL1 dump in /tmp/sbl1.err
2017-12-19 16:25:46: F_CDARB:
2017-12-19 16:25:46: F_CDARB: DEVARB=0, DEVARBEMPTY=1
2017-12-19 16:25:46: F_CDARB: ended
battery_level:100 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-19 16:25:46: F_GETINFO: ended
2017-12-19 16:25:46: parsing arb:0:1
2017-12-19 16:25:46: parsing battery_level:100
2017-12-19 16:25:46: parsing device_sw_version:H81520g
2017-12-19 16:25:46: parsing secure_device:S
2017-12-19 16:25:46: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-19 16:25:46: parsing model_name:LG-H815
2017-12-19 16:25:46: parsing target_country:COM
2017-12-19 16:25:53: F_BACKUP: started with these arguments:
2017-12-19 16:25:55: F_BACKUP: choosen backup type was 1, Full, 0 KB
2017-12-19 16:25:57: F_BACKUP: choosen target directory was /tmp
Traceback (most recent call last):
File "/root/programs/lglafng/extract-partitions.py", line 72, in <module>
main()
File "/root/programs/lglafng/extract-partitions.py", line 65, in main
with partitions.laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-19 16:26:07: F_MSGOK: started
2017-12-19 16:26:07: F_ADVMENU: started
2017-12-19 16:26:10: getlog script started
Click to expand...
Click to collapse
many thanks for writing such a qualified report
Please open SALT
Click the Update button
and set everything to develop like here:
Click Update to switch to the testing release and close SALT when prompted.
start SALT again and attach again the Debug log. I have just adjusted the debug log output to identify the issue for you.
plus (if its generated) the file /tmp/sbl1.err which MAY gets generated once you opened SALT.
.
SALT log data from development branch
Hi,
I've followed the instructions. SALT was updated to development branch 29 changes in 3 files . kdztools and lglaf no changes detected. New log generated and attached. Same error happed when reading ARB - 0x8000010a (LAF_ERROR_ACCESS_DENIED). File /tmp/sbl1.err was not created at all. Tested just after starting SALT and when attempting backup.
I've also found out discussion on similar issue - but there is is too much low level details in it for me :
Try to check on github.com the following link /Lekensteyn/lglaf/issues/7
Sorry - I'm not allowed to publish external links
2017-12-20 09:56:35: Starting SALT v1.2-0:TESTING!
****************************************************
2017-12-20 09:56:35: F_EGO: started
2017-12-20 09:56:35: F_EGO: /tmp/salt.lock created
2017-12-20 09:56:35: DEVCON before: 99
2017-12-20 09:56:35: F_CHKDEVCON: started
2017-12-20 09:56:35: F_CHKDEVCON: Device seems to be connected!
2017-12-20 09:56:35: RET: 0
2017-12-20 09:56:35: DEVCON after: 0
2017-12-20 09:56:35: F_GETINFO: started
2017-12-20 09:56:35: F_CDARB: started
Traceback (most recent call last):
File "/root/programs/lglafng/partitions.py", line 369, in <module>
main()
File "/root/programs/lglafng/partitions.py", line 330, in main
with laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:56:37: EMPTY ARB DETECTED:
2017-12-20 09:56:37: Please send this log and the SBL1 dump in /tmp/sbl1.err
2017-12-20 09:56:38: 2017-12-20 09:56:37,718 LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
2017-12-20 09:56:37,721 partitions: DEBUG: Using Protocol version: 0x1000001
Traceback (most recent call last):
File "/root/programs/lglafng/partitions.py", line 369, in <module>
main()
File "/root/programs/lglafng/partitions.py", line 330, in main
with laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:56:38: F_CDARB:
2017-12-20 09:56:38: F_CDARB: DEVARB=0, DEVARBEMPTY=1
2017-12-20 09:56:38: F_CDARB: ended
battery_level:95 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-20 09:56:39: F_GETINFO: ended
2017-12-20 09:56:39: parsing arb:0:1
2017-12-20 09:56:39: parsing battery_level:95
2017-12-20 09:56:39: parsing device_sw_version:H81520g
2017-12-20 09:56:39: parsing secure_device:S
2017-12-20 09:56:39: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-20 09:56:39: parsing model_name:LG-H815
2017-12-20 09:56:39: parsing target_country:COM
2017-12-20 09:56:39: Reboot button script started
2017-12-20 09:56:55: F_BACKUP: started with these arguments:
2017-12-20 09:57:00: F_BACKUP: choosen backup type was 1, Full, 0 KB
2017-12-20 09:57:02: F_BACKUP: choosen target directory was /tmp
Traceback (most recent call last):
File "/root/programs/lglafng/extract-partitions.py", line 72, in <module>
main()
File "/root/programs/lglafng/extract-partitions.py", line 65, in main
with partitions.laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:57:18: F_ABOUT: started
2017-12-20 09:59:49: F_ADVMENU: started
2017-12-20 09:59:51: getlog script started
Click Update to switch to the testing release and close SALT when prompted.
start SALT again and attach again the Debug log. I have just adjusted the debug log output to identify the issue for you.
plus (if its generated) the file /tmp/sbl1.err which MAY gets generated once you opened SALT.
.[/QUOTE]
bodziak said:
Hi,
I've followed the instructions. SALT was updated to development branch 29 changes in 3 files . kdztools and lglaf no changes detected. New log generated and attached. Same error happed when reading ARB - 0x8000010a (LAF_ERROR_ACCESS_DENIED). File /tmp/sbl1.err was not created at all. Tested just after starting SALT and when attempting backup.
I've also found out discussion on similar issue - but there is is too much low level details in it for me :
Try to check on github.com the following link /Lekensteyn/lglaf/issues/7
Sorry - I'm not allowed to publish external links
2017-12-20 09:56:35: Starting SALT v1.2-0:TESTING!
****************************************************
2017-12-20 09:56:35: F_EGO: started
2017-12-20 09:56:35: F_EGO: /tmp/salt.lock created
2017-12-20 09:56:35: DEVCON before: 99
2017-12-20 09:56:35: F_CHKDEVCON: started
2017-12-20 09:56:35: F_CHKDEVCON: Device seems to be connected!
2017-12-20 09:56:35: RET: 0
2017-12-20 09:56:35: DEVCON after: 0
2017-12-20 09:56:35: F_GETINFO: started
2017-12-20 09:56:35: F_CDARB: started
Traceback (most recent call last):
File "/root/programs/lglafng/partitions.py", line 369, in <module>
main()
File "/root/programs/lglafng/partitions.py", line 330, in main
with laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:56:37: EMPTY ARB DETECTED:
2017-12-20 09:56:37: Please send this log and the SBL1 dump in /tmp/sbl1.err
2017-12-20 09:56:38: 2017-12-20 09:56:37,718 LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
2017-12-20 09:56:37,721 partitions: DEBUG: Using Protocol version: 0x1000001
Traceback (most recent call last):
File "/root/programs/lglafng/partitions.py", line 369, in <module>
main()
File "/root/programs/lglafng/partitions.py", line 330, in main
with laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:56:38: F_CDARB:
2017-12-20 09:56:38: F_CDARB: DEVARB=0, DEVARBEMPTY=1
2017-12-20 09:56:38: F_CDARB: ended
battery_level:95 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-20 09:56:39: F_GETINFO: ended
2017-12-20 09:56:39: parsing arb:0:1
2017-12-20 09:56:39: parsing battery_level:95
2017-12-20 09:56:39: parsing device_sw_version:H81520g
2017-12-20 09:56:39: parsing secure_device:S
2017-12-20 09:56:39: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-20 09:56:39: parsing model_name:LG-H815
2017-12-20 09:56:39: parsing target_country:COM
2017-12-20 09:56:39: Reboot button script started
2017-12-20 09:56:55: F_BACKUP: started with these arguments:
2017-12-20 09:57:00: F_BACKUP: choosen backup type was 1, Full, 0 KB
2017-12-20 09:57:02: F_BACKUP: choosen target directory was /tmp
Traceback (most recent call last):
File "/root/programs/lglafng/extract-partitions.py", line 72, in <module>
main()
File "/root/programs/lglafng/extract-partitions.py", line 65, in main
with partitions.laf_open_disk(comm) as disk_fd:
File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
return next(self.gen)
File "/root/programs/lglafng/partitions.py", line 61, in laf_open_disk
open_header = comm.call(open_cmd)[0]
File "/root/programs/lglafng/lglaf.py", line 264, in call
raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))
RuntimeError: Command failed with error code 0x8000010a (LAF_ERROR_ACCESS_DENIED)
2017-12-20 09:57:18: F_ABOUT: started
2017-12-20 09:59:49: F_ADVMENU: started
2017-12-20 09:59:51: getlog script started
Click to expand...
Click to collapse
ok great thx again. This confirms what I thought.
The important line is: 2017-12-20 09:56:37,721 partitions: DEBUG: Using Protocol version: 0x1000001
I'm in active discussion with Lekensteyn and others to fix/implement things around LGLAF (backend tool in SALT) so I'm aware of this
Background: Older LAF versions do not needed a challenge / response when doing several actions. Newer need them.
Until now we all assumed that we can use the protocol version as an indicator if that challenge/response is needed or not but this seems to be not the case as your example shows.
I also have another user running a H811 with exact the same issue.
So basically this will work for you with a simple change: replacing all occurrences of 0x1000004 with 0x1000001 in lglaf.py and partitions.py but unfortunately this would break then for other users running an older release of LAF. I will implement another detection which then should work for all (hopefully).
.
EDIT: @bodziak could you pls do this in a terminal while in download mode and device connected (no SALT needed):
lsusb
thx!
Editions ??
Hi ,
I'm not quite sure what you mean by "could you pls do this in a terminal while in download mode and device connected (no SALT needed)". Do you mean "replacing all occurrences of 0x1000004 with 0x1000001 in lglaf.py and partitions.py" . So I should:
- connect the device in download mode
- use terminal to edit python files
- start SALT
is it correct sequence ?
Bodziak
steadfasterX said:
ok great thx again. This confirms what I thought.
The important line is: 2017-12-20 09:56:37,721 partitions: DEBUG: Using Protocol version: 0x1000001
I'm in active discussion with Lekensteyn and others to fix/implement things around LGLAF (backend tool in SALT) so I'm aware of this
Background: Older LAF versions do not needed a challenge / response when doing several actions. Newer need them.
Until now we all assumed that we can use the protocol version as an indicator if that challenge/response is needed or not but this seems to be not the case as your example shows.
I also have another user running a H811 with exact the same issue.
So basically this will work for you with a simple change: replacing all occurrences of 0x1000004 with 0x1000001 in lglaf.py and partitions.py but unfortunately this would break then for other users running an older release of LAF. I will implement another detection which then should work for all (hopefully).
.
EDIT: @bodziak could you pls do this in a terminal while in download mode and device connected (no SALT needed):
lsusb
thx!
Click to expand...
Click to collapse
bodziak said:
Hi ,
I'm not quite sure what you mean by "could you pls do this in a terminal while in download mode and device connected (no SALT needed)". Do you mean "replacing all occurrences of 0x1000004 with 0x1000001 in lglaf.py and partitions.py" . So I should:
- connect the device in download mode
- use terminal to edit python files
- start SALT
is it correct sequence ?
Bodziak
Click to expand...
Click to collapse
sorry for the confusion
connect device in download mode to the pc (wait until you see the cycle arrows screen)
open terminal and type: lsusb
gimme the output
no change in code for the above needed.
thx
LSUSB result
Hi,
Here is result from LSUSB
Bus 001 Device 009: ID 1004:633a LG Electronics, Inc.
By the way I was able to backup using SALT by modify the file as suggested. As far as i understand right now i need downgrade the device to android 5 then update it to nougat.An you do not advice to use SALT for that. Correct ?
Bodziak
steadfasterX said:
sorry for the confusion
connect device in download mode to the pc (wait until you see the cycle arrows screen)
open terminal and type: lsusb
gimme the output
no change in code for the above needed.
thx
Click to expand...
Click to collapse
bodziak said:
Hi,
Here is result from LSUSB
Bus 001 Device 009: ID 1004:633a LG Electronics, Inc.
By the way I was able to backup using SALT by modify the file as suggested. As far as i understand right now i need downgrade the device to android 5 then update it to nougat.An you do not advice to use SALT for that. Correct ?
Bodziak
Click to expand...
Click to collapse
thanks.
open a terminal and go into the lglaf folder again: /root/programs/lglaf
then type (this will revert your manual changes as I have implemented a new way of detection):
git reset --hard
start SALT again (no device connected)
execute the UPDATE again
close SALT
connect device
start SALT when download mode is fully up
open advanced menu -> show partitions
when you see the partition listing my brand new fix had worked
pls send in any case the debug log as well
you dont need to downgrade to LP in order to uprade to Nougat. Just flash the TOT.
.
It Works !!!!
Hi,
Your fix is working now . Log is bellow - just removed from it HTML data. See bellow. Can you recommend any specific TOT file ?
Thank for help and prompt response
Bodziak
2017-12-20 15:26:14: Starting SALT v1.2-3:TESTING!
****************************************************
2017-12-20 15:26:14: F_EGO: started
2017-12-20 15:26:14: F_EGO: /tmp/salt.lock created
2017-12-20 15:26:14: DEVCON before: 99
2017-12-20 15:26:14: F_CHKDEVCON: started
aarch64
2017-12-20 15:26:15: F_CHKDEVCON: Device seems to be connected!
2017-12-20 15:26:15: RET: 0
2017-12-20 15:26:15: DEVCON after: 0
2017-12-20 15:26:15: F_GETINFO: started
2017-12-20 15:26:15: F_CDARB: started
2017-12-20 15:26:16,588 partitions: INFO: Wrote 1048576 bytes to -
2017-12-20 15:26:16: F_CDARB:
2017-12-20 15:26:16: ARB valid and 0
2017-12-20 15:26:16: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2017-12-20 15:26:16: F_CDARB: ended
battery_level:100 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-20 15:26:17: F_GETINFO: ended
2017-12-20 15:26:17: parsing arb:0:0
2017-12-20 15:26:17: parsing battery_level:100
2017-12-20 15:26:17: parsing device_sw_version:H81520g
2017-12-20 15:26:17: parsing secure_device:S
2017-12-20 15:26:17: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-20 15:26:17: parsing model_name:LG-H815
2017-12-20 15:26:17: parsing target_country:COM
2017-12-20 15:26:25: F_ADVMENU: started
2017-12-20 15:26:27: F_LISTPARTS: started
2017-12-20 15:26:27: F_GETPARTS: started
2017-12-20 15:26:28: modem,1,32768,208895,2C9C5EC0-5089-C2FD-2BB8-B0D6B55FC969
2017-12-20 15:26:28: pmic,2,229376,230399,E0887475-3501-9541-0995-604BB69779CA
2017-12-20 15:26:28: sbl1,3,230400,232447,E4A4D5BB-85C9-86FA-39B5-6D3E1A116849
2017-12-20 15:26:28: tz,4,232448,234495,A5505947-385B-5172-8592-69ABD5E3F82C
2017-12-20 15:26:28: sdi,5,234496,235519,07EFDA3B-B262-86D1-42DC-A16EF3719745
2017-12-20 15:26:28: hyp,6,235520,236543,D2DAF4F8-F494-F8AF-445B-F7AEEA17BDCC
2017-12-20 15:26:28: rpm,7,236544,237567,4C0D1B93-329C-AB73-7FA7-36D373E9767D
2017-12-20 15:26:28: aboot,8,237568,241663,8D24F8E9-80B6-9926-9225-1B9741F497DA
2017-12-20 15:26:28: sbl1bak,9,241664,243711,B736164F-DBCE-91B4-7C0E-97635A37E655
2017-12-20 15:26:28: pmicbak,10,243712,244735,16294DF1-8874-A104-8040-85DAD0085055
2017-12-20 15:26:28: tzbak,11,244736,246783,C19E6F07-CF19-DFDB-194B-DE650336E75D
2017-12-20 15:26:28: hypbak,12,246784,247807,0E9DDEB4-85E6-CEF7-87AE-2FAAEEA7CDB0
2017-12-20 15:26:28: rpmbak,13,247808,248831,B54BA8EE-5FCD-9BF2-B651-CD5A1D2FC3CC
2017-12-20 15:26:28: abootbak,14,248832,252927,C615F011-743C-D40F-0FB6-1594027DFB8B
2017-12-20 15:26:28: sdibak,15,252928,253951,04F5EC33-21A5-FE27-2A88-0F0EA036FFE9
2017-12-20 15:26:28: limits,16,253952,254975,00258E3B-090A-F71E-FA35-67862A4FE206
2017-12-20 15:26:28: devinfo,17,254976,255999,5BEEF108-1A26-72CC-9009-CE1C4F97EFA9
2017-12-20 15:26:28: apdp,18,256000,257023,FF02DE10-0634-8D65-F3A6-F2C106096830
2017-12-20 15:26:28: msadp,19,257024,258047,AFA69886-0D12-794F-B2B8-182E8B6D836E
2017-12-20 15:26:28: dpo,20,258048,259071,6A5DD444-EDC6-0975-7248-8867FEE7A810
2017-12-20 15:26:28: spare1,21,259072,262143,CEBB7F6C-0111-B41B-2272-569AD420F845
2017-12-20 15:26:28: misc,22,262144,294911,BF82D982-CFAC-EA0E-4B45-91942204DB13
2017-12-20 15:26:28: persist,23,294912,360447,BF06643E-8F51-237B-0D28-0B199C14F0AB
2017-12-20 15:26:28: modemst1,24,360448,363519,E04AEBC1-5925-68FE-4DCC-EA77E9038039
2017-12-20 15:26:28: modemst2,25,363520,366591,8417A7B8-4006-9175-C0F9-846B44B4E2A9
2017-12-20 15:26:28: fsg,26,366592,369663,ED3127E3-F4F7-A60F-8D49-2C790E709221
2017-12-20 15:26:28: fsc,27,369664,370687,9F0BDD06-5207-2139-CBFF-57E3D6D324BE
2017-12-20 15:26:28: ssd,28,370688,371711,DF246A3F-63E9-398F-1152-0A835A3A091D
2017-12-20 15:26:28: keystore,29,371712,372735,02280F6A-D0B0-05B4-8EC0-A2B388541783
2017-12-20 15:26:28: DDR,30,372736,376831,33A0E627-CD91-5BB3-8C3E-EB4FF1628C98
2017-12-20 15:26:28: sec,31,376832,377855,48470F02-90C6-0F79-C6CD-6AD3214F8BF2
2017-12-20 15:26:28: encrypt,32,377856,378879,F99FAEE6-0929-121B-8B9D-341C7AAFFF87
2017-12-20 15:26:28: eksst,33,378880,379903,95478EC7-9779-BCB7-B719-0B690AB33C82
2017-12-20 15:26:28: rct,34,379904,380927,021E62FE-3B12-BE62-A984-292D8FA57809
2017-12-20 15:26:28: persistent,35,380928,385023,47D47D16-CE0B-D069-E355-32A7291416D9
2017-12-20 15:26:28: spare2,36,385024,393215,84D64CA6-A736-00B5-1F20-EC9B8DD4AC38
2017-12-20 15:26:28: laf,37,393216,491519,26EBE353-E019-6B2F-B3A2-A3EAFDC12ED2
2017-12-20 15:26:28: boot,38,491520,573439,441836A1-4500-548F-5C7D-9B0B67D3EAA8
2017-12-20 15:26:28: recovery,39,573440,655359,70349858-D9AB-5A65-5F45-AB1B2349F1F7
2017-12-20 15:26:28: drm,40,655360,671743,97629E9A-6940-7260-3E03-0428128363E8
2017-12-20 15:26:28: sns,41,671744,688127,CA9C961A-A56A-784E-98ED-422D203BB457
2017-12-20 15:26:28: mpt,42,688128,753663,38B7E3E5-322D-A359-43B9-A206C6727178
2017-12-20 15:26:28: factory,43,753664,847871,EE22CFCB-8973-1A18-C462-05F74E14FC64
2017-12-20 15:26:29: fota,44,847872,868351,B9391BEA-A332-F97A-2C93-EF4FCB8E2CE1
2017-12-20 15:26:29: raw_resources,45,868352,876543,C8B74B09-291E-1661-9181-F97011D73B58
2017-12-20 15:26:29: raw_resourcesbak,46,876544,884735,2722471E-9CF4-3B7A-D660-DB9BE7632F2C
2017-12-20 15:26:29: system,47,884736,9363455,3254FDD9-5609-84CE-EFE5-42A160233B47
2017-12-20 15:26:29: cust,48,9363456,9887743,9ECF3D3B-E229-7A2E-FE72-BD0DD8479DC6
2017-12-20 15:26:29: cache,49,9895936,12419071,89C12426-F027-38D2-FF99-1A61A02C9ACF
2017-12-20 15:26:29: userdata,50,12419072,61046783,E394BCDC-DD6D-77B4-E54F-362B3C9CA81C
2017-12-20 15:26:29: grow,51,61046784,61071326,105D7851-F50E-198B-3BB0-B6640B8ED2A0
2017-12-20 15:26:29: (F_GETPARTS) created yad list: true
------ CUT redundant data here --
2017-12-20 15:26:46: getlog script started
2017-12-20 15:30:02: F_EXIT: started
2017-12-20 15:30:02: EXIT: main->end with code 0
usunięty '/tmp/salt.lock'
steadfasterX said:
thanks.
open a terminal and go into the lglaf folder again: /root/programs/lglaf
then type (this will revert your manual changes as I have implemented a new way of detection):
git reset --hard
start SALT again (no device connected)
execute the UPDATE again
close SALT
connect device
start SALT when download mode is fully up
open advanced menu -> show partitions
when you see the partition listing my brand new fix had worked
pls send in any case the debug log as well
you dont need to downgrade to LP in order to uprade to Nougat. Just flash the TOT.
.
Click to expand...
Click to collapse
bodziak said:
Hi,
Your fix is working now . Log is bellow - just removed from it HTML data. See bellow. Can you recommend any specific TOT file ?
Thank for help and prompt response
Bodziak
2017-12-20 15:26:14: Starting SALT v1.2-3:TESTING!
****************************************************
2017-12-20 15:26:14: F_EGO: started
2017-12-20 15:26:14: F_EGO: /tmp/salt.lock created
2017-12-20 15:26:14: DEVCON before: 99
2017-12-20 15:26:14: F_CHKDEVCON: started
aarch64
2017-12-20 15:26:15: F_CHKDEVCON: Device seems to be connected!
2017-12-20 15:26:15: RET: 0
2017-12-20 15:26:15: DEVCON after: 0
2017-12-20 15:26:15: F_GETINFO: started
2017-12-20 15:26:15: F_CDARB: started
2017-12-20 15:26:16,588 partitions: INFO: Wrote 1048576 bytes to -
2017-12-20 15:26:16: F_CDARB:
2017-12-20 15:26:16: ARB valid and 0
2017-12-20 15:26:16: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2017-12-20 15:26:16: F_CDARB: ended
battery_level:100 device_sw_version:H81520g secure_device:S device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0 model_name:LG-H815 target_country:COM 2017-12-20 15:26:17: F_GETINFO: ended
2017-12-20 15:26:17: parsing arb:0:0
2017-12-20 15:26:17: parsing battery_level:100
2017-12-20 15:26:17: parsing device_sw_version:H81520g
2017-12-20 15:26:17: parsing secure_device:S
2017-12-20 15:26:17: parsing device_factory_version:LGH815AT-00-V20g-OPT2-HQ-JUL-20-2016+0
2017-12-20 15:26:17: parsing model_name:LG-H815
2017-12-20 15:26:17: parsing target_country:COM
2017-12-20 15:26:25: F_ADVMENU: started
2017-12-20 15:26:27: F_LISTPARTS: started
2017-12-20 15:26:27: F_GETPARTS: started
2017-12-20 15:26:28: modem,1,32768,208895,2C9C5EC0-5089-C2FD-2BB8-B0D6B55FC969
2017-12-20 15:26:28: pmic,2,229376,230399,E0887475-3501-9541-0995-604BB69779CA
2017-12-20 15:26:28: sbl1,3,230400,232447,E4A4D5BB-85C9-86FA-39B5-6D3E1A116849
2017-12-20 15:26:28: tz,4,232448,234495,A5505947-385B-5172-8592-69ABD5E3F82C
2017-12-20 15:26:28: sdi,5,234496,235519,07EFDA3B-B262-86D1-42DC-A16EF3719745
2017-12-20 15:26:28: hyp,6,235520,236543,D2DAF4F8-F494-F8AF-445B-F7AEEA17BDCC
2017-12-20 15:26:28: rpm,7,236544,237567,4C0D1B93-329C-AB73-7FA7-36D373E9767D
2017-12-20 15:26:28: aboot,8,237568,241663,8D24F8E9-80B6-9926-9225-1B9741F497DA
2017-12-20 15:26:28: sbl1bak,9,241664,243711,B736164F-DBCE-91B4-7C0E-97635A37E655
2017-12-20 15:26:28: pmicbak,10,243712,244735,16294DF1-8874-A104-8040-85DAD0085055
2017-12-20 15:26:28: tzbak,11,244736,246783,C19E6F07-CF19-DFDB-194B-DE650336E75D
2017-12-20 15:26:28: hypbak,12,246784,247807,0E9DDEB4-85E6-CEF7-87AE-2FAAEEA7CDB0
2017-12-20 15:26:28: rpmbak,13,247808,248831,B54BA8EE-5FCD-9BF2-B651-CD5A1D2FC3CC
2017-12-20 15:26:28: abootbak,14,248832,252927,C615F011-743C-D40F-0FB6-1594027DFB8B
2017-12-20 15:26:28: sdibak,15,252928,253951,04F5EC33-21A5-FE27-2A88-0F0EA036FFE9
2017-12-20 15:26:28: limits,16,253952,254975,00258E3B-090A-F71E-FA35-67862A4FE206
2017-12-20 15:26:28: devinfo,17,254976,255999,5BEEF108-1A26-72CC-9009-CE1C4F97EFA9
2017-12-20 15:26:28: apdp,18,256000,257023,FF02DE10-0634-8D65-F3A6-F2C106096830
2017-12-20 15:26:28: msadp,19,257024,258047,AFA69886-0D12-794F-B2B8-182E8B6D836E
2017-12-20 15:26:28: dpo,20,258048,259071,6A5DD444-EDC6-0975-7248-8867FEE7A810
2017-12-20 15:26:28: spare1,21,259072,262143,CEBB7F6C-0111-B41B-2272-569AD420F845
2017-12-20 15:26:28: misc,22,262144,294911,BF82D982-CFAC-EA0E-4B45-91942204DB13
2017-12-20 15:26:28: persist,23,294912,360447,BF06643E-8F51-237B-0D28-0B199C14F0AB
2017-12-20 15:26:28: modemst1,24,360448,363519,E04AEBC1-5925-68FE-4DCC-EA77E9038039
2017-12-20 15:26:28: modemst2,25,363520,366591,8417A7B8-4006-9175-C0F9-846B44B4E2A9
2017-12-20 15:26:28: fsg,26,366592,369663,ED3127E3-F4F7-A60F-8D49-2C790E709221
2017-12-20 15:26:28: fsc,27,369664,370687,9F0BDD06-5207-2139-CBFF-57E3D6D324BE
2017-12-20 15:26:28: ssd,28,370688,371711,DF246A3F-63E9-398F-1152-0A835A3A091D
2017-12-20 15:26:28: keystore,29,371712,372735,02280F6A-D0B0-05B4-8EC0-A2B388541783
2017-12-20 15:26:28: DDR,30,372736,376831,33A0E627-CD91-5BB3-8C3E-EB4FF1628C98
2017-12-20 15:26:28: sec,31,376832,377855,48470F02-90C6-0F79-C6CD-6AD3214F8BF2
2017-12-20 15:26:28: encrypt,32,377856,378879,F99FAEE6-0929-121B-8B9D-341C7AAFFF87
2017-12-20 15:26:28: eksst,33,378880,379903,95478EC7-9779-BCB7-B719-0B690AB33C82
2017-12-20 15:26:28: rct,34,379904,380927,021E62FE-3B12-BE62-A984-292D8FA57809
2017-12-20 15:26:28: persistent,35,380928,385023,47D47D16-CE0B-D069-E355-32A7291416D9
2017-12-20 15:26:28: spare2,36,385024,393215,84D64CA6-A736-00B5-1F20-EC9B8DD4AC38
2017-12-20 15:26:28: laf,37,393216,491519,26EBE353-E019-6B2F-B3A2-A3EAFDC12ED2
2017-12-20 15:26:28: boot,38,491520,573439,441836A1-4500-548F-5C7D-9B0B67D3EAA8
2017-12-20 15:26:28: recovery,39,573440,655359,70349858-D9AB-5A65-5F45-AB1B2349F1F7
2017-12-20 15:26:28: drm,40,655360,671743,97629E9A-6940-7260-3E03-0428128363E8
2017-12-20 15:26:28: sns,41,671744,688127,CA9C961A-A56A-784E-98ED-422D203BB457
2017-12-20 15:26:28: mpt,42,688128,753663,38B7E3E5-322D-A359-43B9-A206C6727178
2017-12-20 15:26:28: factory,43,753664,847871,EE22CFCB-8973-1A18-C462-05F74E14FC64
2017-12-20 15:26:29: fota,44,847872,868351,B9391BEA-A332-F97A-2C93-EF4FCB8E2CE1
2017-12-20 15:26:29: raw_resources,45,868352,876543,C8B74B09-291E-1661-9181-F97011D73B58
2017-12-20 15:26:29: raw_resourcesbak,46,876544,884735,2722471E-9CF4-3B7A-D660-DB9BE7632F2C
2017-12-20 15:26:29: system,47,884736,9363455,3254FDD9-5609-84CE-EFE5-42A160233B47
2017-12-20 15:26:29: cust,48,9363456,9887743,9ECF3D3B-E229-7A2E-FE72-BD0DD8479DC6
2017-12-20 15:26:29: cache,49,9895936,12419071,89C12426-F027-38D2-FF99-1A61A02C9ACF
2017-12-20 15:26:29: userdata,50,12419072,61046783,E394BCDC-DD6D-77B4-E54F-362B3C9CA81C
2017-12-20 15:26:29: grow,51,61046784,61071326,105D7851-F50E-198B-3BB0-B6640B8ED2A0
2017-12-20 15:26:29: (F_GETPARTS) created yad list: true
------ CUT redundant data here --
2017-12-20 15:26:46: getlog script started
2017-12-20 15:30:02: F_EXIT: started
2017-12-20 15:30:02: EXIT: main->end with code 0
usunięty '/tmp/salt.lock
'
Click to expand...
Click to collapse
amazing thx for verifying.
just use the xda search. there is only one TOT available for v29.
Related
Hello! Every time I try to build my DS homebrew app, this comes up.
1>------ Build started: Project: NintendoDS1, Configuration: Debug Win32 ------
1>Performing Makefile project actions
1>Project : error PRJ0002 : Error result 255 returned from 'C:\Windows\system32\cmd.exe'.
1>Build log was saved at "file://c:\Users\adam\Documents\VisualStudio2008\Projects\HelloWorld\NintendoDS1\Debug\BuildLog.htm"
1>NintendoDS1 - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
How do I fix this? It is becoming annoying. CMD works fine.
There are (leaked) OTA updates for Samsung devices floating around.
These files have the .bin extension, but can different types: RBMT multidelta and .zip archives.
The information in this thread are related to RBMT multidelta (RedBend update agent patches).
Using the following steps, the RBMT file is split into delta.* files, ready to be flashed. The only requirement is to have a big enough /cache partition. Else you could play with symlinking the /cache/fota/ folder.
adb push TheNameOfTheOta.bin /sdcard/ota.bin
adb install FOTA.apk
adb shell
su
chmod -R 0777 /cache
Run FOTA application from app drawer
Press the button
Wait a few minutes (or check logcat to see when it's done)
Check the contents of /cache/fota, it should contain *.delta files and fota.status
In the adb root shell prompt enter:
LTE devices: reboot arm11_fota
Tablets: reboot fota
Phones:
echo -n "--install_fota" > /cache/recovery/command
reboot recovery
Wait for OTA update (percentage on screen)
Notes:
You must have the corresponding base ROM installed for the OTA (the required version can be read at the end of the .bin file)
Nadavi reported that the update fails at updating the bootloader. As a workaround, delete delta.Sbl from the fota folder
Arlicc reported that you must have the stock recovery before flashing back to stock with Odin. So flash the package twice, or the stock recovery first then the package.
Donations are always welcome PayPal
PS: Looking for P7300 ICS? -> http://forum.xda-developers.com/showthread.php?t=1893456
The main idea behind the technique consists in wrapping up a JNI interface for libdprw.so. This file is included in syncmldm.apk. Then we deodex syncmldm.odex and figure out the calls to the JNI.
cschmitt's info about the FOTA procedure pointed out some missing pieces.
There's also a working version for Galaxy Note with Gingerbread: Application => Procedure
I would prefer if someone would try the app from the first post and symlink /cache/fota/ to /data/fota/ to see if it works and generalize the problem.
For other devices, I need the dump of /system/app/syncmldm.apk, /system/app/syncmldm.odex and /system/framework/ (whole folder). I'll help as my time permits.
Changelog:
Check existence of /sdcard/ota.bin
Check if it's an RBMT multidelta
UI cosmetics
Todo:
Gather information about other devices
Provide a generalized application
Make the app fully automatic
Hi,
Great to see a truly knowledgable person get into this.
I've only come across a thread that explains how to capture an update .bin file. The good part is that it deals with exactly the same fotaclient process and the same /data/data folders as explained in the skyrocket thread.
This is what I found.
If not anything else it gives an idea about the address of the update servers and where the .bin files are downloaded from.
I bet that the SQlite database exploration will turn up a result as to where the.bin file is stored to be flashed thereafter.
Or what if the wssdmdatabase.db can be edited so that it will have the Software Update process start doing its thing with the .bin.
There is nothing revealing actually within fotaclient.apk.
All very simplistic approaches on my part, bu this is as far/near as my knowledge goes.
I have a very vague idea of the complex stuff you are talking about, but as far as I can understand, you wish to use a JNI wrapper to manually execute the code to split the .bin file.
Isn't there a way to just trigger the Software Update to do its thing with the .bin file in the right place instead?
Probably not the key to everything, but (at least to me) an understandable insight into redbend FOTA and delta files.
http://www.visionmobile.com/rsc/researchreports/Firmware_OTA_research_paper.pdf
Due to health problems, I didn't have time for this matter.
Started again, wrote a JNI Wrapper that loads libdprw.so (that contains the split functions). I have a strange problem when loading it (java.lang.UnsatisfiedLinkError: unknown failure), trying to figure it out...
EDIT: Library loaded, trying to communicate with it's functions...
EDIT2: The package name is hardcoded in the lib, so I need to hex edit it... or grant root privileges to the app
EDIT3: su gets root for the app, but not for the lib
EDIT4: hexing partially works, we still need root for /cache partition
Code:
09-18 18:17:53.960: D/dalvikvm(3122): Trying to load lib /data/data/ro.tracid.fota/lib/libdprw.so 0x4076cee8
09-18 18:17:53.960: D/dalvikvm(3122): Added shared lib /data/data/ro.tracid.fota/lib/libdprw.so 0x4076cee8
09-18 18:17:53.960: I/jnifota.cpp(3122): JNI_OnLoad
09-18 18:17:53.960: I/jnifota.cpp(3122): FOTA_WriteFlag
09-18 18:17:53.960: I/dp.c(3122): call dp_set_flag
09-18 18:17:53.960: I/dp.c(3122): mkdir(/cache/fota/): ret=-1 errno=13
09-18 18:17:53.960: I/dp.c(3122): Open fail /cache/fota/fota.status
09-18 18:17:53.960: I/jnifota.cpp(3122): FOTA_DeltaWrite :
09-18 18:17:53.960: I/dp.c(3122): dp_write_fw_delta path : /sdcard/ota.bin
09-18 18:17:54.030: I/dp.c(3122): Open /sdcard/ota.bin
09-18 18:17:54.040: I/dp.c(3122): DP Version : DP_7_0
09-18 18:17:54.040: I/dp.c(3122): APFWDeltaSize(kernel): 4553496
09-18 18:17:54.040: I/dp.c(3122): APFSDeltaSize(platform): 252019202
09-18 18:17:54.040: I/dp.c(3122): APSBLDeltaSize(sbl): 0
09-18 18:17:54.040: I/dp.c(3122): APUADeltaSize(ua): 324664
09-18 18:17:54.040: I/dp.c(3122): BPFWDeltaSize(modem): 367644
09-18 18:17:54.040: I/dp.c(3122): BPSBLDeltaSize(hidden): 53529324
09-18 18:17:54.040: I/dp.c(3122): BPUADeltaSize(recovery): 5044224
09-18 18:17:54.040: I/dp.c(3122): CPFWDeltaSize(modem_3g): 0
09-18 18:17:54.040: I/dp.c(3122): CPSBLDeltaSize(modem_lte): 0
09-18 18:17:54.040: I/dp.c(3122): CPUADeltaSize(not used): 0
09-18 18:17:54.040: I/dp.c(3122): APFSTrgValDeltaSize(flex): 0
09-18 18:17:54.040: I/dp.c(3122): mkdir(/cache/fota/): ret=-1 errno=13
09-18 18:17:54.060: I/dp.c(3122): dp_split offset = 0x50, size = 0x457b18, path=/cache/fota/delta.zImage
09-18 18:17:54.250: I/dp.c(3122): dp_split path=/cache/fota/delta.zImage
09-18 18:17:54.260: I/dp.c(3122): Failed to open /cache/fota/delta.zImage: Permission denied
09-18 18:17:54.260: I/dp.c(3122): dp_split(kernel) failed with return value: -1
EDIT5: chmod 0777 /cache did the trick
Code:
[email protected]:/cache/fota $ ls -al
ls -al
-rw-r--r-- app_110 app_110 53529324 2012-09-18 18:22 delta.hidden
-rw-r--r-- app_110 app_110 367644 2012-09-18 18:22 delta.modem
-rw-r--r-- app_110 app_110 252019202 2012-09-18 18:21 delta.platform
-rw-r--r-- app_110 app_110 5044224 2012-09-18 18:22 delta.recovery
-rw-r--r-- app_110 app_110 324664 2012-09-18 18:22 delta.ua
-rw-r--r-- app_110 app_110 4553496 2012-09-18 18:21 delta.zImage
-rw-r--r-- app_110 app_110 36 2012-09-18 18:21 fota.status
Update in progress
First post from official ICS GTab 8.9
Sent from my GT-P7300 using xda app-developers app
:thumbup:
Wysyłane z mojego GT-P7300 za pomocą Tapatalk 2
tracid said:
First post from official ICS GTab 8.9
Click to expand...
Click to collapse
OMG I'm moved to tears. :good:
Anything working fine? I think we'd need some further tests for battery, 3G (is it working all over the world? we'll see), etc.. which languages are included?
Can anyone dump the system for me so that i can make a CWM Flashable zip
I'm already working on it, please be patient.
tracid, Can you please create an application to handle these .bin files.
from .bin to the parts inside. then we can use ODIN to write them or create update.zip.
Here is a sample one For the Galaxy Note: "http://www.hotfile.com/dl/171858907/a3bc9d2/GT-N7000_ILO_354458940.bin.html"
Nadavi, the application is semi-automatic. You need to chmod 0777 /cache before running it. Even if the app itself gets root permission granted, the library seems to run under the apps normal permission. Will try to fix and upload it these days.
HI,
i don't have the ota update on my phone.
i have the .bin file.
How to start?
Can you post the needed files?
instructions?
Nadav.
First post updated with instructions + application.
tracid said:
First post updated with instructions + application.
Click to expand...
Click to collapse
thanks it is time to flash ...
The ICS dump for P7300 has been posted here: http://forum.xda-developers.com/showthread.php?t=1893456
tracid said:
First post updated with instructions + application.
Click to expand...
Click to collapse
How to bypass the maximum folder size of the Cache Folder? I am stuck at that step, trying to extract an Galaxy S2 DBT update.
darth_mickrig said:
How to bypass the maximum folder size of the Cache Folder? I am stuck at that step, trying to extract an Galaxy S2 DBT update.
Click to expand...
Click to collapse
Send me your libdprw.so file. It's included syncmldm.apk/lib/
It is possible that your files are extracted somewhere else (maybe /sdcard)
tracid said:
Send me your libdprw.so file. It's included syncmldm.apk/lib/
It is possible that your files are extracted somewhere else (maybe /sdcard)
Click to expand...
Click to collapse
Here is the lib. Hope you can solve this problem.
Updated.
Disclaimer, I am not resposible for anything you do, and what works for me may not work for you. To start I am running Cyanogenmod 10 on a Galaxy s III sprint, rooted, busybox, and whatever else you may need.
First :Anything being done on the PC is being done on Kali Linux:
Create a custom kali.img as per http://docs.kali.org/armel-armhf/kali-linux-arm-chroot without a desktop as its not needed. I tried to make a list of packages you can use to have them get installed during the process, and have posted it here, alternatively one can run apt-get install and then copy and past the list into the command line over ADB or use the "testautokimg.sh" if you have trouble making one on your own, I'd rather have you make one than to upload one and everybody worry about rootkits and other evils. This script is setup to be used for this purpose but the img may also be used as a normal img to chroot into.
Second
Push the kali.img file to your phone, push it to "/storage/sdcard0/kali, make a folder called "/storage/sdcard0/kali" if one does not exist on your internal sdcard this is the root of your internal storage, not the root of your phone, if you don't have space on your internal sdcard you can put it an external one but a few lines of code will need to be changed in the script that is currently named "test.sh" as everything is still experimental.
I am still working on the script and will update it as often as I can.
Third
Download and move test.sh to "/system/bin/" and then make it executable
If you have trouble with this try on your phone or over ADB:
Code:
su
mount -wo remount systemfs /system
cp -i [location you pushed test.sh to] /system/bin
chmod 0755 /system/bin/test.sh
Then execute test.sh with:
Code:
test.sh
When it askes you if you would like to overwrite choose no for now. You should get a new prompt, go ahead and use the 'set' command to check your PATH variable and also 'which nmap' to make sure everything is available. You should now be able to explore the experimental Kali-Android hybrid system. Hope u Enjoy.
Please don't hesitate to improve on this with sanity checks and error handling, posting the improvments would be great. Ultimately I am going to get this all set up in the boot.img effectively making the mod persistant across reboots. As it is, a reboot will clean the changes, which is a good thing for now, some config, .rc, and other types of files clash in the etc folder but for now I havn't noticed too much harm form mounting the etc directory to androids root (again, this is my experience) but for safty's sake each device will eventually need to have those clashing files patched up to allow both systems the configurations they need to be in synch. Also the "linker" I think may not be right, to get it seamless I think the systems need to be built from scratch together. But hey, I thik this is a great place to start.
[Edit Aug 3, 2013] I finally got around to looking through the etc dir, less work then I thought with a fresh kali.img anyways. I just added a couple lines before mounting to Androids root we gotta make sure some files will still be available afterwards, this should only need to be done once as they wont get deleted off the kali.img file, but since it's interactive you can not overwrite or if Android updated you can overwrite if you choose to. Just make sure you note which files conflict and at least 'cat' their contents and see which one you want if your not going to make a new one that handles any options that are on one but not the other.
[Edit Aug 4, 2013](1) I uploaded a script to automate the kali.img creation. (2) I changed HOME="/sdcard" in test.sh
READ ME STILL DEBUGGING!
[About 'testautokimg.sh'] (1) Download (2) rename to "testautokimg.sh" (3) make executable (chmod +x ./testautokimg.sh) (4) Before exicuting make sure to rename or delete any existing ~/arm-stuff directory, run while logged in as root, and make sure debootstrap and qemu-user-static are installed.
NOTE: Because a large number of programms being installed this will take several hours, make sure you have the time to babysit things as it runs!
This will install a lot of programs and create the kali.img file in ~/arm-stuff/image directory, once complete push it to your device. I think the standard location for the img file is /storage/sdcard0/kali/kali.img if you put it on an external sdcard for whatever reason be sure to modify the mounting script "test.sh"
Updated
The List:
"""
wol-e xprobe dmitry netdiscover miranda casefile creepy jigsaw metagoofil theharvester twofi urlcrazy netmask nbtscan smtp-user-enum braa cisco-auditing-tool onesixtyone sslcaudit ssldump sslh sslscan sslsniff sslstrip sslyze stunnel4 tlssled cdpsnarf p0f tcpflow enumiax ike-scan cisco-auditing-tool bbqsql dbpwaudit hexorbase oscanner sidguesser sqlmap sqlninja sqlsus tnscmd10g bed fuzz powerfuzzer sfuzz siparmyknife lynis nikto unix-privesc-check openvas blindelephant plecost wpscan bbqsql sqlninja sqlsus ua-tester burpsuite powerfuzzer webscarab webslayer websploit wfuzz xsser paros proxystrike apache-users dirb dirbuster cadaver davtest deblaze fimap grabber joomscan padbuster proxystrike skipfish sqlmap w3af wapiti webshag websploit wpscan xsser pyrit chntpw crunch hash-identifier john johnny ophcrack-cli rsmangler samdump2 sipcrack sucrack truecrack cewl dbpwaudit findmyhash hydra medusa ncrack onesixtyone wireshark patator phrasendrescher thc-pptp-bruter zaproxy bluelog blueranger btscanner spooftooph mfcuk mfoc asleap cowpatty eapmd5pass fern-wifi-cracker giskismet kismet mdk3 wifi-honey wifitap wifite cisco-global-exploiter cisco-ocs cisco-torch yersinia ikat jboss-autopwn termineter darkstat dnschef hexinject sslsniff tcpflow fake fiked macchanger rebind sniffjoke tcpreplay iaxflood inviteflood ohrwurm protos-sip rtpbreak rtpflood sipp sipsak voiphopper driftnet ferret mitmproxy dbd intersect powersploit sbd u3-pwn cryptcat iodine miredo proxychains proxytunnel ptunnel pwnat sbd socat sslh stunnel4 webacoo weevely jad clang clang++ flasm javasnoop radare2 dhcpig inundator siege iaxflood thc-ssl-dos mdk3 reaver dex2jar smali extundelete autopsy binwalk foremost galleta sleuthkit missidentify pdgmail readpst reglookup vinetto magicrescue pasco pev recoverjpeg rifiuti2 safecopy scalpel scrounge-ntfs md5deep dc3dd dcfldd ddrescue dff chntpw pdf-parser peepdf volafox volatility casefile magictree metagoofil truecrypt cutycapt dnsenum dnsrecon dnstracer dnswalk fierce urlcrazy fragroute fragrouter arping cdpsnarf dmitry fping hping3 miranda netdiscover aircrack-ng android-sdk
"""
Bug
I created a plain jane kali.img as per the documentation at Kali's website, then I ran the 'test.sh' script and then ran the apt-get install command with the list and this is the result, I got an error at the end about PostgreSQL not working, any advice?
Code:
localhost / # apt-get install wol-e xprobe dmitry netdiscover miranda casefile creepy jigsaw maltego metagoofil theharvester twofi urlcrazy netmask nbtscan smtp-user-enum braa cisco-auditing-tool onesixtyone sslcaudit ssldump sslh sslscan sslsniff sslstrip sslyze stunnel4 tlssled cdpsnarf p0f tcpflow enumiax ike-scan cisco-auditing-tool bbqsql dbpwaudit hexorbase oscanner sidguesser sqlmap sqlninja sqlsus tnscmd10g bed fuzz powerfuzzer sfuzz siparmyknife lynis nikto unix-privesc-check openvas blindelephant plecost wpscan bbqsql sqlninja sqlsus ua-tester burpsuite powerfuzzer webscarab webslayer websploit wfuzz xsser paros proxystrike apache-users dirb dirbuster cadaver davtest deblaze fimap grabber joomscan padbuster proxystrike skipfish sqlmap w3af wapiti webshag websploit wpscan xsser pyrit chntpw crunch hash-identifier john johnny ophcrack-cli rsmangler samdump2 sipcrack sucrack truecrack cewl dbpwaudit findmyhash hydra medusa ncrack onesixtyone wireshark patator phrasendrescher thc-pptp-bruter zaproxy bluelog blueranger btscanner spooftooph mfcuk mfoc asleap cowpatty eapmd5pass fern-wifi-cracker giskismet kismet mdk3 wifi-honey wifitap wifite cisco-global-exploiter cisco-ocs cisco-torch yersinia ikat jboss-autopwn termineter darkstat dnschef hexinject sslsniff tcpflow fake fiked macchanger rebind sniffjoke tcpreplay iaxflood inviteflood ohrwurm protos-sip rtpbreak rtpflood sipp sipsak voiphopper driftnet ferret mitmproxy dbd intersect powersploit sbd u3-pwn cryptcat iodine miredo proxychains proxytunnel ptunnel pwnat sbd socat sslh stunnel4 webacoo weevely jad clang clang++ flasm javasnoop radare2 dhcpig inundator siege iaxflood thc-ssl-dos mdk3 reaver dex2jar smali extundelete autopsy binwalk foremost galleta sleuthkit missidentify pdgmail readpst reglookup vinetto magicrescue pasco pev recoverjpeg rifiuti2 safecopy scalpel scrounge-ntfs md5deep dc3dd dcfldd ddrescue dff chntpw pdf-parser peepdf volafox volatility casefile magictree metagoofil truecrypt cutycapt dnsenum dnsrecon dnstracer dnswalk fierce urlcrazy fragroute fragrouter arping cdpsnarf dmitry fping hping3 miranda netdiscover
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libclang-common-dev' for regex 'clang+'
Note, selecting 'libclang1' for regex 'clang+'
Note, selecting 'libclang-dev' for regex 'clang+'
Note, selecting 'clang' for regex 'clang+'
Note, selecting 'libsclang1' for regex 'clang+'
reaver is already the newest version.
The following extra packages will be installed:
apache2 apache2-mpm-worker apache2-utils apache2.2-bin apache2.2-common arj
aspell aspell-en bind9-host binfmt-support bkhive blt bluez brasero
brasero-common bwidget ca-certificates-java cdrdao comerr-dev cryptsetup-bin
default-jdk default-jre default-jre-headless desktop-file-utils
dictionaries-common dmsetup dnsutils dosfstools dsniff ed eject enchant
firebird2.5-common firebird2.5-common-doc fonts-droid fonts-freefont-ttf
fonts-liberation fonts-lyx freepats freetds-common fuse gccxml gcr
geoip-database gir1.2-atk-1.0 gir1.2-clutter-1.0 gir1.2-clutter-gst-1.0
gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-evince-3.0 gir1.2-freedesktop
...[...]...[...]...
xfonts-cyrillic
Recommended packages:
firmware-mod-kit vbetool wish
The following NEW packages will be installed:
apache-users apache2 apache2-mpm-worker apache2-utils apache2.2-bin
apache2.2-common arj arping asleap aspell aspell-en autopsy bbqsql bed
bind9-host binfmt-support binwalk bkhive blindelephant blt bluelog
blueranger bluez braa brasero brasero-common btscanner burpsuite bwidget
ca-certificates-java cadaver casefile cdpsnarf cdrdao cewl chntpw
...[...]...[...]...
The following packages will be upgraded:
libgcrypt11
1 upgraded, 1049 newly installed, 0 to remove and 2 not upgraded.
2 not fully installed or removed.
Need to get 983 MB of archives.
After this operation, 2200 MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://http.kali.org/kali/ kali/main libevent-2.0-5 armhf 2.0.19-stable-3 [152 kB]
Get:2 http://security.kali.org/kali-security/ kali/updates/main libgcrypt11 armhf 1.5.0-5+deb7u1 [289 kB]
Get:3 http://security.kali.org/kali-security/ kali/updates/main libgssrpc4 armhf 1.10.1+dfsg-5+deb7u1 [76.5 kB]
Get:4 http://http.kali.org/kali/ kali/main libgnutls-openssl27 armhf 2.12.20-7 [216 kB]
Get:5 http://http.kali.org/kali/ kali/main libgpm2 armhf 1.20.4-6 [34.0 kB]
Get:6 http://security.kali.org/kali-security/ kali/updates/main libkadm5clnt-mit8 armhf 1.10.1+dfsg-5+deb7u1 [60.4 kB]
Get:7 http://security.kali.org/kali-security/ kali/updates/main libkdb5-6 armhf 1.10.1+dfsg-5+deb7u1 [58.8 kB]
Get:8 http://http.kali.org/kali/ kali/main libpci3 armhf 1:3.1.9-6 [51.6 kB]
Get:9 http://http.kali.org/kali/ kali/main geoip-database all 20130213-1 [1466 kB]
Get:10 http://security.kali.org/kali-security/ kali/updates/main libkadm5srv-mit8 armhf 1.10.1+dfsg-5+deb7u1 [73.0 kB]
Get:11 http://http.kali.org/kali/ kali/main libcap2-bin armhf 1:2.22-1.2 [20.7 kB]
Get:12 http://security.kali.org/kali-security/ kali/updates/main libgbm1 armhf 8.0.5-4+deb7u2 [750 kB]
Get:13 http://http.kali.org/kali/ kali/main kismet armhf 2013.03.R1b-1kali1 [1735 kB]
Get:14 http://security.kali.org/kali-security/ kali/updates/main libegl1-mesa armhf 8.0.5-4+deb7u2 [69.4 kB]
...[...]...[...]...
Get:1033 http://http.kali.org/kali/ kali/main volatility all 2.2-1kali0 [1710 kB]
Get:1034 http://http.kali.org/kali/ kali/main w3af-console all 1.1svn5547-1kali3 [9954 kB]
Get:1035 http://http.kali.org/kali/ kali/main w3af all 1.1svn5547-1kali3 [392 kBPackage configuration
��������������������������Ĵ sslh configuration ���������������������������Ŀ
� sslh can be run either as a service from inetd, or as a standalone �
� server. Each choice has its own benefits. With only a few connection per �
� day, it is probably better to run sslh from inetd in order to save �
� resources. �
� �
� On the other hand, with many connections, sslh should run as a �
� standalone server to avoid spawning a new process for each incoming �
� connection. �
� �
� Run sslh: �
� �
� from inetd �
� standalone �
� �
� �
� <Ok> �
� �
����������������������������������������������������������������������������
(Reading database ... 55161 files and directories currently installed.)
Preparing to replace libgcrypt11:armhf 1.5.0-5 (using .../libgcrypt11_1.5.0-5+deb7u1_armhf.deb) ...
Unpacking replacement libgcrypt11:armhf ...
Selecting previously unselected package libevent-2.0-5:armhf.
Unpacking libevent-2.0-5:armhf (from .../libevent-2.0-5_2.0.19-stable-3_armhf.deb) ...
...[...]...[...]...
Selecting previously unselected package libice6:armhf.
Unpacking libice6:armhf (from .../libice6_2%3a1.0.8-2_armhf.deb) ...
Selecting previously unselected package libsm6:armhf.
Unpacking libsm6:armhf (from .../libsm6_2%3a1.2.1-2_armhf.deb) ...
Selecting previously unselected package libxt6:armhf.
Unpacking libxt6:armhf (from .../libxt6_1%3a1.1.3-1+deb7u1_armhf.deb) ...
...[...]...[...]...
Unpacking xfonts-encodings (from .../xfonts-encodings_1%3a1.0.4-1_all.deb) ...
Selecting previously unselected package xfonts-utils.
Unpacking xfonts-utils (from .../xfonts-utils_1%3a7.7~1_armhf.deb) ...
Selecting previously unselected package lmodern.
Unpacking lmodern (from .../lmodern_2.004.2-1_all.deb) ...
Selecting previously unselected package libkpathsea6.
Unpacking libkpathsea6 (from .../libkpathsea6_2012.20120628-4_armhf.deb) ...
Selecting previously unselected package luatex.
Unpacking luatex (from .../luatex_0.70.1.20120524-3_armhf.deb) ...
Selecting previously unselected package libjudydebian1.
Unpacking libjudydebian1 (from .../libjudydebian1_1.0.5-1_armhf.deb) ...
Selecting previously unselected package miredo.
Unpacking miredo (from .../miredo_1.2.3-1.1_armhf.deb) ...
Selecting previously unselected package fuse.
Unpacking fuse (from .../fuse_2.9.0-2+deb7u1_armhf.deb) ...
Processing triggers for man-db ...
Processing triggers for libglib2.0-0:armhf ...
Processing triggers for fontconfig ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for initramfs-tools ...
Setting up libfuse2:armhf (2.9.0-2+deb7u1) ...
Setting up fuse (2.9.0-2+deb7u1) ...
Creating fuse group...
Adding group `fuse' (GID 111) ...
Done.
MAKEDEV not installed, skipping device node creation.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
Selecting previously unselected package ntfs-3g.
(Reading database ... 61999 files and directories currently installed.)
Unpacking ntfs-3g (from .../ntfs-3g_1%3a2012.1.15AR.5-2.1_armhf.deb) ...
Selecting previously unselected package openjdk-7-jre-lib.
Unpacking openjdk-7-jre-lib (from .../openjdk-7-jre-lib_7u25-2.3.10-1~deb7u1_all.deb) ...
Selecting previously unselected package openjdk-6-jre-lib.
Unpacking openjdk-6-jre-lib (from .../openjdk-6-jre-lib_6b27-1.12.6-1~deb7u1_all.deb) ...
Selecting previously unselected package tzdata-java.
Unpacking tzdata-java (from .../tzdata-java_2013c-0wheezy1_all.deb) ...
Selecting previously unselected package java-common.
Unpacking java-common (from .../java-common_0.47_all.deb) ...
Selecting previously unselected package libnss3-1d:armhf.
Unpacking libnss3-1d:armhf (from .../libnss3-1d_2%3a3.14.3-1_armhf.deb) ...
Selecting previously unselected package openjdk-6-jre-headless:armhf.
Unpacking openjdk-6-jre-headless:armhf (from .../openjdk-6-jre-headless_6b27-1.12.6-1~deb7u1_armhf.deb) ...
Selecting previously unselected package default-jre-headless.
Unpacking default-jre-headless (from .../default-jre-headless_1%3a1.6-47_armhf.deb) ...
Selecting previously unselected package ca-certificates-java.
Unpacking ca-certificates-java (from .../ca-certificates-java_20121112+nmu2_all.deb) ...
Selecting previously unselected package openjdk-7-jre-headless:armhf.
Unpacking openjdk-7-jre-headless:armhf (from .../openjdk-7-jre-headless_7u25-2.3.10-1~deb7u1_armhf.deb) ...
Selecting previously unselected package stunnel4.
Unpacking stunnel4 (from .../stunnel4_3%3a4.53-1.1_armhf.deb) ...
...[...]...[...]...
Unpacking samba-dsdb-modules (from .../samba-dsdb-modules_2%3a4.0.6+dfsg-1kali1_armhf.deb) ...
Selecting previously unselected package samdump2.
Unpacking samdump2 (from .../samdump2_1.1.1-1.1_armhf.deb) ...
Selecting previously unselected package scalpel.
Unpacking scalpel (from .../scalpel_1.60-1_armhf.deb) ...
Selecting previously unselected package screen.
Unpacking screen (from .../screen_4.1.0~20120320gitdb59704-7_armhf.deb) ...
Processing triggers for initramfs-tools ...
Processing triggers for man-db ...
Processing triggers for ca-certificates ...
Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Processing triggers for fontconfig ...
Processing triggers for mime-support ...
Processing triggers for libglib2.0-0:armhf ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for shared-mime-info ...
Processing triggers for install-info ...
Processing triggers for postgresql-common ...
supported_versions: WARNING: Unknown Debian release: Kali Linux 1.0
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
en_us
insserv: warning: current start runlevel(s) (empty) of script `postgresql' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `postgresql' overrides LSB defaults (0 1 6).
insserv: warning: script '90userinit' missing LSB tags and overrides
insserv: warning: script '00banner' missing LSB tags and overrides
[....] Starting PostgreSQL 9.1 database server: main[....] The PostgreSQL server failed to start. Please check the log output: 2013-08-03 08:36:45 UTC LOG: could not create IPv6 socket: Permission denied 2013-08-03 08:36:45 UTC LOG: could not create IPv4 socket: Permission denied 2013-08-03 08:36:45 UTC WARNING: could not create listen socket for "localhost" 2013-08-03 08:36:45 UTC FATAL: could no[FAILate any TCP/IP sockets ... failed!
failed!
invoke-rc.d: initscript postgresql, action "start" failed.
dpkg: error processing postgresql-common (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for gconf2 ...
Errors were encountered while processing:
postgresql-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
localhost / #
Edit: It seems installing postgresql during the making of the img file works.
need to create a new group
Postgresql is looking for the aid_inet group which does not exist on the Kali Linux OS...this is why you are most likely getting a permission denied error.
You need to create the group aid_inet and do the following:
Step 1. Add aid_inet group
command -> groupadd -g 3003 aid_inet
Step 2. Install Postgresql 9.1
command -> apt-get install postgresql libpq-dev
Step 3. add user postgresq to group aid_inet
command -> sudo usermod -a -G aid_inet postgres
Then try -> "service postgresql restart" and all should work just fine.
Hope it helps...
-droidshadow
I have compiled AOSP (android-7.1.1_r8) for my pixel and I am able to boot, however, mobile data is not working. I get the following message in the "logcat" every 5 seconds which I think may be related:
01-06 14:58:08.749 2503 2503 I libmdmdetect: No supported ESOC's found
01-06 14:58:08.753 2503 2503 I libmdmdetect: slpi subsystem located
01-06 14:58:08.753 2503 2503 I libmdmdetect: Found internal modem: modem
01-06 14:58:08.753 2503 2503 I libmdmdetect: modem subsystem found
01-06 14:58:08.758 2503 2503 I libmdmdetect: No supported ESOC's found
01-06 14:58:08.759 2503 2503 I libmdmdetect: slpi subsystem located
01-06 14:58:08.759 2503 2503 I libmdmdetect: Found internal modem: modem
01-06 14:58:08.759 2503 2503 I libmdmdetect: modem subsystem found
01-06 14:58:08.760 2503 2503 E QC-NETMGR-LIB: QC-NETMGR
I have the latest radio image. Any help would be greatly appreciated.
It seems netmgrd fails to start, from dmesg:
[ 3051.236076] c2 1 init: Starting service 'netmgrd'...
[ 3051.344711] c2 1 init: Service 'netmgrd' (pid 3714) exited with status 255
[ 3051.344840] c2 1 init: Service 'netmgrd' (pid 3714) killing any children in process group
every 5 seconds.
and no rmnet interface? hmmm
please help...
Okay, I used strace and found that persist.rmnet.data.enable was false and a config file /system/etc/data/netmgr_config.xml was missing. I used setprop to set persist.rmnet.data.enable to true. I also grabbed that config file from the stock rom and had aosp add it to my system image. It seems this keeps netmgr from crashing. Now I have an rmnet_data0 interface but I still can't get an IP. Progress? maybe but not sure...
Please help.
logcat -b radio yields:
01-10 07:43:14.385 1560 1708 D DC-1 : onConnect: carrier='Rogers LTE' APN='ltemobile.apn' proxy='' port=''
01-10 07:43:14.386 1560 1708 D RILJ : [3911]> SETUP_DATA_CALL 14 0 ltemobile.apn 0 IPV4V6 [SUB0]
01-10 07:43:14.388 607 755 E RILQ : (0/607): RIL[0][main] qcril_data_request_setup_data_call: unable to get dsi hndl
01-10 07:43:14.388 607 755 E RILQ : (0/607): RIL[0][main] qcril_data_request_setup_data_call: qcril_data_request_setup_data_call: EXIT with FAILURE
01-10 07:43:14.388 1560 1659 D RILJ : [3911]< SETUP_DATA_CALL DataCallResponse: {version=11 status=4100 retry=-1 cid=0 active=0 type= ifname= mtu=0 addresses=[] dnses=[] gateways=[] pcscf=[]} [SUB0]
01-10 07:43:14.389 1560 1659 E TelephonyMetrics: Unknown type:
any help would be appreciated.
Okay I figured it out.
There are two files that are present in the system image of the stock rom, /system/etc/data/dsi_config.xml and /system/etc/data/netmgr_config.xml these files must be present in your AOSP system image in order to have LTE.
Thanks for this, only helpful info I found on No Supported ESOCs. Allowed me to debug my problem and fix.
Hello there.
Long story short: I have a Mate 9 MHA-L09 running on latest Oreo update which was rooted (with bootloader unlocked of course) and worked fine. I've installed Xposed (without making a backup, nice job me …) and, unfortunately, I'm now stuck in bootloop.
I've tried following methods:
starting in fastboot mode to recover using HiSuite but my Mate 9 isn't supported.
Boot on TWRP and tried to wipe data cache and dalvik but it didn't work.
Tried to install Oreo and Nougat updates from TWRP (with 3 archives on SD card: update.zip, update_data_public.zip and update_all_hw.zip) however I'm also getting and error when trying to install the first zip file (error 7 - "update_huawei_pkg_from_ota_zip: update package from zip failed")
I also tried the HWOTA method but after starting in TWRP and connecting a USB cable, the script seems frozen.
Maybe I'm using an incorrect function of TWRP? Or there is an easier method?
Any help would be greatly appreciated.
Thanks guys!
Tried to install latest MHA-L09C33 firmware and got an error 9 on TWRP.
Here is the log: https://pastebin.com/Yc0bnbfk
I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?
Gynsu2000 said:
I'm trying to invoke @ante0 as he seems quite an expert
The current situation is the following:
Phone is bootlooping
I can start in fastboot (PHONE Unlocked, FRP Unlock)
I can start on TWRP. I did install the version @ante0 suggested me (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353) but it's stuck on start screen. Therefore I install another one (https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967) which is correctly starting.
The thing is that the model is MHL-C09 but I don't remember if the exact region is C33 (FR) or C432 (EU). Does it matter?
Anyway, I downloaded the latest firmware of both versions using Firmware Finder:
MHA-L29C432B369 (8.0.0.369) / MHA-L09C432B369 (8.0.0.369)
MHA-L09C33B317 (8.0.0.317) / MHA-L09BC33B317 (8.0.0.317)
So I boot in TWRP, try to install the Update.zip file of either one of the two versions and ... I still get an error 9.
Apparently it's the following instruction which fails:
Code:
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
See the output log for L09C432B369: https://pastebin.com/1iLNPNBR
Am I doing anything wrong? Is there a missing step?
Click to expand...
Click to collapse
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Thanks for the update and the command.
MHA-L09 8.0.0.316(C33)
ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay
Gynsu2000 said:
Thank again for your help.
Follow-up:
I copied the correct ROM version and HuRUpdater however it doesn't work with Blackballs' TWRP.
Code:
********************
* HuRUpdater *
* by zxz0O0 *
********************
Trying to find the gpio-keys event node.
Found and will be using /dev/input/event1!
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/hurupdate-binary
Archive: /external_sd/fw/MHA-L09C33B316/HuRUpdater_0.3.zip
inflating: utils/busybox
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Archive: /external_sd/fw/MHA-L09C33B316/update.zip
inflating: VERSION.mbn
unzip: invalid zip magic 0447C7F0
CANNOT LINK EXECUTABLE "/tmp/utils/busybox": cannot locate symbol "__sendto_chk" referenced by "/tmp/utils/busybox"...
Aborted
I've tried to switch back to Pretoriano80's twrp but I'm still stuck on startup screen.
Is there any other method? Even downgrading to Nougat would be okay
Click to expand...
Click to collapse
I guess you could try:
Extract update.app from update.zip
Download Huawei Update Extractor
Open Huawei Update Extractor and go to options and uncheck header check.
Open update.app in Huawei Update Extractor.
Right click on system and extract selected.
Do the same for vendor.
Flash both using fastboot, then try Pretoriano80s TWRP again.
(you could try to boot phone after flashing system and vendor)
Another solution could be to:
Unpack Pretoriano80s TWRP with Android Image Kitchen, copy ramdisk/sbin/busybox and paste to desktop or somewhere not in the ramdisk folder.
Unpack Blackballs twrp and put the previously copied busybox in ramdisk/sbin/ then repack image and flash.
Then try HuRUpdater again.
For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !
Gynsu2000 said:
For some reason flashing the system worked but not the vendor.
Code:
D:\download\android\mate9\MHA-L09C33B316>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' (460651 KB)...
OKAY [ 10.857s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 10.873s
However, the phone now boots correctly, flashing the system partition was enough (I assume it seems obvious for an experienced guy).
\o/
Thanks a lot @ante0 !
Click to expand...
Click to collapse
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
ante0 said:
You can't flash update.zip directly in TWRP, you need to use HuRUpdater. It can be found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If it works with Blackballs twrp I do not know.
Though, you would have to know your cust before flashing.
You can check in Fastboot using this command:
fastboot oem get-build-number
After you know, download the appropriate firmware
Click to expand...
Click to collapse
Have been able to upgrade latest Oreo firmware using @Blackball twrp.
Just follow the instructions on his page.
1.Now that you have your correct firmware downloaded and intact.
2.Rename to this (update.zip, update_all_hw.zip, update_data_public.zip )
3.Download this file from here https://drive.google.com/file/d/1YM-Bga-wAKOct971WrrKCsX2K3tFP6zF/view?usp=sharing
4.Create a folder and rename to HWOTA8 , copy the downloaded file and the 3 firmware files
5.Now copy the the whole folder to your external storage and boot phone to twrp recovery.
6.Install by locating this file hwota8_update in the HWOTA8 folder on your external storage.
7.When done it will reboot and firmware upgrade processing will take over.
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:
ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
First thing I checked: bootloader was still unlocked.
Second thing: TWRP -> Backup.
golastic said:
when you use this method,you will not loose and bit of information you original have before the installation,everything will be intact.:good::good:
Click to expand...
Click to collapse
Thanks for the heads up. Hopefully I will backup thing first on TWRP before toying around with the phone.
ante0 said:
Check if OEM unlocking is still enabled.
It seems to disable itself sometimes when flashing system.
Click to expand...
Click to collapse
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.
Gynsu2000 said:
Ok, so now the phone is correctly starting but I have 2 issues.
First one is more an annoyance than an issue: when I reach the "About" screen, the model pf the phone is marked as ... "Unknown". I've tried to flash in fastboot the correct OEMINFO (using the file from there : https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353 ). After that the bootloader was locked and .... I still have an Unknow phone.
Second issue is that I've tried to install superSU but it doesn't seem to work.
Install output is the following:
Code:
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
- System-less mode, boot image support required
- Creating paths
mkdir: can't create directory '/su/bin': File exists
mkdir: can't create directory '/su/xbin': File exists
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists
- Removing old files
- Placing files
rm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sdd35
- Extracting ramdisk
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/dev/block/sdd35] ...
magic: [ANDROID!]
kernel: [12078158] (12079104) @ 0x00080000
ramdisk: [0] (0) @ 0x07c00000
second: [0] (0) @ 0x00f00000
tags: @ 0x07a00000
page size: 2048
unused: [0x00000000] [0x10000125]
dtb(?): [0] (0)
name: []
command line: [loglevel=4 initcall_debug=n page_tracker=on slub_min_objects=16 unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user]
extra command line: []
id: [0xe3bfe4262954c0437ae810fc16281a76152117bb000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
- Decompressing ramdisk (none)
- Checking patch status
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Already patched, attempting to find stock backup
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Stock restore failed, attempting ramdisk restore
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
--- Ramdisk restore failed, aborting
umount: can't umount /su: Invalid argument
BusyBox v1.22.1 bionic (2018-01-13 12:03 +0100) multi-call binary.
Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
losetup -d LOOPDEV - disassociate
losetup -a - show status
losetup -f - show next free loop device
-o OFS Start OFS bytes into FILE
-r Read-only
-f Show/use next free loop device
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
- Unmounting /system and /vendor
- Done !
I:Updater process ended with RC=0
I:Install took 8 second(s).
I:[MTP] MtpServer::run fd: 18
E:[MTP] request read returned -1, errno: 22, exiting MtpServer::run loop
Updating partition details...
I:Data backup size is 1571MB, free: 51976MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
Full log: https://pastebin.com/QGKdMEPU
I've tried 2 other versions but the result is the same.
Click to expand...
Click to collapse
I would do a full update again, oeminfo won't change model in about. Either using HWOTA as someone posted above or use HuRUpdater
Also, use Magisk instead of supersu. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In the end I used HWOTA8 and it worked like a charm. Until I discovered that I wasn't able to access a mobile network: SIM card is detected (icon in status bar have it displayed), however I'm not prompted for the sim's pin. First thing I checked was the sim lock using the super code: it's not (SIMLOCK_DEACTIVE). Then I've tried a couple of sims from other carriers but none of them are working.
Unless you guys have an idea, I suppose I should bring it to warranty.