Spflashtool author & how to flash LG X150 (LG Bello 2)?
Spflashtool author & how to flash LG X150 (LG Bello 2)?
(12-01-2018, 06:00 PM)nijazxp Here is great idea, do you thin it will work? This won't require root or any special knowledge of terminal commands. Just flash system.img instead of cache.img or user.img??? Interesting? Both are ext4, and they have enough space. Even if some additional files may appear in that partition from user (data) or cache, i may delete them. I am gonna try!
(14-01-2018, 06:14 PM)nijazxp Nothing works. System bootloops. When i deodex or not. When i put lgx160 (app and priv-app folders) apps or not. Philz recovery maker just closes after choosing android version and everything...when much text gets displayed in less than a seconds.
...
(15-01-2018, 07:27 PM)X3non(14-01-2018, 06:14 PM)nijazxp Nothing works. System bootloops. When i deodex or not. When i put lgx160 (app and priv-app folders) apps or not. Philz recovery maker just closes after choosing android version and everything...when much text gets displayed in less than a seconds.
...
assayed kitchen seems to be the best in terms of easy repacking.
just so you know, system.img is extremely larger than cache partition in terms of size. SP flash tool wont allow you to flash system.img onto cache. it will throw out an error
(16-01-2018, 03:27 PM)nijazxp Although kingoroot says that they do not support rooting android 5, i read it somewhere yesterday...
OK, finally solved temporary root problem. Used kingo root for pc again, and it says rooting failed. But i noticed i got root on phone, although their superuser was not installed. So it just worked that way without any superuser app. Now i reset phone and lost root again. Then i rooted again and tried to detect where are su and similar root files stored after rooting on phone. Believe it or not, the were stored in /sbin. I thought that was supposed to be in system/sbin maybe. I copied all these files to bin and xbin and copied sbin to system folder. Reset my phone, root is lost again. But I noticed that all modifications I done to system were saved! So I realized, every folder stored in / will be lost immediately. That is true for all android phones, even working and rooted ones. Only mounted partitions were supposed to be there.
Then I used kingo root for mobile and it rooted. And after reset my root persisted. Finally! I think i tried kingo root for mobile previously but had internet problems, so it did not work. Finally I have root, and it works even without superuser app. When there is not kingoroot superuser, then it just works without asking anything. So, this problem is solved. It was never related to locked bootloader. Looks like people who say that, are wrong. I think all these people have same issue as me, not related to locked bootloader.
Now will this in any way increase my chances to repair lg x150 system? Still there is no imei, but that is probably because this firmware uses dual sim, while lg x150 supports single sim. Reflashing partitions didn't repair imei.
But i don't know how to use mount. Words such as loop confuse me. I tried mount -r -w -t ext4 system.img sistem
nothing works... i installed busybox also... tried reading mount on linux debian manpages, and huh, page is long, will take me month to read and learn it...
also android mount is not same as that one, it lacks some commands, but i still am not giving up on mount because i think it is supposed to be working, and much faster than repacking unpacking on windows anything. Also xplore apk support changing permissions of files, in case problem is there. I don't know what should I do now except learning mount, maybe extract somehow all system files of lgx150 (broken), lgx160 (BIN_LGX160-X155-00-V10A-IND), and lgx170 (BRA_X170FTV). I haven't tried flashing this last one yet, but phone has same chipset and resolution and all as my. Only differences dual sim... Hope i will detect problem. Maybe files, or their permissions or user groups, or file system...
Also gonna try making small changes to such files, and detect what causes system to bootloop exactly. Since it's slow on windows due to repacking. Maybe gonna use osforensics and ext2fsd, to mount that on windows and modify file one by one... Use checksums, and dates to detect suspicious differences...
(17-01-2018, 09:54 AM)ColinB Have you had a look at your build.prop for the settings related to dual sim support ?