Hi,
My company bought four Samsung Galaxy A30s (SM-A307FN) phones to be used in a project, where we need remote control and access to the phone and it's camera. So far, everything is looking dandy, however we're missing a critical feature. If the phones runs out of battery, we want it to boot when power has come back again. It's a critical feature, because the phones will be installed in places not easy to reach.
I therefore started looking into getting root access. I used this approach https:// www .recovery-mode. com/ root/ root-samsung-galaxy-a30s-magisk-root-without-twrp. html rooting without twrp and rooting seems succesful. However - the phone periodically toggles airplane-mode - and connection to the carrier cannot be reached. Does anyone have similar issues - or solutions or ideas as to how I can fix it?
If I boot with no root (disable recovery mode) the connectivity comes back, and the phone behaves normally.
I regards to the boot on charge, I've tried different things with the lpm file. I always end up being stuck with the charge symbol in a circle, and I have to reboot with power+vol-up+vol-down.
I tried this:
Google search: Root Samsung Galaxy A30s ( Magisk Root ) without TWRP recovery mode
(i cannot post link since I'm a new user)
and this:
Google search: Auto-starting Samsung Android phone when charger is plugged in. (mediumdotcom)
Lastly I looked into this thread:
Google search: lpm-reboot-samsung-galaxy-s7
but when I try to remount /system with read-write, I get an error message saying " '/system' not in /proc/mounts" .
Also if I try to get root access through adb it tells me "adbd cannot run as root in production builds".
Any help would be appreciated.
/Lasse
Allright, I got this far:
Managed to get the LPM file changed and get the phone to boot on charge.
After rooting successfully (although airplane-mode / Flight-mode keep toggling) I got access to the lpm file.
first, I entered shell
Code:
adb shell
then I gained superuser access:
Code:
su
I had to change read/write mode for the system-directory. I couldn't use "remount -o rw,remount /system" - as it told me that it wasn't part of /proc/mounts/.
I found a thread saying to remount the root directory " / " instead - that worked:
Code:
mount -o rw,remount /
Great - now all I had to do, was to change the contents of the lpm file. Making a new lpm file didn't work - apparently the lpm file has a unique inode value - that the system uses to identify the file, and making a new file, creates a new inode number. So I had to use the original file. I was sceptical about this, because I didn't want to brick the phone, so I made a copy of the lpm contents in order to go back to normal - if it didn't work. I copied the contents to a new file called lpm.orig using cat:
Code:
cat system/bin/lpm > system/bin/lpm.orig
So now i had to insert new text in the original lpm file. I made a script with the following contents:
Code:
#!/system/bin/sh
sleep 30
/system/bin/reboot
and called it lpm-script - the 30 sec sleep period is because I want to make sure the power is back, before booting the phone.
Now all I had to do is to cat the contents of lpm-script into lpm:
Code:
cat system/bin/lpm-script > system/bin/lpm
I rebooted in system mode (not recovery), so I once again had cellular connection, powered the phone off, plugged the usb in, and waited - and success... it worked. Originally I had a 5 second sleep period, but it stille took around 20 sec for the phone to boot - so be a little patient before turning the phone on manually.
So my next issue is the flight-mode toggl. If I managed to get this solved, I hope I'll be able to use the phone with root access all the time, but for now, my initial goal is completed: Boot samsung galaxy a30s on charge.
Let me now if anyone else gets it to work.
/Lasse
Labild said:
Hi,
My company bought four Samsung Galaxy A30s (SM-A307FN) phones to be used in a project, where we need remote control and access to the phone and it's camera. So far, everything is looking dandy, however we're missing a critical feature. If the phones runs out of battery, we want it to boot when power has come back again. It's a critical feature, because the phones will be installed in places not easy to reach.
I therefore started looking into getting root access. I used this approach https:// www .recovery-mode. com/ root/ root-samsung-galaxy-a30s-magisk-root-without-twrp. html rooting without twrp and rooting seems succesful. However - the phone periodically toggles airplane-mode - and connection to the carrier cannot be reached. Does anyone have similar issues - or solutions or ideas as to how I can fix it?
If I boot with no root (disable recovery mode) the connectivity comes back, and the phone behaves normally.
I regards to the boot on charge, I've tried different things with the lpm file. I always end up being stuck with the charge symbol in a circle, and I have to reboot with power+vol-up+vol-down.
I tried this:
Google search: Root Samsung Galaxy A30s ( Magisk Root ) without TWRP recovery mode
(i cannot post link since I'm a new user)
and this:
Google search: Auto-starting Samsung Android phone when charger is plugged in. (mediumdotcom)
Lastly I looked into this thread:
Google search: lpm-reboot-samsung-galaxy-s7
but when I try to remount /system with read-write, I get an error message saying " '/system' not in /proc/mounts" .
Also if I try to get root access through adb it tells me "adbd cannot run as root in production builds".
Any help would be appreciated.
/Lasse
Click to expand...
Click to collapse
airplane mode
Hi,
I'm stuck with the airplane mode toggling on and off after rooting with magisk. I've tried to re-flash the phone, but it seems to be the same issue, although the root procedure had no errors or no warnings. Root access works.
Is there anyway to permanently disable airplane mode? Other than pushing the on/off switch.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help or suggestions would be appreciated.
/Lasse
Hey, did you find how to solve this problem? i also have it
Related
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
ADB FIX
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Installed Wrong Preloader?
Luckily for us we can just open Sp Flash Tool with the correct files then push and hold the Power + Vol Up with the usb connected. After approximately 30seconds it should allow flashing.
jeffmoss1999 said:
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Click to expand...
Click to collapse
Is your device still working?
leetree2001 said:
Is your device still working?
Click to expand...
Click to collapse
Yes. So far I have found it's hard to kill this unit. I don't have the original firmware but have it working with this firmware where it is usable. Like I stated the worst thing is the screen rotation but all u have to do is lock rotation and it's fine.
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
leetree2001 said:
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
Click to expand...
Click to collapse
This is not for the w22B just the w22.
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
I have the 22B version also
leetree2001 said:
understand your warning. But had these under the coach
for about a year. And nothing else has poped up on the
old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
did this work????
Did it work?
leetree2001 said:
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
Im having the same issue looking for a rom for my Voyager 2
Did that sulution work for the w22b version?
Yay my tablet is bricked. Thanks SP flash. frickin crashed
My tablet no longer turns on after I tried SPFlashTools, it started DL process and then timed out. If I connect to windows computer, it makes a connect sound but does not do anything, neither responds to SPFlashTools anymore. Any Idea ?
jeffmoss1999 said:
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
Click to expand...
Click to collapse
What version is this Android OS?
Also: I can't have access to wifi.rar fix file. Where is it?
I am also looking around for stock rom RCT6773W22 (no additional letters or numbers)
I've installed all possible drivers for this tablet.
I physically inspected the USB charging port was not bent and (internally at circuit level) everything is connected, nothing is loose.
When the tablet is off, the device is not seen. But the screen of the tablet shows it is charging from the PC normally.
Windows 10, then proceeds to chime "device disconnected" sound.
If I turn on the tablet, I ask for ADB DEVICES and the tablet is not recognized at all. The tablet stays at logo boot loop.
Maybe I need to install something so the hardware of the tablet grants access to adb commands?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in brief:
the data should be there on the phone, so there's hope it should be easier to recover than deleted data but i run out of ideas how to get adb to find and pull it... maybe a more advanced user has better knowledge (better commands or tools)
adb devices and fastboot devices communicate with phone, so i have all drivers installed, i can only tackle with it via usb from windows 7 based computer
the detailed story:
i have a huawei g620s-L01, stuck in bootloop (just loading huawei logo forever or until battery empty but does not restart) and also "volume down" button does nothing... the bootloader is locked and huawei seems to have stopped providing unlock codes...the touch works but is shattered so i was told repair the button is not an option...
i can boot it into recovery mode using "volume up + power" but i can't use the recovery menu due to the dead "volume down"
from recovery menu i can only "reboot system now" but that re-enters the bootloop,
also i get bootloop if i try to boot into download mode via adb command
i can use some adb commands (i say some because some return errors, others say i don't have permissions)
i can boot into fastboot via adb command too...i can not find my dcim folder or any data folder to use the pull commnad, i tried the generic commands to pull sdcrd or dcim or all files with *.jpg
the user data is not accesible, i could browse some system directories but they did not contain my files via cd commands
i found some threads saying maybe i need mount or root commands
but trying to mount partitions or access su via adb also gives errors
su is not found, i do remember there was a su when android was working on the devices but is useless if i can't find/access it
i found the factory rom and some tools to try to restore rom to the phone due to claims that same rom might find my data, but the tools failed to start due to locked bootloader
i also tried several versions of full android sdk (old and new) trying to find "monitor or file browser" tools but the menu is not there...perhaps it will not activate those tools when device is in fastboot/recovery modes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i also found a 3rd party full android browser but can't connect with it either
also recovery softs are useless, they need a working android to try to recover anything...some recovery softs claimed they can fix bootloop but don't support my device
free tools that try to unlock bootloader also failed
so at this point i am running out of things to try
this is what i figured so far: i can see my data but can't touch it
i seem to have 4 partitions on the device:
1 is called sdcard but has nothing accesible on it, could be the feature for external card
2 is called ext , total size is 711,49mb , used 124,98 and available 586,5
3 is called system , total size 1,64 gb, used 1,23gb, available 418,1mb
4 is called data, total size 3,96gb, used 3,75gb, available 218,16mb
clearly the data partition is still keeping my data
i can not see my installed apps, so i guess they are also on that partition
i can see some system apps, namely 49 out of 146
so i'm guessing the issue is with one application, likely system app since i can't see them all
the phone may be partly rooted, the android may have some rooted features but the adb on it is not rooted
so i can not use the adb root command to get to my data
and i can not try to flash recovery or rom or custom boot img from adb due to bootloader locked and asking for unknown code
Spoiler: Phone Data:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted
Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.
Hello, I'm new to this- all of it, I've only just recently got into rooting and such things, but I'm progressing and that's what matters, no?
Anyway, I've successfully managed to root this phone via Magisk, that no one probably cares for anymore through trial and error and I'll do my very best to explain my method, and give updates as this is very on-going, there are certain issues and things I need to work out, but I appreciate any help, pointers, and such as before mentioned, I am new.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ALCATEL A30 FIERCE - Specs, and Specifications.
This phone was released in August, 2017.
Display - 5.5inches, 1280 x 720
Camera - 13 MP (Single Camera)
Hardware - MediaTek, 2GB RAM
Storage - 32GB, microSDXC
Battery - 3000mAh
OS - Android 7.0 Nougat
My own notes about this device.
Lots of MetroPCS Bloatware, can be a bit janky, but it's manageable.
It does not have a traditionally accessed Bootloader, no "adb reboot bootloader", this command just restarts the device to system.
Fastboot is odd, I managed to access Fastboot by some way I don't entirely understand, I'll go about what I did to get there later on in this post and try to recreate it later on as this post updates.
This device has colour states (if that's commonology), meaning, once the Bootloader is "unlocked", you will get an "Orange State" message before starting your phone that gets in the way of some things, I have yet to fix this, but I imagine we will if this gains traction, there will be a quicker fix!
No TWRP yet, as of posting, flashing a ported twrp.img through MTK_TWRP, or the TWRP_Port has not worked, and after flashing, neither will flashing the stock recovery but I've a quickfire way of getting around to fix this, if I can.
MTKCLIENT - https://github.com/bkerler/mtkclient
My Process, in the system, press the build number seven times to enable developer options - enable OEM Unlocking.
Then enable USB Debugging, and make sure you've installed adb and fastboot, as well as the correct drivers.
Through that link, follow the instructions specific to your operating system (I use POP OS and WINDOWS 11, YOU DON'T HAVE TO USE THE SAME AS ME), you may use the mtkclient_gui for an easier experience.
To unlock the bootloader, which will trigger "Orange State", open your terminal in the directory of the mtkclient and run python "mtk e metadata,userdata,md_udc", then, with your powered off device, and it will say something along the lines of "Preloader - Waiting for Device", with your USB Cable, and your wits about you, hold the volume down button (if this doesn't work for you, hold both volume buttons in" and plug your device into your PC with that command running. If the command completes, then run "python mtk da seccfg unlock", and this will unlock your bootloader.
WARNING: Unlocking the bootloader wipes the data of your device!
After this, dump your boot vbmeta with the commands in the mtkclient instructions, if this does not work for you with python or python3, I will provide the required files below.
Then, power your device back up, and install the patched magisk-app and push it to your sd card through adb, or traditional file transfer.
If you have your boot.img, push it to your sd card and patch it with magisk, then retrieve it from your phone - this is where my tutorial and mtk's tutorial take a bit of a turn!
I had a problem with the "reconnecting to preloader" phase, as it would not go through, or an error labeled [Unpack Requires A Buffer Of 12 Bytes] would crop up which prevented me from flashing the required files through "python mtk w boot,vbmeta boot.patched,vbmeta.img.empty". Let's go through some cautionary steps, what I did to achieve perma-root.
Create a funny-named file in the mtkclient directory labeled "DUMPY", do "python/python3 mtk_gui" and connect your powered off phone through the previously mentioned volume holding until it connects you in BROM mode. Under "read partitions", select all partitions, then "read partitions" and make sure the output is that "DUMPY" folder. This process will take awhile!
Once it finishes, rename your patched magisk-boot from [magisk.img name] to "boot.patched.bin" and under "write partitions", select the boot partition and write the boot.patched.bin to the boot partition! Once finished, start your device and install a root checker! It should be working!
If there are any errors, I will do my best to try and help you but keep in mind, I am very new to this, I hope it works for you too!
hi, i have a s10e (sm-g970f) im a noob btw plz hlep
last night it was working fine but now when i turned on the phone it started bootlooping on the lock screen (boot animation shows before i can do anything)
ive already tried booting into safe mode, remove lock screen, power off, waiting, remove sd card/sim card but the loop still continues
its rooted with magisk 25.2 on pixel experience plus (android 13) with twrp 3.7.0_9-1
bootloader is unlocked
before ive flashed disable dm verity and force encrypt thing so its not encrypted
magisk modules:
systemless hosts
magiskhide props config
universal safetynet fix
shamiko
substratum
pixelify
lsposed
pixel 6 pro (raven) props
is there a way to fix this without wiping data/apps bc ive already done that like 20 times and its annoying
theres a last_kmsg log attached idk if its important
someone help
thanks
edit: kmsg log not uplaoding
video of bootloop imgur.com/a/y9NXjNn
why you have done this 20 times?
first, twrp backup /data and copy files to PC. next, try to boot magisk core only.
Code:
adb pull -a /sdcard
adb shell touch /cache/.disable_magisk
no luck, same bootloop is still there
get logcat from boot-loop and share via pastebin.com maybe there is hint for cause
how do i do that?
when i try to get logcat from adb its stuck on - waiting for device -
I was assuming you already enabled usb-debugging and authorized adb previously.
However, you can enable from TWRP. you can place adbkey.pub directly.
- find the %UserProfile%\.android\adbkey.pub file
- use the little shell script (you can view as text file and have a look into what it actually does)
- copy in TWRP
Code:
adb push adbkey.pub /cache
adb push adbguard.sh /data/adb/service.d
adb shell
cd /cache
rm .disable_magisk
cat adbkey.pub >> /data/misc/adb/adb_keys
chmod 0755 /data/adb/service.d/adbguard.sh
- now reboot and try again adb logcat
- if it works, reboot one more time and redirect logcat to text file
Code:
adb logcat > logcat.log
ive enabled usb debugging,
ive also tried modifying boot.img from this thread (https://forum.xda-developers.com/t/how-to-logcat-when-bootloop.3490228)
im pretty sure twrp is decrypted how do i place adbkey thing
logcat file too big for pastebin
logcat
edit: text file didnt upload so i put in zip
edit 2: lots of errors and stuff
edit 3: aaaaaaaaaaaaa
20000 lines... well no clue where to start. will have a look into tomorrow. just a quick look in begin of log there is something wrong with keystore. how did you remove lock screen?
also only guesswork, but maybe try to disable zygisk (have to figure out) as I can see some related errors. maybe related to bootanimation crash.
Code:
E Zygote : Zygote failed to write to system_server FD: Connection refused
can you adb pull /data/adb/magisk.db?
hmm alright
i removed lock screen by looking in some xda forums deleting some lock screen files, hopefully it wasnt bad :/
(i removed lock screen after bootloop started)
aIecxs said:
can you adb pull /data/adb/magisk.db?
Click to expand...
Click to collapse
here
okay I don't know if there is easier way, but you can modify magisk.db and disable zygisk. TWRP should have sqlite3 binary in path already, so just skip first three lines and the /cache/ prefix.
(only in case it's missing)
New SQLite3 Binary v3.42.0 for ALL devices
I built the latest stable SQLite3 binary for ARM devices. I built it as I have an app that I requires it, and distribute it with my app TeMeFI , as a lot of people asked to not have to install it as a separate step. TeMeFI app does a LOOOOOT of...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
adb push sqlite3 /cache
adb shell
chmod 0755 /cache/sqlite3
/cache/sqlite3 /data/adb/magisk.db '.mode column' '.headers on' 'select * from settings'
/cache/sqlite3 /data/adb/magisk.db "UPDATE settings SET value = 0 WHERE key = 'zygisk'"
/cache/sqlite3 /data/adb/magisk.db '.mode column' '.headers on' 'select * from settings'
Don't know if that circumvent anything, that's just trial and error. But you can undo by SET value = 0 any time.
uh how do i get sqlite thing working?
it says /sbin/sh: /cache/sqlite3: No such file or directory
im total noob
lol
edit: ill try do other stuff tmrw ima go sleep
inside twrp 'adb shell' just type 'sqlite3' instead '/cache/sqlite3'
(I had sleep for 8 hours right before now see you tomorrow)
ok i tried disabling zygisk but it doesnt work
that day i turned on airplane mode and turned off phone, idk if thats causing problems
anyways back to sleep
the log is full with errors, it will probably take more time to fix than start from scratch and restore backup. you can however use logcat-colorize to make it readable.
I can help extracting data.f2fs.win files and restore apps data manually, in case you are interested.
Hmm ok
I have this old twrp backup with Google authenticator on it but I just can't seem to restore it
The other apps/stuff on the phone isn't as important
If I try to fix the bootloop, it will probably take too long
you have TWRP so make backup now #2
ive made a backup, but:
i have this half backup that the really noob past me decided to cancel, i dont know if its still needed
and this ab file that was made when i did smt like adb backup --twrp so its like a twrp backup, but its an adb backup
ill try and usethis https://github.com/TeamWin/Team-Win-Recovery-Project/issues/898#issuecomment-1062793000
ok now i have these files
ok now restoring