yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] ingcolchado:
SuS could not flash LAF and RAWRES

some parts of SuS could not be flashed: LAF & RAWRES

LAF:

(wanted)

843b507333fbe07113fa3150d9d3929f9f0149393f06f45bcdf35a57b3bf2060 (before)

ee7db724fe1df15f9941ecc474995484f7ab9f91acefb30af17504202abf42c6 (after)

rawres:

(wanted)

4ba5632931fb53e4332eb7d0b61689f428d74e8c9f2ad4523725ddcb7e3fc7b5 (before)

f81757904e8c4f7890c03e35b89a695c4bd48f4256858918c57f9bad33621f77 (after)

after all that

there were only a button to close that dialog and then nothing happened, so i'm at Download mode and now SALT won't recognize my device

i would deeply appreciate any help
[Android Software/Hacking General [Developers Only]] sdembiske:
Exactly how are you trying to flash the files ... ? Did SALT indicate that direct flashing for your particular device was available, if that is the way you were trying to flash it? Did you select the right files for your model?

From: the bootloader unlock thread:

If the UsU flashing fails for any reason (SALT will do important pre-checks and validiations before actually flashing):

"If you see a popup about UsU flashing has partially failed do not be scared - just read and follow the instructions!

If you see a different error: do not reboot or power off the device! Ask for support and provide the debug log in SALT (in Advanced Menu -> Debug Logfile button -> Upload button and share the link)!"

Suggest you get on the Support / IRC Channel noted in the bootloader unlock thread ...
[Android Software/Hacking General [Developers Only]] ingcolchado:
Well....i flashed from the internal memory, Direct flashing was available, but i opted for the Forner...

Looks like it did unlocked my mobile, cause im typing this with it,

After I saw that message from SALT that it couldn't flash those, I panicked and SALT wasn't responding, so I rebooted to fastboot and also rebooted FWUL and then SALT didn't recognized mi mobile, so I remembered that this is a spare phone and forgot about it for a couple of hours

I fixed (i did nothing actually) it by updating SALT and then it recognized my mobile

Im still in stock MM from my carrier, rooted, I have that pretty warning at boot, and TWRP is persistent, my ARB was 0, my device is a H815p, GPT compatibility is H815

i have noticed a couple problems,

i cannot use any ported pixel launcher, they all chrash

I inserted my sim card and only got 1 bar for signal although I was able to make a call and surf on 4g

I'll buy another sim card to fool around with it this weekend, and see if there is another glitch

I got the complete log from SALT but I can't post links

Don't know if there's a way to get another log, to clarify things up, I'm open to suggestions
[Android Software/Hacking General [Developers Only]] steadfasterX:
The log is the only way to help.

You could attach it in a post or send the link by pm.
[Android Software/Hacking General [Developers Only]] moreogthanu:
I'm confused on how to download SALT
[Android Software/Hacking General [Developers Only]] sdembiske:
If you're confused already, your best bet is to do what steadfasterX recommends in the Installation instructions in the OP on the first page in this thread - head over to the FWUL thread - SALT is included in FWUL - read the OP's in the FWUL and SALT threads thoroughly until your confusion dissipates ...
[Android Software/Hacking General [Developers Only]] moreogthanu:
Ok
[Android Software/Hacking General [Developers Only]] moreogthanu:
This may sound like a joke but will VirtualBox work on a Dell latitude e5400?
[Android Software/Hacking General [Developers Only]] fil3s:
You will get more use of ram using Rufus to burn the iso (as dd img) also drivers won't be an issue. Alternatively as sfx has instructed, u may burn forgetful iso to an dvd and boot from it
[Android Software/Hacking General [Developers Only]] ReeS86:
Hey just want to pust something here to see if others have experienced the same as me. When I use rufis to put the latest FWUL persistent 8GB image on a 32GB usb stick (Kingston one, USB3 not a cheap tradeshow giveaway one) it won't boot properly in persistent mode properly. What I mean by this is it boots to a blank desktop without any icons or shortcuts but the full OS is loaded, can open browser and use the start menu. It boots perfectly in forgetful mode.

