Develop Bugs

Help with removing max. frequence lock

Hello!
I flashed CM9 nightly on my GSM Galaxy Nexus a few days ago, and it has worked like a charm ever since. Until a few hours ago, that is...
I dug around in the CM-specific settings and (unfortunately!) ended up finding the Advanced settings, more specifically the CPU frequency setting. Just to see how it would handle things, I tried setting the max. frequency to 350 MHz (aka the default min. frequency). I was very surprised to see that the game Road Trip worked perfectly, and so I chose to keep it this way to save energy; I ticked "restore on boot". Later on, the phone rebooted during a phone call, but I thought, "oh, it's a nightly, this is to be expected."
What I noticed a few seconds thereafter (what is my real problem) is that the boot animation froze a few cycles in (after running at full fps for about one cycle), and the phone rebooted again, running into the same problem.
I still have this issue, even after factory resetting and reflashing the nightly (which I thought would remove the freq. "lock", but didn't).
Does anyone know how I can fix this? Is it as easy (or hard, because I can't access the actual system) as flashing some CPU-fixing ROM, or do I need to do something more, even send it to repair?
Thank you guys!

Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.

tingen said:
Go to revovry.
Go to Mounts and storage.
Format /system.
Format /cache.
Format /data.
Flash rom.
Flash Gapps.
Wipe data/factory reset.
Reboot.
Click to expand...
Click to collapse
Did that, but the problem persists.
Anything else I can try?

swefse said:
Did that, but the problem persists.
Anything else I can try?
Click to expand...
Click to collapse
You have to wipe the init.d file.. in there is the script that is locking your boot settings...

zapford said:
You have to wipe the init.d file.. in there is the script that is locking your boot settings...
Click to expand...
Click to collapse
How exactly do I do that? From some advanced menu in CWM or somewhere else?

Now I got some help over on Google+:
Adb remount
Adb shell
rm /system/etc/Init.d
Click to expand...
Click to collapse
but the last command gives me a no such file or directory...
Where in the system structure is init.d?

swefse said:
Now I got some help over on Google+:
but the last command gives me a no such file or directory...
Where in the system structure is init.d?
Click to expand...
Click to collapse
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
if it still gives you "file or folder not found"
'ls /system/etc/i*'
do you see /system/etc/init.d/ or not? if not, either your current rom hasn't created that folder yet (case of AOPK comes to mind, user had to create dir manually), or it doesn't support init.d scripts at all.

bk201doesntexist said:
'adb shell'
'su'
'rm -rf /system/etc/init.d/' - folder/file names in android (as in Linux) are case-sensitive.
Click to expand...
Click to collapse
'su' might have worked (it said
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
'rm -rf /system/etc/init.d/' returned
rm -rf /system/etc/init.d/
Click to expand...
Click to collapse
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?

Should be, give it a try.
BTW, booting a device is cpu intensive, hence the boot loops at low frequency

swefse said:
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
@ Tubes6al4v:
Nope, didn't work.
Btw, 'ls /system' returns
bin
Click to expand...
Click to collapse
Is that normal?

My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.

Tubes6al4v said:
My failsafe is to use fastboot to push a stock image over. Just keep in mind it will wipe your sd card.
Click to expand...
Click to collapse
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?

swefse said:
'su' might have worked (it said
'rm -rf /system/etc/init.d/' returned
Does this mean it worked, and that it is safe to reboot?
EDIT: Rebooted, problem persists...
Can I check to see if init.d is removed from adb?
Click to expand...
Click to collapse
if 'su' errors, then you don't have su binary installed. you wouldn't be able to delete /system/etc/init.d even if it was there. you should see a lot more stuff inside /system/ though.
swefse said:
So I'll follow this guide?
http://forum.xda-developers.com/showthread.php?t=1366806
Just one more n00b question: Can I pick whichever image I want, even though my phone came with 4.0.1?
If not, how do I know if it's ITL4D or ITL4F?
Click to expand...
Click to collapse
before you go restoring to stock, go in bootloader and try:
'./fastboot erase cache'
'./fastboot erase userdata'
see if it boots.
'adb logcat >> logcat.txt' would help debugging as to why the device is bootlooping as well.

Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310

swefse said:
Or is it easier to use this, and not have to worry about what version it is/was?
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
that's your choice. if you do use that toolkit (or any toolkit, for that matter), read instructions well.

I was redirected to this guide to get the fastboot drivers (and fastboot): http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
When I open "install-superboot-windows.bat", though, it says "waiting for device", and stops there.
Should I just have downloaded it and continued with the first guide (linked a few posts above), or should I have clicked "install-superboot-windows.bat"?
Edit: Now when I tried "install-superboot-windows" a second time, it rebooted the phone, but into Android (resulting in the usual freeze-reboot). I'm stuck, please help me!

Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?

swefse said:
Now I tried flashing MCR Ir9, which I had laying around on the internal memory, but it screwed up even worse: Now I don't even get past the first "Google" + unlocked boot loader icon screen.
Should I maybe just send it to Samsung, and foot the bill, before I brick it forever (if I haven't already, that is), or do you guys know what to do?
Click to expand...
Click to collapse
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.

bk201doesntexist said:
Pull batery, VOLUP+VOLDOWN+POWER into fastboot/bootloader. Reflash stock with fastboot.
Click to expand...
Click to collapse
I'll try that, and let you know how it works. Thank you!

Now it was successfully recovered and works again, thanks to fastboot and the wonderful convincing of you, bk201doesntexist!
Thank you!

Bypass Security Screen

I found my old GS3 which I had a lock screen but I can't remember the pattern I used. I tried doing the forget my password option but it's not recognizing that either. I there a way to unlock the phone without knowing the pattern?

Does it have a custom recovery? If not, flash one using Odin and then boot into recovery (power off then do VolUp+Power+Home) and run the following
Code:
adb shell rm /data/system/gesture.key
Source: Forgot my password once and had to figure this out :sly:

Is there a similar way to defeat a PIN on the lockscreen?

m20120 said:
Is there a similar way to defeat a PIN on the lockscreen?
Click to expand...
Click to collapse
adb shell rm /data/system/password.key

forgotten password

hi i have forgotten my pattern password.
i have a rooted verizon one with the latest cm11 snapshot.
su is not ebabled on apps and adb is only on apps.
tryed doing the command: adb shell
rm /data/system/gesture.key
but it says i dont have permisson i have notics i have a: $
instead of a #
tryed typing su and it didnt help
any suggestiones ?

UdiFlpb said:
hi i have forgotten my pattern password.
i have a rooted verizon one with the latest cm11 snapshot.
su is not ebabled on apps and adb is only on apps.
tryed doing the command: adb shell
rm /data/system/gesture.key
but it says i dont have permisson i have notics i have a: $
instead of a #
tryed typing su and it didnt help
any suggestiones ?
Click to expand...
Click to collapse
load the latest TWRP in fastboot and use the file manager to pull the file manually?

synisterwolf said:
load the latest TWRP in fastboot and use the file manager to pull the file manually?
Click to expand...
Click to collapse
lol just noticed there was a forgotten pattern button fixed the problem.
thanx anyway

UdiFlpb said:
lol just noticed there was a forgotten pattern button fixed the problem.
thanx anyway
Click to expand...
Click to collapse
Oh yeah, enter the google password to unlock. i forgot that was an option. Its been a while sense i used the pattern lock.
glad you figured it out thought. ^_^

Trouble Restoring Backed Up Stock ROM & WiFi Won't connect using LOS 15.1

Most of my the question/topic was explained here.
@steadfasterX
Re the WiFi pls share also the boot logs (see LOS faq).
Click to expand...
Click to collapse
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
Ok the choose "format" data in twrp and try to boot first without your userdata backup into stock. Lemme know if that works.
Click to expand...
Click to collapse
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?

emperordogma said:
Most of my the question/topic was explained here.
@steadfasterX
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
Click to expand...
Click to collapse
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?

steadfasterX said:
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
Click to expand...
Click to collapse
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found

emperordogma said:
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
Click to expand...
Click to collapse
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?

steadfasterX said:
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
Click to expand...
Click to collapse
Ahhhh, I assumed everything I saw was in a "copy/paste" format so, I didn't think to even try to exclude the adb from it.
I was able to mount system, and browse apps, there was stuff in there.
I used the "bs=512" method, and it gave the same result. I'm starting to think I'm just boned honestly. I'll upload my boot.img here in a few (in case you see this before I do).
I was hoping I could back up my texts/call logs (I was able to salvage a few, but I'm missing about a months worth), properly backup WhatsApp, get my Nova settings, and make sure I'm not missing anything else (I had a list, but can't think of it now). And I was hoping by doing it, it would fix the annoying Wifi bug.
Edit 1: I don't think it's "bootlooping", because I read that you could boot into TWRP while it's doing it (if your timing is good), I tried and couldn't get into TWRP at all, it's "stone walling" at the LG screen.
Edit 2: My stock Boot.img

ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd

steadfasterX said:
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
Click to expand...
Click to collapse
Huh, I am not sure how that happened. I'm starting to wonder if after the first try with adb push if I was even using my Stock Boot.img, magisk must've messed with me (they said the recommend way to to patch a boot.img) and I got them mixed up? Or at least that's the only thing I can think of.
Anyways, this should be the right one. Boot.img

@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).

emperordogma said:
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
Click to expand...
Click to collapse
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers

steadfasterX said:
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
Click to expand...
Click to collapse
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.

emperordogma said:
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
Click to expand...
Click to collapse
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right

steadfasterX said:
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
Click to expand...
Click to collapse
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".

emperordogma said:
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
Click to expand...
Click to collapse
Its just there by mistake. Not by LG but the OEMs. The OEMs like verizon, etc are not doing a good job but that's not new..

Question Help with bootloop after editing settings file

Hey folks,
Last night I was editing a file located under "data/system/users/0/settings_ssaid.xml" and upon rebooting my phone, it's been stuck in a boot loop. I have an original copy saved in a different folder, but unable to access anything to replace it.
Is there any specific fastboot command I can run to swap the files (adb push, pull etc)? Only boot slot A is giving me an issue, and I was reading flashing system.img would be able to help, but I don't wanna do anything I'm unsure will wipe any of my data where I'd have to start over unless I've recovered some of that data first.
If I do have to flash any stock images, pls post the instructions for clarity.
Thanks in advance.

Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
You can run the following command to list all the files in your specific folder.
adb shell ls FILEPATH
Every file in your specific folder will be listed. You can then do the following to pull/push your file
adb pull FILEPATH
adb push FILENAME FILEPATH
Of course you need to place the file that you want to push in your ADB folder.
Mind though, that simply replacing your edited file with the backup might not solve your bootloop.
You can always look up available commands here
adb shell ls - Android ADB Shell Commands Manual

Morgrain said:
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
Click to expand...
Click to collapse
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?

RetroTech07 said:
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
Click to expand...
Click to collapse
No because your file is on /data.
The issue is that you can't push your file to /scard since (I guess) you can't even get beyond to the point where /sdcard is mounted.
So copying it from /sdcard will likely be too late in the boot process.
Pushing directly into /data does not work either as you would have to be root. In the old days you could run and in root mode but I'm not sure that is still possible.
Factory reset will work.
On devices with separate recovery partition it would be possible to change recovery to allow adb access to /data so then push old file via recovery... But I would not know how to do that on Pixel as recovery is s part of the boot partition.

So effectively, it's likely you're only solution is to do a full firmware flash along with wipe.

I would first try a full flash removing the -w to avoid the wipe. It may work.

TonikJDK said:
I would first try a full flash adding the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.

Lughnasadh said:
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Click to expand...
Click to collapse
Thank you! My post is fixed.

TonikJDK said:
I would first try a full flash removing the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Obviously I'd be in fastboot / recovery mode, then perform a flash-all but remove the -w so as to not erase my data?
Once the system boots, all of my texts and setup should remain as is, or do I have to go and recover it?
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?

RetroTech07 said:
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
Click to expand...
Click to collapse
Nope ... there is only 1 data partition, so even when you flash the OS to the inactive slot, it would still use the same data partition. Moreover, it is then likely to upgrade/convert some files on /data which might result in not being able to go to the previous version in the old slot.

RetroTech07 said:
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/

so, unfortunately doing a full flash without wiping data didn't work. I'm almost inclined to believe that if TWRP was available for the P6/P, that I could go and push the file I had saved back into the directory of where it was and save myself from this mess.
I'm kicking myself because I'm usually backing up my data before I modify any system files, but this one time I hadn't done so and I had Google's backup turned off at the time, so I'm gonna have to lose some text messages over the last few days with some folks I enjoy speaking to. I do have some saved from late last week, but nothing from the weekend up until now.

As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.

DanielF50 said:
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
Click to expand...
Click to collapse
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.

RetroTech07 said:
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
Click to expand...
Click to collapse
Ah damn, I was too late!
The 90% thing sounds like the November Google Play services updated - mine updated yesterday and I got the same thing when I rebooted, maybe something between the two got corrupt.
Yeah, I get that, I've had more than my fair share of self inflicted (and not so self inflicted) problems that have lost me data but you live and you learn I suppose