Hello, this sounds a little bit impossible but i made some progress with my friend. We made a vendor partition, edited the TWRP but we stuck at the part of making a vendor. Can the g4 community do it? I think you can, especially @steadfasterX. UsU, FWUL and SALT were masterpieces.
Also, it looks so hard. Because there is no phone with S808 and A9.
If you need to know how did i made the vendor partiton, i can help.
I use H815TR UsU'd. If that helps.
You should describe much more detailed what you did and what problems you have after that.
steadfasterX said:
You should describe much more detailed what you did and what problems you have after that.
Click to expand...
Click to collapse
First i put the parted file on the phone and run it via terminal in TWRP.
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted was the command i used.
Second, i unmounted every partition and wrote the command: parted /dev/block/mmcblk0
After, I wrote p to see what number was my userdata (it was 50) and i wrote rm 50.
After i deleted the userdata, i wrote
mkpart userdata ext4 6359MB 30GB
mkpart vendor ext4 30GB 31.3GB
to make a vendor partiton.
Finally, i did a format data and @MeizuM6T edited the TWRP.
I did everything with @MeizuM6T .
Now i need vendor files.
The easiest way is to simply copy /system/vendor from an existing ROM tbh.
steadfasterX said:
The easiest way is to simply copy /system/vendor from an existing ROM tbh.
Click to expand...
Click to collapse
Most roms contain system-as root, obviously this is where @Emo19 and me get stuck.
Would connecting the vendor via FSTAB be enough to boot?
MeizuM6T said:
Most roms contain system-as root, obviously this is where @Emo19 and me get stuck.
Would connecting the vendor via FSTAB be enough to boot?
Click to expand...
Click to collapse
Well then i don't get the problem.
We mimic a vendor partition since (iirc) pie and to follow android standards we already moved everything needed to /system/vendor including config updates where needed pointing to /vendor. I would say 98% of this move is done already for the rest see e.g: https://github.com/LGgFour/android_device_lge_g4-common/search?q=System/vendor
Ofc currently /vendor is just a symlink to /system/vendor but for the system it feels like it has a separate vendor partition already.
So my guess was you just copy everything from /system/vendor and put that in your /vendor partition and if we made everything right and you fix the rest of the few /system/vendor paths it should just boot. Ofc you would need to update fstab to point to the dedicated vendor partition then. Does that help?
steadfasterX said:
Well then i don't get the problem.
Click to expand...
Click to collapse
The vendor has successfully connected but the treble support is still not visible.
Vendor is connected to the system and is working now, how should we arrange for treble?
MeizuM6T said:
The vendor has successfully connected but the treble support is still not visible.
Vendor is connected to the system and is working now, how should we arrange for treble?
Click to expand...
Click to collapse
no idea really. I have never ported anything to treble. just the other way around
steadfasterX said:
no idea really. I have never ported anything to treble. just the other way around
Click to expand...
Click to collapse
Thanks, I think we need to write "ro.treble.enabled = true" via build.prop. then we will try to install some GSI Roms.
MeizuM6T said:
Thanks, I think we need to write "ro.treble.enabled = true" via build.prop. then we will try to install some GSI Roms.
Click to expand...
Click to collapse
well I dont think its THAT easy. I was serious about the other way around so take a look at what I did for another device:
https://code.binbash.rocks:8443/MVA-VoLTE/android_device_samsung_j5y17lte/commits/branch/eos-q/search?q=treble&all=true
https://code.binbash.rocks:8443/MVA-VoLTE/android_device_samsung_exynos7870-common/commit/ab2567dc82fbdb2a21aa3ea28572dd18e5b7fb79
https://code.binbash.rocks:8443/MVA-VoLTE/android_kernel_samsung_exynos7870/commit/b8e2cf570dfd383fb3a4497d6b53d51c9226ca7b
Ofc you would do the opposite then what the commits showing and ofc I dunno if thats enough and haven't checked what needs to be adapted etc but it should give you an idea
steadfasterX said:
well I dont think its THAT easy. I was serious about the other way around so take a look at what I did for another device:
Click to expand...
Click to collapse
I doubt it will open either, it shouldn't be that simple. I will look at what you have thrown
Related
I've just flashed the boot.img and system.img from Peter Alfonso:
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
Boot.img worked fine after the reboot. I've flashed the system.img now and its been on the pretty colours screen for a good few minutes.
Anyone got any ideas? Trying to unroot my device
Anyone :'(
Sent from my iPad 2 using Tapatalk
Can someone please upload their system.img so I can flash it.
Sent from my iPad 2 using Tapatalk
I believe your problem is that those images are for the VZW LTE version and the build.prop is telling the system to use the LTE ril and you have a GSM radio. There may be other discrepancies as well between versions. Check to development forum for a GSM system and
boot image that you can fastboot to restore your phone.
cellzealot said:
I believe your problem is that those images are for the VZW LTE version and the build.prop is telling the system to use the LTE ril and you have a GSM radio. There may be other discrepancies as well between versions. Check to development forum for a GSM system and
boot image that you can fastboot to restore your phone.
Click to expand...
Click to collapse
They are for a GSM version I believe aren't they. I cant find a system.img anywhere
I think I was wrong, I read about updating the VZW images when its released and got confused sorry.
Not sure why it might have hosed your phone. Have you tried reflashing it in fastboot?
cellzealot said:
I think I was wrong, I read about updating the VZW images when its released and got confused sorry.
Not sure why it might have hosed your phone. Have you tried reflashing it in fastboot?
Click to expand...
Click to collapse
yep. I did ./fastboot flash system system.img
Just gets in a loop on the loading screen
Could I flash the CWM image in fastboot and install the modaco rom? Would that work?
Theoretically, yes it should, but I was hesitant to suggest something like that because we weren't sure what caused the issue to begin with. If you are willing to give it a shot and have already resigned yourself to losing your warranty, then it seems worth a try.
At this point, the safest thing would be to wait until an OTA update is pushed out and it will either fix everything or give you a clearer chance at getting it replaced under warranty.
Not a very satisfying answer, sorry.
cellzealot said:
Theoretically, yes it should, but I was hesitant to suggest something like that because we weren't sure what caused the issue to begin with. If you are willing to give it a shot and have already resigned yourself to losing your warranty, then it seems worth a try.
At this point, the safest thing would be to wait until an OTA update is pushed out and it will either fix everything or give you a clearer chance at getting it replaced under warranty.
Not a very satisfying answer, sorry.
Click to expand...
Click to collapse
The issue occured when i flashed the system.img. The boot.img from his package worked fine.
I can only get the device into fastboot it seems, so I cant adb push the ROM to the device anyway :'(
http://forum.xda-developers.com/showthread.php?t=1352347
Did you try downloading the images from that thread? They may work better for you since they were pulled from a UK device.
Do you mean the DD image? I was a bit weary as it was 600mb .img file and a normal system.img is 250mb
Not entirely sure what that is and don't want to make it worse. Also, not sure what the zip file is either
Sent from my iPad 2 using Tapatalk
Evostance said:
Do you mean the DD image? I was a bit weary as it was 600mb .img file and a normal system.img is 250mb
Not entirely sure what that is and don't want to make it worse. Also, not sure what the zip file is either
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
It's probably a sparse image judging from the size of it. If it compresses down to a normal size when you zip it you will know if my guess was correct.
Not sure how you would flash those though, other than using dd to write them back.
blunden said:
It's probably a sparse image judging from the size of it. If it compresses down to a normal size when you zip it you will know if my guess was correct.
Not sure how you would flash those though, other than using dd to write them back.
Click to expand...
Click to collapse
He has put
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
So the system is in gnsys.zip and fasboot can flash system via a zip I take it.
I have no idea how to use dd either :/
Evostance said:
He has put
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
So the system is in gnsys.zip and fasboot can flash system via a zip I take it.
I have no idea how to use dd either :/
Click to expand...
Click to collapse
If it's an update.zip is has to be flashed using recovery, a custom recovery in this case since the signature will be changed or incorrect.
My dd comment was referring to what parts of the emmc you should set as the output. Using dd in general is not a problem, even though one should always be careful when using it.
Rather than try to cobble together a solution, I think it's probably best to wait until someone posts a proper system image or an official set of stock images is made available. While I believe it could very well work and should, I just think its safer to try to restore it with known good images, especially since you haven't done anything that extreme yet and the fix should be very simple.
That is the frustrating part because all you need is the right set of images to restore.
Edit: /system is about 643MBs when you use dd to make an image and mmcblk0p10 is the /system partition
I am generally all for DIY solutions but without a safety net of stock images this early, when an official solution is likely to be made available shortly, I recommend waiting.
OK cheers guys.
Won't the OTA just have part of a system rather than the lock?
I've got in contact with Pete so might try see of we can solve that. If not, hopefully patch will be out before Wednesday so I can flash and send back.
Failing that I'll have to hope someone accepts it anyway
Sent from my HTC Desire HD using Tapatalk
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you solved this problem? if yes how did you solve your problem?
mauronofrio said:
Have you solved this problem? if yes how did you solve your problem?
Click to expand...
Click to collapse
I haven't yet. I don't know if it's possible without modifying TWRP to read from /data/cache on startup since the cache partition doesn't exist on a/b devices
I doubt it will help or not...
But I noticed when sideloading an OTA, that whatever the .zip file would be called would "extract" to the folder "sideload" (in the /sdcard, but there's a good chance that it's its own folder in the root directory...) as sideload.zip (i believe...I can easily be wrong....but I remember it was a simple and obvious one-word name....). I remember having issues with TWRP processing the initial .zip file, so I would extract the initial OTA .zip file, then manually input what was extracted into that folder under that specific name and TWRP was able to automatically start processing the OTA....
I'm not sure, but maybe you might find this process beneficial and/or interesting/inspiring...
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
mauronofrio said:
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
Click to expand...
Click to collapse
I did that. It didn't work
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
UncertainSpin said:
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
Click to expand...
Click to collapse
I'm having the same problem too. I have been using Tasker to write to /cache/recovery/openrecoveryscript because that's all I could find online.
I intend to have this in the Run Shell command in Tasker.
chmod 0777 /cache/recovery
echo "backup SDCRBM weeklybackup" > /cache/recovery/openrecoveryscript
echo "reboot" >> /cache/recovery/openrecoveryscript
chmod 664 /cache/recovery/openrecoveryscript
I have verified that it is writing the file, and TWRP seems to be erasing it which from what I gather it is supposed to do. But it is not executing the command when TWRP starts.
LineageOS 16.0 unofficial/ TWRP 3.2.3 on Samsung Galaxy S7.
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
rfgamaral said:
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
Click to expand...
Click to collapse
Yup indeed needs to be fixed..
Already extracted mmcblk0 can be found on the following thread here
Can someone with a rooted stock rom please pull the following partition and upload it here
Requirements
Rooted moto g5
TWRP recovery
Blank micro sd card (at least 32gb)
make sure adb debugging in enabled in dev options
enter TWRP recovery
Follow instructions from here but amend the extract command with the values given below
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you have a 32gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=29820
and if you have a 16gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=14910
Please note this partition will be very large so compress it in a zip file as best you can and you will obviously need good internet connection and file storage to upload it
Please also enclude what varient the mmcblk0 was taken from with your upload
How to here
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
but what we need is someone who has a motorola g5 cedric xt1671 that has root and twrp and can provide us with that file to be able to revive our cell phones
I don't have the stock ROM will it be fine
abhimanyuk said:
I don't have the stock ROM will it be fine
Click to expand...
Click to collapse
Prefer stock but it should work if you have a custom rom too
TheFixItMan said:
Prefer stock but it should work if you have a custom rom too
Click to expand...
Click to collapse
But it will include my device all info like imei serial number etc.
Will it be safe.
abhimanyuk said:
But it will include my device all info like imei serial number etc.
Will it be safe.
Click to expand...
Click to collapse
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research
TheFixItMan said:
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research
Click to expand...
Click to collapse
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom
abhimanyuk said:
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom
Click to expand...
Click to collapse
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine
TheFixItMan said:
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine
Click to expand...
Click to collapse
I have Linux installed. I will do that tomorrow Hope we will get the desired result.
Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!
I'm still waiting for someone to provide the mmcblk0 partition
If you have a working rooted moto g5 see the first post
what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
https://www.youtube.com/watch?v=rJGsZuWkboo
You did it ?
gugsta said:
Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!
Click to expand...
Click to collapse
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me
dalissonetcaf said:
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me
Click to expand...
Click to collapse
We are awaiting someone to upload the mmcblk0 partition for this device
Until that happens there is currently no known solutionn (other than motherboard replacement or specialist flash boxes) to revive a moto g5 with no access to the bootloader
Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.
Happiness777 said:
Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.
Click to expand...
Click to collapse
It's because of the file system. Fat32 can only handle files up to 4GB. Best way to get around this, is to first format the sdcard in exFAT or ext4 on your computer (sdcard reader).
Here is a mmcblk0 image someone sent me
Unzip it
Use an sd card boot image tool to create a bootable sdcard with the image (one that can handle a dd image)
You may need to format the sd card to ext4
If it works it may take a long time before it does boot from sd card
mmcblk0.zip
See below for how to write image
https://www.embeddedarm.com/blog/how-to-write-an-sd-card-image-linux-windows-mac-osx/
my mmcblk0 weighs 27.9 Gb (30,000,000,000)
Is it the right size?
Happiness777 said:
Friend and created the mmcblk0 but I am in doubt if the size is accurate
Click to expand...
Click to collapse
Either that link doesn't work or it's not accessible to me
Make sure the sd card is formatted to ext4 when you create the image
The image I posted is 15gb (once unzipped) but since I don't have this device I can't check it
Phone stopped making any sounds.
what works: bluetooth, wifi, sim card (data + receiving texts, calls not tested)
what doesn't: sensors (rotating), camera, sound
dmesg https://pastebin.com/gY1pgn96
What was flashed that I can find/remember in no particular order
H810_UsU_unlock.zip
h810_21y_modem.zip
H810_UsU_baseband_flash-in-twrp.zip
G4_29a_N_modem_UsU.zip
LG-G4_VideoLag-Fix_EXTRACTME-AND-READ-THE-README.7z
h810_10o_UsU_bootloader_ARB2.zip
lineage-15.1-20190121-UNOFFICIAL-h810_usu.zip
lineage-15.1-20190409-UNOFFICIAL-h810_usu.zip
lineage-16.0-20190512-UNOFFICIAL-h810_usu.zip
and magisk + gapps
zip of sbl1 rpm tz pmic partitions attached.
On a side note I see h810_10o_UsU_bootloader_ARB2.zip that I forgot about earlier. Explains the ARB2 that the phone is at now. Looking back through my bash history I was having these issues before I flashed this.
@steadfasterX per request
You flashed so much stuff steadfaster can't even help you
baconbacon said:
Phone stopped making any sounds.
what works: bluetooth, wifi, sim card (data + receiving texts, calls not tested)
what doesn't: sensors (rotating), camera, sound
dmesg https://pastebin.com/gY1pgn96
What was flashed that I can find/remember in no particular order
H810_UsU_unlock.zip
h810_21y_modem.zip
H810_UsU_baseband_flash-in-twrp.zip
G4_29a_N_modem_UsU.zip
LG-G4_VideoLag-Fix_EXTRACTME-AND-READ-THE-README.7z
h810_10o_UsU_bootloader_ARB2.zip
lineage-15.1-20190121-UNOFFICIAL-h810_usu.zip
lineage-15.1-20190409-UNOFFICIAL-h810_usu.zip
lineage-16.0-20190512-UNOFFICIAL-h810_usu.zip
and magisk + gapps
zip of sbl1 rpm tz pmic partitions attached.
On a side note I see h810_10o_UsU_bootloader_ARB2.zip that I forgot about earlier. Explains the ARB2 that the phone is at now. Looking back through my bash history I was having these issues before I flashed this.
@steadfasterX per request
Click to expand...
Click to collapse
Perfect thx that explains a lot..
As you mentioned already the bootloader stack thing but also another one you flashed 21y modem .. I will need some time to investigate both things and come back to you asap
Update:
ok so the worst thing you had done was flashing the 21y modem. The problem with that one is that it is ARB 3 (see known ARB) and so blown fuses (in areas not related to the bootloader ARB but for firmware).
Anyways that will refuse using several parts of your firmware now.
There is no guarantee if the following would make things even more worse but that's what I would try:
extract the system and the modem partition of the 21y kdz
grab the "etc/firmware/venus.*" files from the extracted system partition and copy them to system/etc/firmware/ (mount "system" in TWRP before)
grab the "image/a2dsp.*" files from the extracted modem partition and copy them to /firmware/image (mount "Firmware" in TWRP before)
boot again and grab the dmesg as soon as possible
again that can make things even more worse so you do this on ur own risk.
Sent from my OnePlus 6T using XDA Labs
Before I do this, because hell why not , is the 21y here https://storagecow.eu/index.php?dir=Xda/LG+G4/H810/AT&T/ what I am looking for? Want to be sure before I make matters worse for myself.
baconbacon said:
Before I do this, because hell why not , is the 21y here https://storagecow.eu/index.php?dir=Xda/LG+G4/H810/AT&T/ what I am looking for? Want to be sure before I make matters worse for myself.
Click to expand...
Click to collapse
Yes the rar file. It will contain a TOT file (so you cannot use SALT to extract) .
TOTs require the windows software :
https://forum.xda-developers.com/showthread.php?t=2600575
Sent from my OnePlus 6T using XDA Labs
How do I grab the files out of system.img . I had to use WindowsLGFirmwareExtract-1.2.1.0-Release as the newest one would dump 20G+ junk files.
Code:
$ file system_691200.bin
system_691200.bin: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
I can't mount the file, after making it the size it wants with "truncate -s $((1159168*4096)) system_691200.bin" it will mount but then is completely empty. Repairing with fsck annihilates everything. What is the trick to dumping/mounting this?
modem.img mounted fine.
baconbacon said:
How do I grab the files out of system.img . I had to use WindowsLGFirmwareExtract-1.2.1.0-Release as the newest one would dump 20G+ junk files.
I can't mount the file, after making it the size it wants with "truncate -s $((1159168*4096)) system_691200.bin" it will mount but then is completely empty. Repairing with fsck annihilates everything. What is the trick to dumping/mounting this?
modem.img mounted fine.
Click to expand...
Click to collapse
The latest should work fine but you have to merge (!) the files once extracted which is a separate option in that tool. For mounting you could then use SALT (advanced menu) if you like
Sent from my OnePlus 6T using XDA Labs
It only extracts one system file, system_691200.bin, there is nothing to merge. That's with 1.2.6.1, I tried several different versions and all of them only list/extract one file. The tot I used is not corrupt (i believe), downloaded 3 more and they all had the same md5.
Do you know offhand if I would be able to push the system_691200.bin onto the phone and mount it just to grab those files?
baconbacon said:
It only extracts one system file, system_691200.bin, there is nothing to merge. That's with 1.2.6.1, I tried several different versions and all of them only list/extract one file. The tot I used is not corrupt (i believe), downloaded 3 more and they all had the same md5.
Do you know offhand if I would be able to push the system_691200.bin onto the phone and mount it just to grab those files?
Click to expand...
Click to collapse
ok when it lists only 1 file there it is only 1. Lemme check if I can do that today.
EDIT:
ah yea another reason why I hate that windows tool.. it extracts bull****.. trying to fix that but that can take some secs
EDIT2:
wow thats is really a stubborn crap.. Cannot mount, resize, fsck, fix, testdisk/photorec , ... (and yea I used DD to get the correct size, offset ...)
EDIT3: @baconbacon
no one is as stubborn as me lol..
ok I have not figured out why that crappy windows software does not extract it correctly but I searched and found another extractor here. (whoa.. that way I could make TOT files support available in SALT...)
compiled. ran. mounted. simply works..
so here you go: http://leech.binbash.it:8008/stock/LG/h810/21y_arb3
you just need: h810_21y_ARB3_system-etc-firmware.tgz
download that one.
extract it and follow the prev post here
jfi:
I am currently uploading the full system image and other stuff of that firmware as well (should be fully uploaded in 40 min or so)
.-
That fixed it completely! Sound works, rotation works, camera works. Installed the newest rom and the phone is quite snappy now. As a bonus it also fixed the video lag.
Thank you very much, you went above and beyond to help me fix this. Is that bitcoin address on your profile accurate?
baconbacon said:
That fixed it completely! Sound works, rotation works, camera works. Installed the newest rom and the phone is quite snappy now. As a bonus it also fixed the video lag.
Thank you very much, you went above and beyond to help me fix this. Is that bitcoin address on your profile accurate?
Click to expand...
Click to collapse
GREAT ! Glad we solved it.
I really hoped it will fix it and yea that's again a proof of fusing in modem and firmware files (due to flashing the 21y modem).. I will remove that one from the list so no one will go for the same journey.
yea my BTC is fine but given some thx click on any of my posts is fine too
have fun!
.-
here are some commands I have tried after root following @sd_shadow 's guide
[email protected] ~ $ adb remount
/system/bin/sh: remount: inaccessible or not found
caprip:/ # mount -o rw,remount /system
mount: '/system' not in /proc/mounts
caprip:/ # mount -o rw,remount /
'/dev/block/dm-0' is read-only
caprip:/ # touch file
touch: 'file': Read-only file system
Wanted to post something like this right now since i have the same problem, i think for adb remount to work you need to first run adb root, but that doesnt work unless you modify ro.debuggable=0 to 1 which cannot be done since you cant mount system as rw, i will keep you updated if i find anything tho!
- Apparently you can modify the boot.img to set ro.debuggable=1 but most of the tools i tried dont recognize this phones boot image as valid so i wont really spend more time on this since i think its something way beyond the scope of what i can do. And the only tool that worked outputted a unusable archive, i think this has to do with the source of the device being closed or something related to why we dont have custom roms on this device yet. But dont take my word for it since i just started playing with stuff like this a few hours ago so i can remap the assistant button.
And even if i could modify it i have a hunch it would behave just as using remount from shell.
If anyone who understands this better than me could provide some insight to my rambling it would be great!
The reason for this behaviour is the unified "super" partition. /system is dynamic, i.e. it may change size depending on future updates. /vendor is also a part of the "super" partition, thus is also read only. There is a way to restore rw access but it a) is not guaranteed and b) affects the ability to apply OTA updates.
If you're willing to take the risk, you should be able to find the relevant post on here (XDA, not the G30 section) with some search fu. You will need a Linux machine and the knowledge to use it. The "run on device" unified script does not fully work on the G30 and you need to reconfig the super image on a Linux box.
Chron0s said:
The reason for this behaviour is the unified "super" partition. /system is dynamic, i.e. it may change size depending on future updates. /vendor is also a part of the "super" partition, thus is also read only. There is a way to restore rw access but it a) is not guaranteed and b) affects the ability to apply OTA updates.
If you're willing to take the risk, you should be able to find the relevant post on here (XDA, not the G30 section) with some search fu. You will need a Linux machine and the knowledge to use it. The "run on device" unified script does not fully work on the G30 and you need to reconfig the super image on a Linux box.
Click to expand...
Click to collapse
Can I have some more search terms to find what you are talking about?
I can do better than that but with the usual caveats of bootloops, hard-bricks, kicked kittens, spacetime anomalies and global thermonuclear war:
G30 /system rw
I remain totally immune for blame when this goes wrong. You need a disaster recovery strategy in place before trying this. Read the first post in that thread thoroughly before doing anything.
Make sure you have a copy of the correct stock ROM and at least RSD-lite to recover. Also, revert Magisk patched initrd (boot.img - be sure your stock matches the ROM version or you'll lose the touch screen/RIL) before attempting this method - you can restore it later but the script requires the live ROM on the device to be stock. This is not something Motorola can be blamed for, it's upstream and applies to all devices running with a super partition and dynamic /system and /vendor.
More caveats: You will lose OTA updates. You will still need to boot to fastbootd to access /system. There is still currently no custom recovery for this device. A manual update will put you back to square one, which is why I decided to forget rw on /system and use Magisk to debloat/degoogle as the method employed in the debloater persists across updates.
Chron0s said:
I can do better than that but with the usual caveats of bootloops, hard-bricks, kicked kittens, spacetime anomalies and global thermonuclear war:
G30 /system rw
I remain totally immune for blame when this goes wrong. You need a disaster recovery strategy in place before trying this. Read the first post in that thread thoroughly before doing anything.
Make sure you have a copy of the correct stock ROM and at least RSD-lite to recover. Also, revert Magisk patched initrd (boot.img - be sure your stock matches the ROM version or you'll lose the touch screen/RIL) before attempting this method - you can restore it later but the script requires the live ROM on the device to be stock. This is not something Motorola can be blamed for, it's upstream and applies to all devices running with a super partition and dynamic /system and /vendor.
More caveats: You will lose OTA updates. You will still need to boot to fastbootd to access /system. There is still currently no custom recovery for this device. A manual update will put you back to square one, which is why I decided to forget rw on /system and use Magisk to debloat/degoogle as the method employed in the debloater persists across updates.
Click to expand...
Click to collapse
As long as I still have access to the bootloader I it should be fine? Also others on this device thread don't have this issue, why?
As long as you can boot to fastboot, you should be able to recover. There are, of course, exceptions to this as every G5s plus owner who ever deleted the persist partition without a bit-perfect backup will know only too well.
I haven't seen a single instance of anyone on a dynamic /system device, including the Moto G30, being able to remount /system rw without jumping through hoops like these. Perhaps it is simply because most people know that dynamic /system became A Thing recently. Again, this is on Alphabet, not Lenovo/Motorola.
This is also why this device section is full of "how to root" queries as the traditional method of banging su into /system/sbin and installing a management APK doesn't work with dynamic partitions. The only way to get a working su binary onto the system is via initramfs preloaded with the kernel, which is what Magisk patches and is why Magisk is the only root solution for this device.
If you think I'm typing nonsense, that's fine. Here's the advice, it was free and comes with a guarantee worth exactly what you paid for it.
No, not at all. Thanks for your help, Got error 73 which is where the Linux comes in so I imagine it's probably fine? I'll run the repair script when I get home later.
Error 73 is exactly the error I got, which is indeed why you need the older Linux method of patching the super image.