I tried using Win32 Disk Imager and it works fine in all boot modes with the same image download and the same disk and PC.
[Android Software/Hacking General [Developers Only]] sdembiske:
Yes, I ran into the same issue on a Lexar 16gb USB stick, it just froze on the login screen - I believe it could be the way Rufus handles writing the the image file to some flash drives. No problem with FWUL forgetful iso file on the same flash drive but in the end, because I wanted to save my SALT backups directly to my PC's hard drive, I elected Virtual Box, running SALT both in Arch Linux 64 and FWUL persistent. I have 5 SALT backups now on my PC's hard drive, something I couldn't do with any of my current USB sticks.

Good find on the Win32 Disk Imager for those who want to use FWUL persistent on a USB drive. Perhaps steadfasterX could reference it in the OP ...
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
It may have issues with certain hardware and drivers, especially custom ones. I have a custom built Desktop PC and Virtualbox has issues with the GPU. Anyway, the more generic parts your PC has, better off you are with Virtualbox. I have no issues with VMWare Workstation though. Functions very well, detects all my hardware.

Anyway I burned FWUL to a USB flash drive (If you don't have one, you can use ImgBurn and burn it to a DVD-RW or BluRay disk), disable the GPU in the BIOS and just use Intel Integrated Graphics, as well as plug a general USB mouse and keyboard when I run Linux. I don't want to risk having FWUL not supporting my GPU and custom peripherals.

Good Luck!!!! :):good:

---------- Post added at 05:03 PM ---------- Previous post was at 04:42 PM ----------

I am trying to install SALT in an Amazon EC2 instance, then use a USB over IP program to connect it to peripherals. I'll let you guys know how it goes.
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
No problem, I will explain step-by-step.

First, you cannot run SALT in Windows OS, you need to have UNIX/Linux. So what you can do, is either setup a Linux instance from scratch, and install the following programs, or download FWUL (FWUL has SALT already installed) and burn it to a DVD.

Method 1: Linux instance from scratch

Before you are able to install SALT, you must install the following programs:

yad

git

gksudo

python3

python3-pyusb

python3-crypto

But the way to install these programs is different from one type of linux to another. So depending on your type of linux, you must enter the following commands to install these programs. These commands are to be entered into the terminal:

Arch Linux:

yaourt -Sy yad

sudo pacman -Sy git gksu xterm python-pyusb python-crypto

Manjaro Linux:

sudo pacman -Sy yad git gksu xterm python-pyusb python-crypto

Ubuntu/Debian:

sudo apt install yad git gksu xterm python3 python3-usb python3-crypto

Once you have installed these programs, you can now install SALT. To do so, enter the following commands into the terminal:

git clone https://github.com/steadfasterX/SALT.git

cd SALT

bash install-desktop.sh

sudo ~/SALT/salt

If it asks to install anything extra, say yes.

Method 2: FWUL (with all programs including SALT already installed for you):

Download this ISO file: https://xdaforums.com/devdb/project/dl/?id=28806

