Related
UPDATE - I have built the required kernel modules ( magic: 3.0.8+ SMP preempt mod_unload ARMv7) for ICS.
Download: archos-ics-gsm.zip
Remember these are only the kernel level drivers and a bit more hacking is required if you want to used these in the android environment.
Happy Hacking!
[ORIGINAL POST]
Hi
Here is the required kernel module (usb_wwan.ko) to enabled the modem functionality at the kernel level for Huawei 3G Dongles on the archos G9.
I don't know if anyone will find it useful but I thought I'd share it anyway
It was built from the archos-g9-gpl and is compatible with kernel version "2.6.35.7+ #1 SMP PREEMPT"
Notes:
Huawei USB 3G Modems actually require 2 modules to function usb_wwan.ko and option.ko. Archos already ship option.ko in /lib/modules on the device so this was the only one missing.
To use:
1. insmod usb_wwan.ko
2. insmod option.ko
3. Use usb_modeswitch to initialize the modem
The modem can be then be found at /dev/ttyUSB*
See this post for a quick guide into making a ppp connection using this driver
Thanks
I'm very interested in this. So I have a Huawei EC168 air card from a little cdma provider named Alltel (who is now partially owned by Verizon), would installing this allow it to function? I mean do you know if this is a universal driver or is it meant for GSM only?
I'm a bit of a noob at this. I've got the first two commands to run and usb_wwan.ko is just in my /mnt/storage
What are the specific switches I need to get the usb_modeswitch command working? -H just results in "No default vendor/product ID given. Aborting."
Btw I'm running everything through Terminal Emulator as I don't have adb or anything like that up and running currently on my computer.
Edit: I can't mess with this until I get hdd mounting working again. That was the whole reason I bought this tablet.
If anyone can help with that my topic is here. http://forum.xda-developers.com/showthread.php?p=22722509
I'm unsure whether this is a CDMA driver but you can give it a go.
From the command line I copied usb_wwan.ko to /lib/modules on the device and then did then following (the command should work equally as well in terminal emulator, with out the adb shell bit obviously )
Code:
adb shell insmod /lib/modules/usb_wwan.ko
adb shell insmod /lib/modules/option.ko
Then I Usb Mode Switched to the modem. I my case a Huawei E1752 [O2 UK Branded]
I discovered the correct target product [0x1436] (which isn't included in the 12d1_1446 config file) after plugging it into linux an listing my USB devices using lsusb in a terminal window.
Code:
adb shell usb_modeswitch -s 6 -v 12d1 -p 1446 -V 12d1 -P 1436 -M 55534243123456780000000000000011062000000100000000000000000000 > /dev/null
Obviously the usb modeswitch parameters are unique to your device and you can of course specify a configuration file using the -c switch instead of using the switches I have here.
After this I had access to the modem on the /dev/tttyUSB*
I gave the modem about 1 minute to initialize and then ran
Code:
adb shell /system/bin/pppd /dev/ttyUSB0 115200 nocrtscts nocdtrcts local usepeerdns defaultroute noipdefault ipcp-accept-local ipcp-accept-remote user cmnet password cmnet debug kdebug 7 connect "/system/xbin/chat -v -t 500 -s -f /data/media/gprs_start"
This brings up a PPP connection on ppp0. Although it didn't register as any sort of connection in android, it does however allow me to use the android web browser on this connection.
Note:
You do need 2 additional files which I have attached - The gprs_start script which I copied to the /data/media directory and is run by pppd and ip-up which you need to place in your /etc/ppp directory. This handles setting the correct dns servers after you have connected
This method is a little rough and I have been experimenting with the android ril interface but I'm having some problems keeping the connection alive for any length of time after starting the ril-daemon and I found the connection was at it's most stable when the ril-daemon is stopped.
Hi
trevd said:
It was built from the archos-g9-gpl and is compatible with kernel version "2.6.35.7+ #1 SMP PREEMPT"
Click to expand...
Click to collapse
Hi. how you install this kernel?
Add link
I didn't manage to get the full kernel to build because there was errors in the makefile last time in downloaded the source
out of more speculation than anything else I copied the makefile from the gen8 gpl source.
This didn't complete the build, it failed on ffmpeg but it did build kernel modules which is all I really needed for this.
I might have another go now that I understand a little more about the build process and makefiles.
Sent from my HTC Sensation XE with Beats Audio using xda premium
trevd said:
I didn't manage to get the full kernel to build because there was errors in the makefile last time in downloaded the source
out of more speculation than anything else I copied the makefile from the gen8 gpl source.
Click to expand...
Click to collapse
Current kernel sources are fine- compilation went without any problems. Included linux.config seems to be the recovery kernel config though (2.5 MB zImage, quite some modules built).
Compiled using crosstool-ng 1.9.3 on xubuntu 10.10 x86 (in VirtualBox)
hi, very interested in this, I have an Archos 80 G9 16GB Turbo and a Huawei USB 3G dongle as well. But I'm coming from windows mobile, just my first android device. Anyone willing to give some more info & instructions on how to get it working all together? Is it required to have a rooted device?
Maybe a little app can be created to automate the installation/usage of non archos USB 3G dongles?
CIAO!
VOODOOS!L
Hi Voodoos!l
Rooted Device is required. Apologies for the light instructions post 3 explains slightly more
It still may not be enough if your coming from a windows only environment!
I Assume at least some basic knowledge of:
Android Debug Bridge (ADB)
Composite Usb Devices (usb_modeswitch)
Android/Linux Kernel Modules (Installing insmod /lsmod etc)
Point to Point Protocol (How to start a connection)
I did write a quick and dirty app to do the mode-switching and then start the connection, I can give you the code if you want, it's nothing special, It just runs the commands from android using Superuser.
I've not had chance to work on this lately and I think a better route to go down is to hack the UsbKeyManager.apk which is what Archos use to turn on there own 3G Dongle. We should be able to modify it to accept any dongle. I had begun testing with HoneyComb but was waiting for ICS to appear before continuing.
i have archos 101 g9 can you have a video to do this?i have pen k3565 vodafone
@ trevd
i am very insteresting by a video or photos
and a todo for Dummys
Hi Guys.
I'll get the drivers compiled for ICS later on and see If I can get smoother solution for you folks to play with.
@jamespvz Is this the one you have http://3g-modem.wetpaint.com/page/Huawei+K3565+%28Vodafone%29? can you confirm that this is the one made by Huawei and not ZTE?
TIP: The Huawei one has the code K3565-H
Thanks
Trev
yes is that pen
Hi all.
I'm following this thread too because I need a 3g adapter but I found that the archos one is 7Mbps, while I'd like to have a 14Mbps one. Trevd, I hope that you will find the solution for me and the other archos fans!
If you suggest me a good adapter, I'll buy it and then help you with tests.
Thanks.
Bye
Hello
this work with ICS 4?
Regards, Robert
file is corrupt archos-ics-gsm.zip 554 byte ... resend please
h47e said:
file is corrupt archos-ics-gsm.zip 554 byte ... resend please
Click to expand...
Click to collapse
The file is not corrupt, i'ts correct 404 error html. But not zip, really.
# usb_modeswitch -s 6 -v 12d1 -p 1446 -V 12d1 -P 1436 -M 55534243123456780000000000000011062000000100000000000000000000
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
No devices in default mode found. Nothing to do. Bye.
# ls -la /dev/tty*
crw-rw-rw- 1 root root 5, 0 Apr 21 18:04 /dev/tty
crw------- 1 root root 249, 0 Apr 21 18:04 /dev/ttyGS0
crw------- 1 root root 249, 1 Apr 21 18:04 /dev/ttyGS1
crw------- 1 root root 249, 2 Apr 21 18:04 /dev/ttyGS2
crw------- 1 root root 249, 3 Apr 21 18:04 /dev/ttyGS3
crw------- 1 root root 252, 0 Apr 21 18:04 /dev/ttyO0
crw------- 1 root root 252, 1 Apr 21 18:04 /dev/ttyO1
crw------- 1 root root 252, 2 Apr 21 18:04 /dev/ttyO2
#dmesg
[ 2338.794708] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 2338.795043] hub 1-0:1.0: unable to enumerate USB device on port 1
Bus 002 Device 013: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552 (HSPA modem)
3g stick ON
I'm running MyROM 1.2 and it doesn't have tun.ko which I need. I tried the installer from google play without success. I'm willing to change ROMS if necessary but I need to know which ones have it already integrated or how to install it. If I have to compile it please give details instructions.
go0 said:
I'm running MyROM 1.2 and it doesn't have tun.ko which I need. I tried the installer from google play without success. I'm willing to change ROMS if necessary but I need to know which ones have it already integrated or how to install it. If I have to compile it please give details instructions.
Click to expand...
Click to collapse
Module must be compiled exactly for your kernel version.
You have to download kernel sources, compile kernel and module, so vermagic of kernel and module will be the same.
I can try to compile this module for you, but you need to provide me content of your /proc/version file for spoof kernel version for verification.
Kostyan_nsk said:
Module must be compiled exactly for your kernel version.
You have to download kernel sources, compile kernel and module, so vermagic of kernel and module will be the same.
I can try to compile this module for you, but you need to provide me content of your /proc/version file for spoof kernel version for verification.
Click to expand...
Click to collapse
Hi Kostyan,
I'm not certain I know where to get the sources from and the next steps to compile the module. Is there a tutorial somewhere?
My /proc/version reads:
Linux version 3.0.8-00370-g3be8d90 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PEEMPT Tue Sep 2 13:21:11 CST 2014
Click to expand...
Click to collapse
Create directory for module:
Code:
adb shell
su
mount -o rw,remount /system
cd /system/lib
mkdir modules
exit
exit
Copy module in /system/lib/modules
Set permission 644 for tun.ko
Try to load module:
Code:
adb shell
su
insmod /system/lib/modules/tun.ko
if insmod will fail, get error description by this command:
Code:
dmesg | grep insmod
P.S. All these operations requires full root access.
(Download 2016-12-16 TWRP 3.0.3 : https://www.androidfilehost.com/?fid=673368273298921729)
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
[EXP] Multirom33 TWRP3.1.1 +TrampolineV27 +MultiROMMgr.apk with No-Kexec work-around
Credits ( @mkasick ) @Tasssadar https://forum.xda-developers.com/showthread.php?t=2104706
p880 ( @Adam77Root ) @Demetris @fritzcola https://forum.xda-developers.com/optimus-4x-hd/orig-development/mod-multirom-v32-t3116422
Source https://github.com/Tasssadar/device_asus_grouper
https://github.com/P880-dev/android_kernel_lge_x3/commit/de499e8fd657925a74015f62229c5165620f127a
Complete manual : https://forum.xda-developers.com/showthread.php?t=2011403<--donations' thread
DOWNLOAD FILES : https://www.androidfilehost.com/?w=files&flid=146943
twrpMR3.0.3 sources : https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom
Roms kick-flip are auto-explanatory...
-for 2ndRoms, twrp3__MR33v27 simulates a clean virtual format/data at every new creation (without wiping your internal medias & files !)
-multirom' Trampoline works with all recoveries (cwm&twrp) and provides a stand-by interface (added in your primary installed kernel), with all reboot options, and authorized adb (shell ls /mrom_bin /realdata ...)
-all your roms can be matched with dedicated onboot script.sh https://github.com/Tasssadar/multirom/wiki/run-on-boot-scripts
-attached Cyospak7-2016.zip is a kexec-ed compatible (any)kernel with: cm12 aosp5 aosp6 aosp7
Due to pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img , p880 will likely NOT be official for MultiROM Manager app
NEW triple EDITION with No-Kexec work-around (boot.img shuv-it)
-20170517 twrp3.1.1(f2fs1.7) img MultiROM : //github.com/multirom-dev/Team-Win-Recovery-Project/commits/android-7.1-mrom
-20170701 Multi-boot zip menu ://github.com/multirom-dev/multirom/commits/master
-MultiROMMgr apk ://github.com/AdrianDC/MultiROMMgr/commits/master
TIP for hard buttons: using one nail to light click isn't as destructive as "fat" fingerprint pressure !
Kernel GPL
f2fs [WIP]
wip (kernel & mount_options*3fstab...)
DOWNLOAD exp f2fs 1.7: X-twrp3_1_0-20170308-f2fs1_7-ufoFLASH-p880.img
TWRPpost#1 are built with (2015-03-04omni6=aosp7=cm12.1)f2fs-tools v1.4.1 & adb authorized
(cm11 uses older 2013-10-25v1.2)
-official p880 recoveries twrp3.0.2/cwm6.0.5 do not include f2fs support
-unmodified p880 recoveries (from source) do not include specific p880 cold boot to recovery : always ext4
-aosp7 & omni7 are using same old f2fs than cm12 : 1.4
-"setup-recovery" is an arbitrary sh designation for one action/phrase to skip p880 cold boot : echo "boot-recovery" | /sbin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
- @laufersteppenwolf twrp2.7.1 was compiled with an added tool fibmap.f2fs, probably to countercheck the specific p880 cold boot (ext4)
-all recoveries can not mount any partition if p880 specific mmcblk0p5 is not void/wiped by postrecoveryboot.sh
- @alfsamsung cm13 doesn't support f2fs for now
So once again, IMHO, Multirom Trampoline is best universal solution to specific p880 cold boot : it provides a stand by menu (linux primary kernel) where you can reboot to bootloader directly (or primary/2nd roms...), and "warm reboot to recovery" option...
I believe that twrp' sources & missing fstab2, have nothing wrong , the origin is the non-standard (secure?) cold boot for p880: all other Tegra3 devices have hybrid ext4/f2fs OK(asusTF700 with official twrp). The best will be to find @laufersteppenwolf twrp2.7.1 repo; the worst is to use cwm editions.
Click to expand...
Click to collapse
with tool like 3CtoolboxFree you can trim/clean etc ; within 3C/terminal/SUticked : type "setup-recovery" then aosp6/7 reboot will get you to twrp & f2fsOK..
3C can behave intrusive, but you can use it static : greenify + autostarts
Finally remember that depending twrp_romVersion and mount/flag used for format/f2fs, can give minor changes (?) : aosp6/7 omni6/7 and cm12 are on "old" regular =1.4.1 ;
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-CM ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 23:58:55 CET 2017"
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery DATA.cpp folder.
Nameless3 =1.5
Only cm13 =1.6.1 and cm14.1 =1.7 include more options : defrag ....
Code:
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...
F2FS-tools: mkfs.f2fs Ver: 1.6.1 (2016-03-22) [modified by Motorola to reserve space]
Info: Debug level = 0
Info: Label =
Info: Segments per section = 1
Info: Sections per zone = 1
Info: Trim is disabled
Info: sector size = 512
Info: total sectors = 786432 (384 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-aosp67 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sun Jan 15 00:32:53 CET 2017"
Info: Overprovision ratio = 10.000%
Info: Overprovision segments = 43 (GC reserved = 28)
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery folder.
When you format via twrp run the save_log option and check the end.
Click to expand...
Click to collapse
(Thx to @Phil_Smith @kessaras for pre-testing)
What: /sys/fs/f2fs/<disk>/gc_max_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the maximun sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_min_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the minimum sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_no_gc_sleep_time
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the default sleep time for gc_thread. Time
is in milliseconds.
What: /sys/fs/f2fs/<disk>/gc_idle
Date: July 2013
Contact: "Namjae Jeon" <[email protected]>
Description:
Controls the victim selection policy for garbage collection.
What: /sys/fs/f2fs/<disk>/reclaim_segments
Date: October 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of segment discard commands.
What: /sys/fs/f2fs/<disk>/ipu_policy
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the in-place-update policy.
What: /sys/fs/f2fs/<disk>/min_ipu_util
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the FS utilization condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/min_fsync_blocks
Date: September 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the dirty page count condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/max_small_discards
Date: November 2013
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the issue rate of small discard commands.
What: /sys/fs/f2fs/<disk>/max_victim_search
Date: January 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the number of trials to find a victim segment.
What: /sys/fs/f2fs/<disk>/dir_level
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the directory level for large directory.
What: /sys/fs/f2fs/<disk>/ram_thresh
Date: March 2014
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the memory footprint used by f2fs.
What: /sys/fs/f2fs/<disk>/trim_sections
Date: February 2015
Contact: "Jaegeuk Kim" <[email protected]>
Description:
Controls the trimming rate in batch mode.
what still WIP ??
Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
Was about to ask the same thing, if I remembered correctly I have seen a recovery released by OP supporting f2fs...... but anyway keep up the good work.
b886b said:
@oF2pks do U mean that with twrp 3.0.3 on your AFH, we will be able to flash AOSP 7 rom, gapps and supersu consecutively without the need to reboot recovery in between like that in cwm????
Click to expand...
Click to collapse
Salman Al-Badgail said:
what still WIP ??
Click to expand...
Click to collapse
First, just want to be sure everything works clear with ext4, for aosp6/7 + opengapps without any error/miss; then I'll upload a recoveryTWRP303.zip for CWM's users to easy install.
WIP: concerning f2fs, apparently there is an issue on cold boot to recovery and f2fs/data returns to ext4 (?!), also I did not try f2fs myself since I'm using Multirom with hidden 2nd Roms: I will soon (after I proceed my backups & AsusTF700->f2fs).
The p880-dev/X3/fs/f2fs is 2015Feb update (much better then AsusTF700!): "Controls the trimming rate in batch mode"; and I'm not sure on best mount options flags.
IMHO, most relevant will be to get fstab' [boot.img(1) + recovery.img(*3)]=4 in par for real testing, on this latest Omnirom based recovery303 ( the CM based 303 looks less accurate).
screen flickers
oF2pks said:
Download : https://www.androidfilehost.com/?fid=673368273298921729
Click to expand...
Click to collapse
Is it just me screen flickers when you press the navigation keys at the bottom?
Even worse is TWRP2.8.6_multirom_p880_20150523.img.
While the screen is perfectly stable in twrp-3.0.2-0-p880.img.
Sparkling! edition (ie wip)
Indeed, like twrpMR2.8.6, screen has some hiccups overlays, but works 100% OK.
Comparing to official twrp 3.0.2, both 2.8.6 & 3.0.3 don't load right framebuffer=3 ; I hope @fritzcola tell us more, also hard to get exact device tree (omni br. ?) from master @Dees_Troy .
Anyway it's remind which twrp being in use (versus nice official); also I remember an assertion on lightweight (? with possible lzma/ramdisk).
Code:
TWRP 3.0.2 graphics OKofficial[/U][/B]
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 3.0.2-0 on Thu Dec 29 14:55:25 2016
(pid 136)
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/tegra-udc.0/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
[B]Starting the UI...Skipping adf graphics -- not present in build tree
Skipping drm graphics -- not present in build tree[/B]
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
[B]double buffered
[U]framebuffer: 3 (720 x 1280)[/U] #####instead of 0->flickering (?)######
Using fbdev graphics.[/B]
I initially voted for data + cache in f2fs, but after several testing I found that the cache does not need to be trimmed regularly so I suspect that only data in f2fs can have improve the performance of our device. I have tested for several cycles using the app fstrim for several weeks and it definitely helps in the way our phone performs, after fstrim our device is more snappy and the sluggish feel after long time usage has significantly decreased. However, whenever I run fstrim it always says that cache does not need to be trimmed so I believe the performance boost is due to the trimming of data partition which leads me to believe that the culprit of our sluggish performance was due to the cramming up of data partition. So I think data in f2fs would be enough.
2017 22 Jan update post#1 [.ZIP] attached
Thx to TeamWin, twrp 3.0.3 is a wip "live" edition for now : https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Soon or later TeamWin will push official p880 (non flickering) thread; while waiting, I will frequently update post#1 from latest github, with a :
-cwm compatible zip
-aosp7 OK with queueing list' zip
-f2fs-tools version1.4.1 (=aosp7=cm12.1)
-adb authorized
-(sparkling edition...)
[twrp 3.0.3] MultiROM : back in blue ! (2016-12-16)
@ze7zez , @juantech , @b886b
Thx to @fizbanrapper (github), no more twrp shove-it for roms kickflips : just focus on aosp7/cyospak7 on primary and flash (upRight burger) your favourites on 2nd (cm11/12/13 aosp6 lgJB omni4 beanstalk4...).
Download 3.0.3 (f2fs1.4.1) : https://www.androidfilehost.com/?fid=817550096634741392
Cyospak7 anykernel is compatible with aosp6 (15~20mn install/2ndRom !), and includes iodak fstab2 f2fs switch. I'll try to upgrade cm13 (only multiboots lgJB for now) with latest kexec soon; cm12.1/Nameless2 are already compatible.
Don't forget to flash the trigger MultiROM trampoline AND pressPOWER/till1stVIBER trick for 2nd/roms/non_shared_boot.img (specific to old p880 boot on/off process).
SuperSu.zip flash can be tricky, due to 2*reboot (via MultiROM): try 2.78sr5.zip+AppUpgrade2.79.apk, with aosp6 on 2nd. Xposed flash works fine.
Until now, basic rule was to flash highest android version on primary.
You tell me...
Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx
dave2609 said:
Hey oF2pks,
Does this recovery flash android 7 without any errors or problems.?
I will flash aosp 7.1 by csk1jw
Thnx
Click to expand...
Click to collapse
Yes indeed, latest twrp3.0.3 build is 2017-01-27 (MultiROM included), but on very new first install, you should always follow OP recommendations : until now @csk1jw is still on cwm6.0.4.5 & OpenGapps stock/WebView; you can still swap cwm/twrp recoveries later, but backups/nandroid are not compatible. Personally I prefer latest twrp3.0.3 and @Deltadroid modular Gapps packages.
Okay thnx,
But how to install aosp 7 by csk1jw
With this recovery?
Just normal procedure?
TWRP MultiROM 2017-02-20 & f2fs 1.6.1
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/Team-Win-Recovery-Project/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
oF2pks said:
New twrp-MultiROM-20170220 is now built with Omni7.1.1, f2fs-tools Ver: 1.7.0 (2016-07-28) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.
red error 7 primary
oF2pks said:
New twrp-MultiROM-20170220 is now built with LineageOs13, f2fs-tools Ver: 1.6.1 (2016-03-22) & adb authorized
https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom
You can still download regular f2fs_Ver1.4.1 (aosp6/7 cm12.1) in post 1&2.
Click to expand...
Click to collapse
ze7zez said:
Almost success! :good:
The interface in this version flickers occasionally.
But still flickers after the entry mode log.
Nevertheless, it should be a warning for people with photosensitive epilepsy.
Click to expand...
Click to collapse
(One more miss,) sorry for that , I removed this untimely build which was buggy ; I wanted to upload another one (Lineage f2fs1.6.1) but error 7 was always back on aosp/primary: after multiple tests on my ok lucky last build twrp303MR2017-01-27.img (regular omni6 and f2fs 1.4), I noticed that switching from aosp6 to aosp7 on primary, could bring error7/system back on 3# zip flash. In this case, follow:
-wipe /system/data/cache (if error mount/system do => hard/keys cold reboot to recovery and repeat wipes)
-repair /system+/data+/cache
then you can flash up to ten zip consecutive+reboot in one action. (don't forget Cyospak7-2016 for MultiROM)
ALL THIS won't tamper your personal data & secondary roms.
I don't get how old cwm 6.0.4 can handle this (maybe e2fsk auto on fresh install?).
Also I didn't find a solution to get @alfsamsung / @iodak cm13 pass file system f2fs check on boot strange that both guys quit xda at same 2016-11-16 ?!)
oF2pks said:
...
Check attached 'install'.zip (to be flashed via cwm or twrp) file, for a more recent edition of twrp3.1.0-0 !
Built with Omnirom 6 repo, from unmodified bootable /TeamWin branch 7.1 (f2fs-tools v1.4)
More news: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Click to expand...
Click to collapse
New twrp 3.1.0 2017 03 07, check post#1 attached zip
oF2pks said:
New twrp 3.1.0 2017 03 07, check post#1 attached zip
Click to expand...
Click to collapse
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
f2fs 1.7 post#3 (adb/authorized)
For futur? roms only : post#3 updated with unmodified 2017-03-08 TWRP 3.1.0 and f2fs 1.7 (Omnirom7.1) (adb/authorized).
https://github.com/omnirom/android_external_f2fs-tools
Magisk Mount , UnMount & ReSize IMG
This is Magisk Mount , UnMount & ReSize IMG ZIP for Users/Developers.
A.K.A. "M2RI" in Short For MagiskMountReSizeIMG.
By Dark❶
Profile @ XDA-Developers : Dark❶ .
Profile @ GitHub : Dark❶ .
Magisk Mount & UnMount IMG :-
GitHub Pages Site : Magisk Mount & UnMount IMG
GitHub Repository : MagiskMountUnMountIMG
XDA Developers Topic : [Magisk] Magisk Mount & UnMount IMG
Notes :
Useful for Users/Developers who wants to Edit Magisk IMG.
This script is Depending on "Magisk" Binary File , Will Not work without IT.
Module folder can be [Deleted/Added] to [Remove/Add] a Module.
File can be [Edited/Modified/Deleted/Added] as per Users/Developers wish.
This ZIP Mount's OR UnMount's on Different Condition's :
1. If "magisk.img" is NOT Mount'ed , Then Mount "magisk.img" To "/Magisk" .
2. If "magisk.img" is Mount'ed , Then UnMount "/Magisk" From "magisk.img" .
This ZIP ReSize's on Different Mounting OR UnMounting ReSize Mode Condition's.
Following is the Pseudo Code for Mount & UnMount :
IF [ ReSize Mode Only ] , Then :
Will UnMount Magisk IMG If Mounted. ~ UnMount "/Magisk" ⇏ "magisk.img" .
This ZIP will ReSize Magisk IMG as-per User Requirement.
ELSE-IF [ "magisk.img" is NOT Mount'ed AND Mounting is Allowed ] , Then :
This ZIP will ReSize Magisk IMG as-per User Requirement.
Then , will Mount Magisk IMG. ~ Mount "magisk.img" ➔ "/Magisk" .
ELSE-IF [ "magisk.img" is Mount'ed AND UnMounting is Allowed ] , Then :
This ZIP will UnMount Magisk IMG. ~ UnMount "/Magisk" ⇏ "magisk.img" .
Then , will ReSize Magisk IMG as-per User Requirement.
ELSE , Then :
This ZIP will Do Nothing BUT Print some Sh*t InFo.
Following is the Pseudo Code for ReSize Mode :
CASE "ReSizeMode" IN
0 , Then :
Display InFo of Magisk IMG "magisk.img".
1 , Then :
ReSize** to Default "64MB" OR MoRe Depending on Current Used IMG Size.
2 , Then :
ReSize to *User Specified Size* ,
BUT NOT less than "64MB" OR Current Used IMG Size.
*User Specified Size* Need's to be Positive[+] Only.
3 , Then :
**ReSize** to Current IMG Size + User Specified Size = Total,
BUT *Total* is *NOT* less than "64MB" OR Current Used IMG Size.
*User Specified Size* Can be Positive[+] OR Negative[-].
I have Copied the Code from "magisk-module-template" ZIP by @topjohnwu.
I have Edited some part of the Code to make it work.
I have Added some part of the Code to make it work.
I have Added some Necessary File(s).
I have Removed Un-Necessary part of Code Because It is Either Not Used OR Not Needed.
I have Removed Un-Necessary Directory(s) & File(s) Because It is Either Not Used OR Not Needed.
I have DoNe Some Optimization to code.
Download : MagiskMountReSizeIMG-v2.0.zip
Download History : XDA:DevDB Downloads OR This Post .
...
XDA:DevDB Information
Magisk Mount ReSize IMG, Tool/Utility for all devices (see above for details)
Contributors
Dark❶
Source Code: https://github.com/dark-1/MagiskMountReSizeIMG
Version Information
Status: Stable
Current Stable Version: 2.0.0
Stable Release Date: 2017-10-25
Created 2017-09-19
Last Updated 2017-10-25
Reserved
Reserved
Explanation :
Explanation from "config.sh" :
Code:
###############################################
## Mount / UnMount Switch [..SW] ##
###############################################
#
# To be Set For "MTSW" , "UTSW" & "ROSW". [..SW]
#
# Set to " true " , To Allow Mount / UnMount .
# Set to " false " , To Prevent Mount / UnMount .
#
# Default is " true " , For Both , "MTSW" & "UTSW". [..SW]
# And " false " For "ROSW".
#
###############################################
###############################################
## ReSize Mode [..RSMO] ##
###############################################
#
# To be Set For "MTRSMO" , "UTRSMO" & "RSMO". [..RSMO]
#
# Set to " 0 " , To Display InFo of Magisk IMG "magisk.img".
# Set to " 1 " , To ReSize to Default "64M" OR MoRe Depending on "Current Used Size".
# Set to " 2 " , To ReSize to "User Specified Size".
# Set to " 3 " , To ReSize to "Current IMG Size" + "User Specified Size".
#
# Default is " 0 " , For All , "MTRSMO" , "UTRSMO" & "RSMO". [..RSMO]
#
###############################################
###############################################
## User Specified Size [..RSMB] ##
###############################################
#
# To be Set For "MTRSMB" , "UTRSMB" & "RSMB". [..RSMB]
#
# All Number's Here Should be Multiple of " 4 " AND in MegaBytes[M].
# AND No Need to Specify character " M " OR " MB ", Just a Number.
#
# IF ReSizeMODE is " 2 " ,
# Then "User Specified Size" Should NOT be less-than "64MB" OR "Current Used IMG Size".
# AND "User Specified Size" Need's to be Positive[+] Only.
# No Need to Specify character " + ".
# IF ReSizeMODE is " 3 " ,
# Then "Current IMG Size" + "User Specified Size" = "Total",
# AND "Total" Should NOT be less-than "64MB" OR "Current Used IMG Size".
# "User Specified Size" Can be Positive[+] OR Negative[-],
# Hence Need to Specify character " + " OR " - ".
#
# Default is " 64 " , For All , "MTRSMB" , "UTRSMB" & "RSMB". [..RSMB]
#
###############################################
Example from "config.sh" :
Code:
###############################################
## Example's ##
###############################################
#
# While Mounting , you want the "magisk.img" to be 80MB,
# then "MTRSMO" & "MTRSMB" will be :
# MTRSMO=2
# MTRSMB=80
#
# Now , after Mounting the "magisk.img" ,
# And While UnMounting , you want the "magisk.img" to be Reduced by 12MB [-12MB],
# then "UTRSMO" & "UTRSMB" will be :
# UTRSMO=3
# UTRSMB=-12
#
###############################################
EnJoY ...
Download History :
Download :
v1.0 : MagiskMountReSizeIMG-v1.0.zip
v2.0 : MagiskMountReSizeIMG-v2.0.zip
Changelog
v0.0
- Initialized.
v1.0
- Initial Release.
- Copied the Code.
- Edited some part of the Code.
- Added some part of the Code.
- Added some Necessary File(s).
- Removed Un-Necessary part of Code.
- Removed Un-Necessary Directory(s) & File(s).
v2.0
- Yea! Jump in Version.
- Updated "update-binary".
- Fix a Critical Bug due to Duplicate Code.
- Optimized the Code.
- Added some Checks.
Credit's
Thank's @topjohnwu for Magisk & for the code in "magisk-module-template" , could not have done without it.
Announcement :
This Thread is not Completed , Kindly give Me some Time Slag .....
Thread is now Completed. Thanks for your Patience.
MagiskMountReSizeIMG v2.0
Here is MagiskMountReSizeIMG v2.0 :
- Yea! Jump in Version.
- Fix a Critical Bug due to Duplicate Code.
- Optimized the Code.
- Added some Checks.
Download : MagiskMountReSizeIMG-v2.0.zip
Wouldn't mind a set of usage instructions that are a bit clearer as opposed to being outlined in pseudo-code. What I'm gathering is that you flash to mount/unmount and that image resizing is automated based on your additions/deletions. That sound about right? Is this to be flashed in recovery or via Magisk Manager?
return.of.octobot said:
Wouldn't mind a set of usage instructions that are a bit clearer as opposed to being outlined in pseudo-code. What I'm gathering is that you flash to mount/unmount and that image resizing is automated based on your additions/deletions. That sound about right? Is this to be flashed in recovery or via Magisk Manager?
Click to expand...
Click to collapse
Yea!!!
& Only in Recovery. This is NOT a Module.
Check my 4th Post : https://forum.xda-developers.com/showpost.php?p=73852785&postcount=4
Cleaner Instruction than that ,,,, then I'll need some time.
Best regards. :good:
Dark❶ said:
Yea!!!
& Only in Recovery. This is NOT a Module.
Check my 4th Post : https://forum.xda-developers.com/showpost.php?p=73852785&postcount=4
Cleaner Instruction than that ,,,, then I'll need some time.
Best regards. :good:
Click to expand...
Click to collapse
No, you're right, my issues had less to do with lack of instructions and more to do with the fact that I'm trying to resize magisk.img on a device with A/B partitions. I don't know why it is, but I've tried plethora of resizing methods, as well as modules that should auto-resize but they all fail and I've discovered in the terminal app systemizer thread that there's a commonality of this issue on A/B devices.
Any chance for update, so it'll work with /data/adb/img?
ch3mn3y said:
Any chance for update, so it'll work with /data/adb/img?
Click to expand...
Click to collapse
Yea!!! I'll try , but no ETA.
I don't think it works with Magisk 17...
I get an error Magisk not found... ?
Dante63 said:
I don't think it works with Magisk 17...
I get an error Magisk not found... ?
Click to expand...
Click to collapse
Yea! I'll Update it soon ....
I am busy with other stuff...
Best regards :good:
Dark❶ said:
Yea! I'll Update it soon ....
I am busy with other stuff...
Best regards :good:
Click to expand...
Click to collapse
I'll be fixing myself...
I know what to do... ?
Great job though
Dante63 said:
I'll be fixing myself...
I know what to do... ?
Great job though
Click to expand...
Click to collapse
If you could make a PR , that would be highly appreciated my friend.
Best regards :good:
Dark❶ said:
If you could make a PR , that would be highly appreciated my friend.
Best regards :good:
Click to expand...
Click to collapse
I'm not good with binary I guess...
Since I get error 2...
I only do script...
I added the script in binary "I know it's different" but that's what I know and I simply crossed fingers hoping it's right ?...
I suppose I'll have to wait for you...
Dante63 said:
I'm not good with binary I guess...
Since I get error 2...
I only do script...
I added the script in binary "I know it's different" but that's what I know and I simply crossed fingers hoping it's right ...
I suppose I'll have to wait for you...
Click to expand...
Click to collapse
Hey!
Try this PR : https://github.com/dark-1/MagiskMountReSizeIMG
I have updated my repo , but it's not tested with all conditions yet.
but if you could , give it a try.
Best regards :good:
Hi All,
Device Detail:
- Samsung S10 5G
- Qualcomm Device
- Model: SM-G977U
- ROM: VZW-G977UVRU2ASH7-20190827135903
- Kernel-Version - Linux version 4.14.83-16633035 ([email protected]) (clang version 6.0.10 for Android NDK) #2 SMP PREEMPT Wed Aug 14 16:23:48 KST 2019
Background: I have
- rooted the device with instructions given by Magisk.
- I can successfully reboot to the recovery rootfs.
Problem: I am trying to modify the `system.img.ext4.lz4` file to root the device with normal boot. I am aware that it will not let the device install OTA Updates.
Unpack-Pack System and make new AP.tar, flash:
- Without any modification to the `system.img`, I have just unpacked `system.img.ext4.lz4`->`system.img.ext4`->`system.img`->mounted to system directory and packed it back to `system.img`->`system.img.ext4`->`system.img.ext4.lz4`.
- Replaced unpack-packed `system.img.ext4.lz4` with the AP `system.img.ext4.lz4` and make a tar of it.
- Then I have flashed it using Odin v3.13 along with BL, CP, and HOME_CSC.
- Odin has show PASS and I have rebooted the device into recovery mode.
- Done the Wipe data/factory reset and reboot to recovery again but released the recovery key combination on splash screen as mentioned in the root instructions .
- The device stuck in a boot loop.
Tries:
1. Disable Dm-verity
- Removed `avb` flag from `boot.img` with
Code:
magiskboot dtb boot.img patch
- Removed `avb` and `verify` flags from `dtbo.img` with
Code:
magiskboot dtb dtbo.img patch
- Patched `ramdisk.cpio` with
Code:
magiskboot cpio ./initrd 'patch false true'
Patched `boot.img` and `dtbo.img` is working fine with magisk patched AP file but the `ramdisk.cpio` creating the issue: Stuck at splash screen when trying to go to recovery after successfully flash with Odin. Download mode is appearing on splash screen.
So, I have used `boot.img` and `dtbo.img` along with unpack-packed `system.img.ext4.lz4` but the result is still a boot loop. I have also tried a combination of `boot.img` and `dtbo.img` along with unpack-packed `vendor.img.ext4.lz4` and flashed the AP.tar with other files but still the result is a boot loop.
So, I want to debug the problem and got to know about `pstore` which preserve the logs when kernel panic.
2. pstore
- Checked that `/sys/fs/pstore` is mounted by the system with following in init file: Grep the pstore using `find . | grep '\.rc' | xargs cat | grep pstore -n -i` and get following result:
Code:
314: # pstore/ramoops previous console log
315: mount pstore pstore /sys/fs/pstore nodev noexec nosuid
316: chown system log /sys/fs/pstore/console-ramoops
317: chmod 0440 /sys/fs/pstore/console-ramoops
318: chown system log /sys/fs/pstore/console-ramoops-0
319: chmod 0440 /sys/fs/pstore/console-ramoops-0
320: chown system log /sys/fs/pstore/pmsg-ramoops-0
321: chmod 0440 /sys/fs/pstore/pmsg-ramoops-0
- Checked the kernel config by pulling the file from /proc/config.gz.
Code:
$ cat config | grep PSTORE
CONFIG_PSTORE=y
CONFIG_PSTORE_ZLIB_COMPRESS=y
# CONFIG_PSTORE_LZO_COMPRESS is not set
# CONFIG_PSTORE_LZ4_COMPRESS is not set
CONFIG_PSTORE_CONSOLE=y
CONFIG_PSTORE_PMSG=y
CONFIG_PSTORE_PMSG_SSPLOG=y
CONFIG_PSTORE_RAM=y
- Check the `ramoops` configuration:
Code:
./sys/module/ramoops/parameters/console_size 262144
./sys/module/ramoops/parameters/dump_oops 1
./sys/module/ramoops/parameters/ecc 0
./sys/module/ramoops/parameters/ftrace_size 262144
./sys/module/ramoops/parameters/mem_address 3241148416
./sys/module/ramoops/parameters/mem_size 1048576
./sys/module/ramoops/parameters/mem_type 0
./sys/module/ramoops/parameters/pmsg_size 262144
./sys/module/ramoops/parameters/record_size 262144
`pstore` setup looks fine but when I am trying the get logs from `sys/fs/pstore` then I found nothing.
I have tried it by two ways:
1. Crash manually with panic kernel using:
Code:
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
Followed Reading Kernel Logs
2. Flashing non-working rom that cause a boot loop and then flashed a working ROM with rooting steps and checked the file at `sys/fs/pstore`.
I need a favor in:
- Any steps to fix/debug the `pstore` problem?
- Any other way to find the kernel logs?
Update 1: I get the logs from recovery but I am not able to identify the problem.
Logs link: https://drive.google.com/file/d/1b-XNmjpYvH-L8lY0xA0SYr7XcITVCrVS/view?usp=sharing
Description: In this video, I have done the following:
1. Displayed recovery logs before: The last recovery logs are ends with 8.
2. Rebooted the device with a recovery key combination. I have already wipe data partition before making this video.
3. The boot loop happens and in the next reboot, I have pressed the recovery key combination to open the recovery mode where logs that end with 9 displayed.
4. Then I have recorded `last_history`, `last_avc_message_recovery`, `last_log.9` and `last_kmsg.9`
5. `last_history` and `last_avc_message_recovery` looks unchanged(same as before boot loop).
6. Then, I just have tried to mount the system but that didn't work.
7. At last, I have just rebooted the system normally without any recovery key combination.
Some Highlighted logs of last_log.9
exec -f /system/bin/e2fsck -v -y /dev/block/bootdevice/by-name/cache
error: _do_exec: can't run '/system/bin/e2fsck'
(errno 13 : Permission denied)
/system/bin/e2fsck terminated by exit(255)
...
E:Can't read /cache/recovery/last_locale: No such file or directory
...
W:Failed to unmount /efs: Device or resource busy
can't unmount /efs - Device or resource busy
...
W:Failed to set brightness: Invalid argument
I:Screensaver disabled
Atomic Commit failed in DisableNonMainCrtcs
Atomic Commit failed, rc = 0
...
Reboot Recovery Cause is [[BootChecker]RebootRecoveryWithKey]
...
print_recovery_cause() : reboot_reason=[[BootChecker]RebootRecoveryWithKey]
...
[property list]
persist.audio.fluence.speaker=true
...
ro.vendor.build.security_patch=2018-08-05
Supported API: 3
I:/efs is already mounted
W:Failed to unmount /efs: Device or resource busy
check_selective_file:Can't unmount /efs - Device or resource busy
just_reboot_after_update = 1
should_wipe_cahcewipe_cache
-- Wiping cache...
erase_volume(/cache)
...
MDF_I: Completed reset MDF flag!
MDF_I: Completed initialized MDF for Recovery!
mke2fs 1.43.3 (04-Sep-2016)
Discarding device blocksL 4096/153600??????????????????????????????done
Discard takes 0.00051s
Creating filesystem with 153600 4k blocks and 38400 inodes
...
Creating journal (2048 blocks): done
...
copy_logs
...
Cache wipe complete
[Checking pre-multi-csc2]
[start failed section]
sales_code=VZW
Carrier ID=[XAA]
[system partition space check]
The device has /product partition.
[out-recovery]
I:system root image is true, so need to change the unmount point from /system to /system_root
running out-recovery time : 0.000s
running recovery time: 1.738s
copy_avc_msg_to_data(1, )
I:fs_type "ext4" for /cache
copy_file 'proc/avc_msg' 'cache/recovery/last_avc_msg_recovery'
!__RECOVERY_FOR_ASSAMBLY
b_del_recovery_command = true
Rebooting...
## finish_recovery_terminate(del=1, reboot_cmd=reboot, clear_BCB=1)
## finish_recovery(delcmd=1,...
I:Saving locale "en-US"
I:fs_type "ext4" for /cache
I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vm-linux
I:## unlink /cache/recovery/command
copy_logs
I:fs_type "ext4" for /cache
copy_log_file :: create recovery log file '/cache/recovery/log'
copy_log_file :: create recovery log file '/cache/recovery/last_log'
Click to expand...
Click to collapse
Is anyone have experience in detecting problems from the kernel logs?
i can not help you, but we can collect ideas. what about re-sign the system.img? there is a key somewhere, i guess just deleting won't work but maybe it is possible to calculate checksum
or maybe you can switch to SuperSU 2.79 SR3 (latest release from chainfire) or at least look inside the update-binary shell script how to root system.
regarding dm-verity i would start with searching for "verify" flag in your fstabs and remove it. magisk is also doing some hex patches and re-signing, it's the best source to look inside magisk installer zip update-binary/ updater-script, if you have the knowledge to read code
another option is try to port a twrp recovery from another snapdragon (i wonder if somebody did this already) if you can find a porting guide
so the vzw s10 5g is unlockable?
elliwigy said:
so the vzw s10 5g is unlockable?
Click to expand...
Click to collapse
yes
aIecxs said:
yes
Click to expand...
Click to collapse
Figures lol.. I have a g975u from big red n don't plan on buying another lol
aIecxs said:
yes
Click to expand...
Click to collapse
Message me on telegram and I can help you if you help me.. I'm curious in some logs and what not.. I also might have something you can use..
Did you get it working? I have the same phone and I want to use the 600mgz tmobile 5g in a few days, so I need the right rom.
elliwigy said:
so the vzw s10 5g is unlockable?
Click to expand...
Click to collapse
aIecxs said:
yes
Click to expand...
Click to collapse
Snapdragon bootloader unlockable? How?
I'm a VZW customer and can get the phone on an upgrade, but want to root it...
i got a g977p and twrp n magisk working great
do you think it is possible to flash other branding on verizon devices with modded odin?
aIecxs said:
do you think it is possible to flash other branding on verizon devices with modded odin?
Click to expand...
Click to collapse
dunno.. its not possible on n976v..
Was there any luck on rooting the Verizon G977U?
@Vats12 has already successful rooted with magisk in recovery. this thread is for rooting system (kind of rooting where su binary is placed in /system/xbin like for older devices, which breaks OTA)
aIecxs said:
@Vats12 has already successful rooted with magisk in recovery. this thread is for rooting system (kind of rooting where su binary is placed in /system/xbin like for older devices, which breaks OTA)
Click to expand...
Click to collapse
So you want like the supersu method?
ExtremeGrief said:
So you want like the supersu method?
Click to expand...
Click to collapse
Yes, do you know how to do this?
Magisk (guide) does a lot of other things too..
Maybe we can use Magisk to disable the securities and then SuperSu can help in the rooting system?
Vats12 said:
Yes, do you know how to do this?
Magisk (guide) does a lot of other things too..
Maybe we can use Magisk to disable the securities and then SuperSu can help in the rooting system?
Click to expand...
Click to collapse
But why? Safetynet will be gone
What model is the device?
ExtremeGrief said:
But why? Safetynet will be gone
What model is the device?
Click to expand...
Click to collapse
model see OP! i guess because of the buttons needed for booting in magiskrecovery, but the reason is not important only HOW (for Vats12, not for me i don't own this device)
Sorry but this thread needs to be closed
aIecxs said:
model see OP! i guess because of the buttons needed for booting in magiskrecovery, but the reason is not important only HOW (for Vats12, not for me i don't own this device)
Click to expand...
Click to collapse
I don't want to be the one who shouts fake, but the instructions you gave a link to says you have to be able to flash a bootloader first, which means an unlocked blootloader, if you have Verizon rom this is not possible, as the blootloader is locked.
If you did find a way to flash a modified bootloader, or a modified recovery those are the instructions we need, because in fastboot you are unable to do this with a locked bootloader and you are unable to unlock the bootloader on Verizon. If you have a modified bootloader or recovery flashed on your device what did you use to flash it with Odin? Because only way to flash a boot.img is either get into download mode and flash with Odin, or with Edl, if you got into edl mode then can you provide instructions on that, because we would like to know how to get the device into EDL mode as well
Sorry boys this is a hoax.
@DroidisLINUX there is video proof in OP, and again for you:
This is not a tutorial about unlocking and rooting, it is a question how he can modify /system to permanently integrate su