Develop Bugs

Busybox?

Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help

It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.

do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?

A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry

Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/

LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.

GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.

Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)

jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'

GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.

GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.

I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?

i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?

Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.

ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.

mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?

same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.

hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now

watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.

ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!

[Help] problems with current ROM + trouble going back to stock Froyo or similar

Hello guys.
Once again I need your help.
Following my last thread:
http://forum.xda-developers.com/showthread.php?t=847320
(AKA "Help! no SD recognition, USB link doesn't work and no signal!")
After taking martijn_bakker's and ianmufc's advice regarding how to issue the correct command from fastboot:
- My phone regained sd functionality.
- My phone had proper signal again.
- BUT I still have USB issues, AND more:
I am currently running Cyanogenmod 6.1.1 for HTC Desire, and I have the following issues:
- When I try to go back to the stock Froyo, or anything that resembles it really (LeeDroid for example), my signal goes bananas: When I try to call anyone, it rings the person, then "ends" the call, only to bring it back again after a few seconds and then disconnect again.
I've also tried different radios (including the one LeeDroid recommended) to no avail.
So basically I cannot make calls with the original ROM.
- USB: When I connect my phone to my PC it charges it, BUT my PC doesn't recognize it, and I cannot transfer files between the SD card and the PC, or sync etc.
- I've got no Bluetooth! (Not sure if this is a Cyanogenmod issue or not though)
- Phone turns off when released from electricity charging (Doesn't happen with PC USB charging though).
The thing is I really didn't mind the original Froyo 2.2 ROM, infact I like it very much. I really like the HTC Sense features and the weather+clock widget with the animations.
The only reason I ever rooted my phone was to get apps2sd on it, so I don't keep running out of space when installing new apps. But I never even got that to work...
My question to you guys is how can I fix my current problems and have a properly working HTC Desire with a stock/custom Froyo ROM (that can make phone calls ) with apps2sd on it?
Thanks in advance!
Liran

First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk

Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
edit2: also you should try flashing a new radio that is known to work like 5.09.05.30_2 just to make sure this isn't also causing problems. It should be possible from a zip file using recovery.

_Dennis_ said:
First how have you been getting stock on your phone? Have you tried the ruu? If you are zip flashing have you wiped everything? Go to recovery wipe data/factory reset, wipe cache, advanced then wipe dalvik cache, back button, mounts then wipe everything except sd-card. Make sure you wipe sdext. Then try to flash.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
TBH I don't exactly know what RUU is. I've heard it before but I'm not sure exactly what it means.
When I said I flashed the stock Froyo I meant this: Official_FroYo_2.10.405.2
and I also tried LeeDrOiD_v2.2f_A2SD.
Regarding the wipes I've done everything you wrote above to no avail.

mortenmhp said:
Well as you still don't have usb-connectivity, it sounds like you need to continue on the usb-brick fix. You have issued the command, which let you use the sd-card again. Now you just need to write a new misc partition as described here:
http://forum.xda-developers.com/showthread.php?t=691639
Doing this should make your phone work like it used to, as this is the only thing that is not fixable by flashing another rom if you need some help on it, i might be able to help, but in short terms, you need to flash a misc image, which have the right values, as the one on your phone have been changed in some way. The image is provided in the thread.
edit: and for god's sake do not try to run a ruu, as flashing the misc image might require root, and you may not be able to regain root without usb-connectivity. Also an ruu does not overwrite the misc partition, so it won't help your problem.
Click to expand...
Click to collapse
Thanks mate I will try that.
One thing I forgot to mention though - My phone is S-ON.
I'm not sure if it used to be S-OFF or not though.
Does that make any difference or does it not matter?

Hum. I appologize I never had a USB brick (knock in wood) so I assumed his problem would be in the rom possibly something he did while fixing the USB brick.
Sent from my HTC Desire using Tapatalk

It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
edit:
dennis: np something else is wrong as well, but fixing the usb is very urgent, and the other problem should be fixable by running a ruu or simply flashing a new radio+rom afterwards.

mortenmhp said:
It does make a difference yes, but you doesn't need s-off for this. It would just make it a whole lot easier. But just get your CID like described in the thread and change the misc image to this. Then flash it like described
Click to expand...
Click to collapse
Will do!
I'll update when I'm done

liranh said:
Will do!
I'll update when I'm done
Click to expand...
Click to collapse
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?

Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data

liranh said:
A bit stuck... Here is what I've done:
1. Got the CID.
2. Got a hex editor. wrote the new CID instead of the one in the img file. Saved it.
3. I put the new img file and flash_image.zip in the /data on my sd card.
I Put the card in my phone, started my phone, opened Terminal Emulator and typed in "/data/flash_image misc /data/mtd0.img" (without the quotes of course). the phone said: "/data/flash_image: not found".
What am I doing wrong?
Click to expand...
Click to collapse
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.

Masdroid: Yes exactly apart from that he apparently didn't have the files on the sdcard root

MasDroid said:
Actually, should it not be like this:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
Reboot.
Click to expand...
Click to collapse
mortenmhp said:
Well you should not have a /data folder on your sd card it is a partition on the phone. In order to put it there, save the 2 files in the root of the sd-card and issue those commands in a terminal emulator:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
As written in the thread, you might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image) but try to do it without those
Then you should be able to run the command you specified in the previous post
Edit: and the reason you got the error before was of course, that your files was in /sdcard/data and not in /data
Click to expand...
Click to collapse
Using a file manager on my phone, I put both files on the root of my SD card.
I then issued the following commands using Terminal Emulator:
su
(granted)
cat /sdcard/flash_image > /data/flash_image
Phone says: /sdcard/flash_image: No such file or directory
I should mention that I took out the card and connected it to my PC again to confirm the files have actually gone onto the root of the SD card (and they have), put the SD card back in my phone, issued the same commands in Terminal Emulator and got the same message...
Any ideas?

Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.