Then either using a hypervisor, create a virtual machine, or burn it to a CD/DVD/BluRay disk or USB flash drive and boot from it.
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
Unetbootin (https://unetbootin.github.io/) worked perfectly for me.
[Android Software/Hacking General [Developers Only]] moreogthanu:
I used win32 disk imager to write FWUL is that okay... If yes then what do i do next?
[Android Software/Hacking General [Developers Only]] sdembiske:
You can trust ReeS86 - just make sure you've done the Persistent version as an image file, not as an iso file.

Plug the USB flash drive into your PC/laptop and reboot into your PC/Laptop Boot Menu - select to boot from the flash drive and let her rip ...
[Android Software/Hacking General [Developers Only]] moreogthanu:
Is it ok if it's on an sd card
[Android Software/Hacking General [Developers Only]] sdembiske:
Please note

: ALL Members - these type of posts are concerning FWUL, not SALT - please remember to post to the appropriate thread (in this case FWUL), from this point on.

If your boot menu on your PC/Laptop allows that option (you can try, but ... ?). Otherwise, get or beg/borrow a flash drive or install with VirtualBox ...
[Android Software/Hacking General [Developers Only]] moreogthanu:
Thanks!
[Android Software/Hacking General [Developers Only]] moreogthanu:
This is what i get when i go to the boot menu
[Android Software/Hacking General [Developers Only]] birry:
For debian/ubuntu users, note that SALT 3.13-1 and above will need to install fastboot to run SALT
[Android Software/Hacking General [Developers Only]] sdembiske:
Looks like you will have to burn the FWUL persistent image to a writable DVD/CD ... or ... install with VirtualBox.
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
The reason why peripherals work in the bios is because it comes preinstalled with generic mouse and keyboard drivers as well as USB driver. For SD card to work, your BIOS must come preinstalled with SD card driver, my friend.
[Android Software/Hacking General [Developers Only]] fil3s:
I've discussed with steadfasterX that forgetful iso can only be burned to a DVD after failing numerous times to burn an extracted 8-30gb disk image to an 4gb DVD.

steadfasterX helped me with salt via IRC and teamviewer. He works magic in a Linux terminal. I'm now running FWUL 2.6 Persistent 30gb from bootable USB

Working flawlessly. I've even taken a full backup to my HDD.
[Android Software/Hacking General [Developers Only]] ingcolchado:
LAF & rawres

I had to edit the log because it weighed more than the half mb allowed, i deleted some time stamps or something like that but kept all the text that had information about the process, from the backup until i rebooted my device

So far everything look good, i got a SIM card and working great, except for battery life but it may be because I'm using the device very heavily to test it
[Android Software/Hacking General [Developers Only]] ingcolchado:
LAF & rawres

I had to edit the log because it weighed more than the half mb allowed, i deleted some time stamps or something like that, but kept all the text that had information about the process, from the backup until i rebooted my device

So far everything look good, i got a SIM card and working great, except for battery life but it may be because I'm using the device very heavily to test it and that is a used replacement battery
[Android Software/Hacking General [Developers Only]] steadfasterX:
Well the reason for the failures you had when flashing are clear:

You haven't updated SALT before you flashed UsU. There were millions of important fixes which you ignored by not updating SALT but you had luck as it worked nevertheless for you.
[Android Software/Hacking General [Developers Only]] ingcolchado:
I was on my job intranet so i couldn't update it :rolleyes:

Should i flash again with SALT so it can flash LAF & RAWRES or i can go on and flash some custom ROM? (I know i know, I'll flash N modern first and then my baseband package, before flashing a N or O ROM)
[Android Software/Hacking General [Developers Only]] Bankai83:
Hi steadfasterX,

I have posted my Frankenstein H815 20o issue here >

https://xdaforums.com/and...flash-t3773589

I have been interested in your SALT project, and I saw that a KDZ file flash is to come on your next SALT

release, when will be the release approximately and do you think it could work with my Frankenstein H815 20o device or no chances at all ?

(If no chances, I will order a new phone asap)

Thanks!
[Android Software/Hacking General [Developers Only]] Makifylmz:
Hi [MENTION=5545101]steadfasterX[/MENTION], I'm trying to extract kdz but arb detection fails. SALT want me to pick a partition but there is no partition appeared at all.

Here is the log -->> https://bpaste.net/show/41bcfd01f4d0
[Android Software/Hacking General [Developers Only]] sdembiske:
Here is the main culprit, it looks like:

[Errno 2]

No such file or directory

: '/home/android/New Folder/extractedkdz/*.dz'

Create a new folder with the stock MM .kdz name, with no periods: e.g., H81520i_00_dz_SALT_extract

where you plan to save the extraction to, making sure you have enough room (mine was approx. 73MB), and direct the extraction to that folder after you select the .kdz to extract.
[Android Software/Hacking General [Developers Only]] Makifylmz:
Yeah approximately 5.5gb free space that I've got. That makes sense. Gonna try it thanks ! :)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Like sdembiske already said the reason is a space in the target directory you made. That's a known issue atm.
[Android Software/Hacking General [Developers Only]] lynx3:
Hi, thanks for all of your hard work.

Could you please help me figure out why I can't get SALT to recognize my G4 H815 (TWN version) in download mode? Running it on FWUL 2.6 using VirtualBox. Happy to provide whatever logs are needed.
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 529 in the FWUL thread - it's a bit of a checklist I have to run through sometimes myself when I'm having trouble connecting. See if it helps.
[Android Software/Hacking General [Developers Only]] lynx3:
Your post did the trick! Thank you!
[Android Software/Hacking General [Developers Only]] steadfasterX:
New release

Checkout the FAQ #9 for howto update to this brand new release

v3.15

Released: 2018-04-25

Full changelog (SALT): at github (this version compared with the previous release)

Summary changelog:

New(SALT): added a Select/Deselect button when extracting a KDZ
[Android Software/Hacking General [Developers Only]] steadfasterX:
The file extension doesn't matter. It can be: bin, img, image, mbn,... it's just a name nothing else. So when you see boot.bin it's the same thing as boot.img and so on.
[Android Software/Hacking General [Developers Only]] steadfasterX:
1) you posted in a complete wrong thread. even my signature has the proper links..

2) your system has no internet access - which prevented to upgrade SALT - so you used a completely outdated SALT release (3.8 instead of the current 3.15) - with TONS of fixes

