I'm stupid, please help. Stuck in bootloop - General Questions and Answers

I have been playing with some commands and wondered what would happen if I set a wrong screen resolution on my S7 Edge.
Code:
adb shell wm size 1080x1922
The answer is that you get stuck in a bootloop.
Now I'm wondering how to escape the bootloop.
Safe mode also bootloops.
Resetting it while booting didn't help:
Code:
adb shell wm size reset
Error type 2
android.util.AndroidException: Can't connect to window manager; is the system running?
at com.android.commands.wm.Wm.onRun(Wm.java:81)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.wm.Wm.main(Wm.java:46)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:316)
This script also didn't:
Code:
@ECHO off
adb wait-for-device
adb -d shell stop
adb shell wm size reset

GreeTech said:
I have been playing with some commands and wondered what would happen if I set a wrong screen resolution on my S7 Edge.
Code:
adb shell wm size 1080x1922
The answer is that you get stuck in a bootloop.
Now I'm wondering how to escape the bootloop.
Safe mode also bootloops.
Resetting it while booting didn't help:
Code:
adb shell wm size reset
Error type 2
android.util.AndroidException: Can't connect to window manager; is the system running?
at com.android.commands.wm.Wm.onRun(Wm.java:81)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.wm.Wm.main(Wm.java:46)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:316)
This script also didn't:
Code:
@ECHO off
adb wait-for-device
adb -d shell stop
adb shell wm size reset
Click to expand...
Click to collapse
Edit:
Apparently this script solved it:
Code:
@echo off
:loop
adb shell wm size reset
goto loop

Related

Urgent Help Required

I tried to root my Sensation XE using Tacoroot. I did the following steps :
Run the following adb commands.
Code:
adb push tacoroot.bin /data/local
adb shell chmod 755 /data/local/tacoroot.bin
adb shell /data/local/tacoroot.bin --setup
The phone will reboot to recovery.
Press Volume Up, Volume Down and Power.
Reboot.
Press the Power button once if the screen remains blank (dark).
Wait for boot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin --root
The phone will reboot.
Run Revolutionary.
Once Revolutionary is successful, reboot.
Run the following command.
Code:
adb shell /data/local/tacoroot.bin –undo
After this, The phone is in a bootloop. I tried removing Battery. It than boots till the homescreen, and after a few seconds goes into the bootloop.
Guys please help me out
EDIT:
SOLVED PLEASE CLOSE THREAD
SOLVED
it was the last command which was mentioned incorrect... it should read
adb shell /data/local/tacoroot.bin ––undo
instead of adb shell /data/local/tacoroot.bin –undo

The adb shell cd command doesn't change directories

When I use adb shell <cmd>, the commands work as expected, except for cd. If I run the following two commands, it shows I'm still in the root directory.
Code:
adb shell cd /any/valid/path
adb shell pwd
The cd command just doesn't ever change directories.
For completeness, I can not do abd shell ls ~/, as I have no HOME, but I assume this is normal?? I'm not concerned about HOME, it's fixable, but I really need to have the cd command working as I'm writing an IPython extension that wraps adb.
Cheers
Carl
I realise that this is a reply to an older question, but the answer might still be of use to some.
You first have to enter the shell before executing the 'cd' command.
STEP 1.
Code:
adb shell
STEP 2.
Code:
cd /any/valid/path
You don't use cd just type the directory you want to go to

[Q] Cant get kindle fire into fastboot

Ive been trying out pokey'9000 [fastboot] stock 6.2.1 fastboot mode without rooting or cables to get my kindle fire into fastboot, I typed in the"adb shell " command and get:
"[email protected]: $" so i guess adb is working I then follow the next step,
"adb push fbmode /data/local/tmp"
and get:
"942 KB/s (510876 bytes in 0.529s)" then:
"adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode"
but just after this final line I get:
"fail opening shift: No such file or directory"
My kindle is rooted and has superuser access already but I cant get it into fastboot mode, also tried:
" adb shell su -c 'idme bootmode 4002' "
and get :
" Reading idme data...
Setting bootmode to 4002
writing new vars to temp area
you must reboot before new values will take efect "
I reboot my kindle bust still cant get into fastboot. What could I possibly be doing wrong?

adb shell OK yet 'adb logcat -s ...' freezes at "--------- beginning of main"

Code:
adb shell ls
Is OK and lists files. adb devices sees the phone no problem too.
Yet:
Code:
adb logcat -s (any input)
freezes at 'beginning of main'.
For example:
Code:
>adb logcat -s dirtysanta
- waiting for device -
--------- beginning of system
--------- beginning of main
(no more output. tried for hours)
What can I try next? This doesn't really seem like a v20 problem but the xdadevs forum needs me to post here afaik.
edit: I think it was Mcafee, bundled by default and preventing run-as com. After a OTA update I managed to get a temp root prompt.
Is there someone I can pay to help me with this?

[HELP] Need help running command 'fastboot erase modemst1' on Pixel 5

After the March security update my Pixel 5 is not receiving any mobile network and i am not able to turn on radio power via the *#*#4636#*# command.
After googling for a solution i found similar posts which suggested resetting the modemst1 and 2 partitions
Tried running the following commands in adb but was unable to
Code:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
For fastboot I used the following commands
Code:
fastboot erase modemst1
fastboot erase modemst2
which gave me an error
Code:
FAILED (remote: Not allowed to erase (modemst1))
I'm also not able to boot into adb root but i am able to run adb shell su
I tried installing adbd insecure which was unable to patch adbd and also installed an adb_root module in magisk which still failed to initialize adb root
Currently I'm running ProtonOS on my Pixel 5. I thought running a custom rom might help but the problem still persists
Please help
Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.
ipdev said:
Hi.
I would suggest making a back up before you erase a partition in case you need to restore it.
Make sure to name the backup clearly so you know what it is.
Since you do not have adb root, you need to run the command as root using su -c "NameOfCommand".
If you boot into a custom recovery, you generally have adbd and do not need to use the su -c option.
Also double check your path, you should be able to call it from /dev/block/by-name.
or list by-name, ls -la /dev/block/by-name/ and call it from the true partition number.
Example of making a backup.
Dump the partition(s) into an image.
Code:
adb shell su -c "dd if=/dev/block/by-name/modemst1 of=/sdcard/redfin-modemst1.img"
adb shell su -c "dd if=/dev/block/by-name/modemst2 of=/sdcard/redfin-modemst2.img"
Copy the image(s) to computer.
Code:
adb pull /sdcard/redfin-modemst1.img
adb pull /sdcard/redfin-modemst2.img
Delete the image(s) from the device.
Code:
adb shell rm /sdcard/redfin-modemst1.img
adb shell rm /sdcard/redfin-modemst2.img
You need to be in fastbootd to modify critical partitions.
adb reboot bootloader will reboot into fastboot.
adb reboot fastboot will reboot into fastbootd.
You can do the same in fastboot/fastbootd
fastboot reboot bootloader will reboot into fastboot.
fastboot reboot fastboot will reboot into fastbootd.
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Good luck.
Cheers.
Click to expand...
Click to collapse
Hello, I hope you will see this text. As you have mentioned, I have rebooted my Pixel 5 to fastbootd but I cannot erase any critical partition. for example, when i run fastboot erase cache OR fastboot erase modemst1, i get the same error message saying FAILED (remote: 'Partition doesn't exist'). Would you mind helping me? I would appreciate it a lot. Thank you.

Categories

Resources