mortenmhp said:
Sounds strange, just to make sure. You have unzipped the flash_image, so that it is not the flash_image.zip you have on you sd-card.
Also run "ls /sdcard" in terminal emulator to see a list of the files in the root and check, that it's there, and do not have a file extension. If it's there and the name is "flash_image" then it should work.
Click to expand...
Click to collapse
Mate you are spot on with your first sentence. Give me a minute

Haha nice one thought i could've made the same mistake

mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Yeah cause you know how when you put files on your phone to flash them you usually keep them in their zip format - that's what tricked me...

Haha yea let us know if you get it sorted

mortenmhp said:
Haha nice one thought i could've made the same mistake
Click to expand...
Click to collapse
Well spotted

mortenmhp and MasDroid thank you both so much!
Everything is working perfectly now!
I thought I would never get my phone to work properly again!
If any of you is ever in London - drinks are on me!

[ Q ] pushing system files thru adb

Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...

808phoneaddict said:
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
Click to expand...
Click to collapse
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#

JimSmith94 said:
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
Click to expand...
Click to collapse
Yeah I tried it didn't recognize su...I'll try again later

808phoneaddict said:
Yeah I tried it didn't recognize su...I'll try again later
Click to expand...
Click to collapse
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.

JimSmith94 said:
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
Click to expand...
Click to collapse
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?

If you have root installed and reboot to recovery, then "adb shell" should get you a # prompt.
If it does, then you're already ADB with root.
If you get $ prompt then you don't have root.
I don't think you can push system files without root?
You certainly can't "adb root" without root. That's for sure.

808phoneaddict said:
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
Click to expand...
Click to collapse
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.

JimSmith94 said:
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
Click to expand...
Click to collapse
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?

808phoneaddict said:
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
Click to expand...
Click to collapse
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.

JimSmith94 said:
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
Click to expand...
Click to collapse
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?

808phoneaddict said:
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
Click to expand...
Click to collapse
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!

JimSmith94 said:
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
Click to expand...
Click to collapse
O yeah I rooted, was rooted for a while but I ran into the data drain that others are reporting when there is an OTA update...knowing that December is upon us I was trying to unroot but push modified hosts file so I wouldn't get ads. Honestly, if it wasn't for the ads, I have no problem with a stock pixel xl...there hasn't been much development for it just yet, understandable since it's so new...

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