3) your disk went full as you have done a backup (I guess a full one) and you had not enough free disk space -> thats the worst thing you can do on any system. you should have stopped here at least.

4) UsU flashing went fine so far just disconnect the USB cable now and close SALT

5) when you want to recover files then ANY installation may destroy traces of these - a much better option is to use the full backup (with a location having 33 GB of free disk space!!!) and then recover the files from the file: userdata.image. e.g. you can use the linux tool photorec (other the name may suggests it can recover a LOT of files not just pics) on that image:

sudo pacman -S testdisk
photorec userdata.image

(https://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step)

EDIT: [MENTION=9083773]Dr. Bubbler[/MENTION]

Or you can just use the latest FWUL nightlies: http://leech.binbash.it:58888/x86_64/ (most current at the top)

It has not just SALT up to date but also included the above tool photorec as a graphical tool (click the Arch symbol most left in the panel and search for Qphotorec)

.
[Android Software/Hacking General [Developers Only]] AdventL:
I think the boot.img doesn't work because it is from a backup that i did after flash TWRP to boot /:

How do I extract the original boot.img from the kdz? I've tried the extract KDZ and pointed it to the original KDZ and i got a DZ file as a result. :confused:
[Android Software/Hacking General [Developers Only]] steadfasterX:
Ensure you have SALT v3.15

simply click the extract KDZ button and choose "boot"

there is one important thing: do not use any space or special character in the folder names (i.e. do not store the KDZ file in a folder which spaces in the name and do not choose a destination with a space in the folder name)

If you still have issues share the SALT debug log (advanced menu -> log -> upload -> share the link)

-
[Android Software/Hacking General [Developers Only]] AdventL:
Here's an image of what I see when I click "Extract". (I am using FWUL Forgetful if that matters)

[IMG="ss"]https://i.imgur.com/ihtHPwz.png[/IMG]

Here is the log

https://bpaste.net/show/db1c4d3bbef3
[Android Software/Hacking General [Developers Only]] steadfasterX:
well its like I said: spaces..

The file name you are trying to open is:

/run/media/android/D286-6661/SEA H81520e_00_0818.kdz

-------------------------------------------^^^

Rename: "SEA H81520e_00_0818.kdz" to "H81520e_00_0818.kdz" and try again
[Android Software/Hacking General [Developers Only]] pocepoke:
hello,

im trying to make backup using SALT from FWUL

the backup process if im using BASIC it finisihed

but id im using FULL it wouldnt finish and always stuck [MENTION=678353]SysteM[/MENTION] partition (always stuck but not [MENTION=232977]SamE[/MENTION] point some time @20% sometime more than 40%)

the stange is i have H811 version and the imai sticker says H811 too, but on the SALT it reconize as H810 ATT and the only thing that point to H811 is GPT compability

im a had got fake (franken) H811 from the seller?

is there any chance to backup all FULL the partition, couse i want to ROOT and change some ROM .....

big thanks for the help
[Android Software/Hacking General [Developers Only]] steadfasterX:
the destination where you store the backup must have 32 GB of free space otherwise it will not work!
[Android Software/Hacking General [Developers Only]] pocepoke:
i im pointing the stroage that willl be use to SSD 256gb free at least 120gb so disk space my not the problems

i realized that arrow circle on download mode had stoped to wthen the backup FULL failed wait for 30minuits still no added more or next file to go still stuck until i pull the usb out

but i will tried again with my sons pc, he has more than 1gig free hard disk :D

by the way tanks for the fast respond ..... i reealy apriciate that :good:

in no native with english so if there some thing wrong with my word plase dont mis undertsanding it :fingers-crossed:

update : on my son pc cannot run just stuck [MENTION=222524]first[/MENTION] reading of the backup file 30minuits still so

and im starting FWUL again couple times still stuck [MENTION=222524]first[/MENTION] readings file .... back to my pc again

im newbie in linux so i dont know where is log file i want to up load here

[IMG="SALT on FWUL"]http://i150.photobucket.com/albums/s103/pocepoke/Screenshot_2018-05-04_00-58-25.jpg[/IMG]
[Android Software/Hacking General [Developers Only]] marcgo:
This sounds like exactly what I've been seeking... but...

Will this work on a mac? If so, what should I look out for?

I've been looking for an alternative to dealing with the dll and issues on a windows box. I run Mac OSX yosemite and I have usually managed to work unix magic on a mac to get things done on 6 other android devices w/o resorting to booting my ancient win/linux laptop. This LG G4 experience has really bummed me out, because it seems that all devs in this forum use and develop on a windows machine and have no real expectation that there are any other platforms.

It's great to see your development specifically for using a Linux system. I'm all for that, but I wish I didn't have to go thru a bunch of other steps to get Linux or FWUL up and running, while mac shares a lot of subsystems and conventions.

I have an LG tablet as well, and i'm eager to use this tool on both... or, at this point, simply throw both devices in the trash. Thanks.
[Android Software/Hacking General [Developers Only]] steadfasterX:
The log file is super easy as its integrated in the menu: Read and follow FAQ #1000

EDIT:

[MENTION=4191027]pocepoke[/MENTION] : AND PLEASE PLEASE UPDATE SALT! Read the FAQ for how!

Well thx for your words. There are many dependencies SALT is based on (some are listed in the OP) which I'm not sure how they can be adapted to Mac's..

So mainly:

python2 and python3

GNU sed (GNU acts different and so consider that as a hard requirement)

GNU grep / egrep (GNU acts different and so consider that as a hard requirement)

GNU findutils (i.e. find) (GNU acts different and so consider that as a hard requirement)

Bash

and maybe other GNU stuff .

I'm not aware how the above fits for a Mac and well.. as long as you do not try to flash/unlock its uncritical to just try the basic stuff first (open the main menu, doing a basic backup, sharing the log! Read FAQ #1000 for how). I can take a look on the log if you like.

Good luck ;)

.
[Android Software/Hacking General [Developers Only]] pocepoke:
thx for the guide,

as i allready update but still not work, im using FWUL on usb flashdisk so even i all ready update SALT when reboot all gone back to default

thats way the screen shoot just using SALT from FWUL (old one)

ok i will tried couple times again and i will upload my SALT log

best regards, poce
[Android Software/Hacking General [Developers Only]] steadfasterX:
Are you sure that you have flashed a PERSISTENT version of FWUL to the disk then? If you flashed or booting the FORGETFUL it will forget your downloads and settings..

But having that up2date is the most important step first

EDIT:

you can also download a nightly release of FWUL which contains the latest SALT release already here: http://leech.binbash.it:58888/x86_64/ (most current builds are at the top)

just ensure you use a persistent one (named "8GB, 15 GB or 30GB") fitting to the size of your USB stick

.
[Android Software/Hacking General [Developers Only]] pocepoke:
using PERSISTENT doesnt work .... i had to use vga mode ( i thing thats is called there 3 on them)

right know im trying make new FWUL usb disk again using 32gb the last one just 2gb and the image is 15gb

mybe that who make error on SALT

it may takes time but im gladly take it ..... i had been playing android since i got "galaxy" spica :p
[Android Software/Hacking General [Developers Only]] steadfasterX:
yes the VGA fallbacks are

not

persistent.

Once you have booted FWUL again try this in a terminal (black little icon in the panel);

sudo lshw -c video

copy and paste the whole output here
[Android Software/Hacking General [Developers Only]] AdventL:
Thanks for your help, I've finally manage to get it to boot the original ROM :)

One more question, I've tried flashing another ROM (that I've downloaded from the link provided in the download section, lineage for h815) and tried flashing that but I keep getting assertion error /:
[Android Software/Hacking General [Developers Only]] steadfasterX:
thats a UsU question. pls go to the UsU thread and read the FAQ.

.