How to fix bootloop in android 4.3 infotainment device - General Questions and Answers

I accidentally flash and overwrite settings.jar and settings.odex in system framework that causes the bootloop.

Re-flash Stock ROM.

jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
How to reflash stock rom? I tried to boot in to recovery mode but it did not show up the recovery menu.

iluvtorock26 said:
How to reflash stock rom? I tried to boot in to recovery mode but it did not show up the recovery menu.
Click to expand...
Click to collapse
Re-flashing Stock ROM typicaly is done by tools provided by OEM/Carrier or by ADB Sideload method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>

jwoegerbauer said:
Re-flashing Stock ROM typicaly is done by tools provided by OEM/Carrier or by ADB Sideload method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.ZIP>
Click to expand...
Click to collapse
same as recovery mode, sideload also not accessible.

iluvtorock26 said:
same as recovery mode, sideload also not accessible.
Click to expand...
Click to collapse
How did you verify this?
BTW: With Android 4.3.1 ADB Sideload was introduced.

jwoegerbauer said:
How did you verify this?
BTW: With Android 4.3.1 ADB Sideload was introduced.
Click to expand...
Click to collapse
the device just keeps on rebooting, there's no menu or any ui that will display except for logo in boot screen..
and when I tried to sideload the app it says adbre-KitKat sideload connection failed: closed

What happens when you enter these
Code:
adb devices
adb get-state
adb reboot fastboot
adb get-state
fastboot flashall <STOCK-ROM.ZIP>
commands - preferredly stored in a Windows batch-file?

jwoegerbauer said:
What happens when you enter these
Code:
adb devices
adb get-state
adb reboot fastboot
adb get-state
fastboot flashall <STOCK-ROM.ZIP>
commands - preferredly stored in a Windows batch-file?
Click to expand...
Click to collapse
List of devices attached
0123456789ABCDEF device
device
error: no devices/emulators found
< waiting for any device >

Related

[Q] Official Stock image via "Fastboot"

Do I need a root device to flash Official Stock Firmware image via "Fastboot" and what is the Adb command to do that ?
xperia_88 said:
Do I need a root device to flash Official Stock Firmware image via "Fastboot" and what is the Adb command to do that ?
Click to expand...
Click to collapse
You need not root your device. Just unlock the bootloader before flashing.
Adb is just an Android Debugger command. Don't bother and search on this command.
Adb and fastboot drivers are the prerequisites for flashing
Detailed guide on flashing is here >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

When running adb shell getting the below error: no devices/emulators found

I am trying to flash/boot twrp and I get a blank screen. when I try adb shell
adb shell error: no devices/emulators found
[email protected]:/home/noah/Documents/platform-tools#
fastboot devices 8442e6e9 fastboot
[email protected]:/home/noah/Documents/platform-tools# adb devices
List of devices attached
I tried to update the driver but to no avail. Please help!!!
I have tried 3 different laptops..played with usb 3.0 and 2.0 but still no avail.
fastboot commands like fastboot flash recovery twrp are working
but when I try to boot twrp.img. there's a blank screen on the phone.
NOTE: I can't enable debug on usb as phone has been wiped clean.
NEED help please!!

G7 thinq keeps booting in fastboot

when i switch on my phone i get the warning as "your device software cannot be checked for corruption. lock the bootloader"
then after some seconds it returns to fastboot. please i need help.
Re-flash Stock ROM.
how do i re-flash stock rom
By means of ADB Sideload method
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE-NAME-HERE>

Fastboot command failed

Hello. I am new to rooting and I wanted to root my old Moto E3 power. But the problem is when I flash TWRP into the recovery it says OKAY and finished then when I try to enter recovery mode my phone just boots up the OS and TWRP is not installed. Please help. Thank you in advance.
Fastboot commands operate on phone's bootloader, not on Android OS as this ADB does.
jwoegerbauer said:
Fastboot commands operate on phone's bootloader, not on Android OS as this ADB does.
Click to expand...
Click to collapse
I know. What i wanted to say was when I do "fastboot flash recovery recovery.img" it just says OKAY and finished. As my phone's power button is broken I can't go directly into recovery from there what do I do?? and also thank you for replying.
Code:
adb devices
adb reboot recovery
jwoegerbauer said:
Code:
adb devices
adb reboot recovery
Click to expand...
Click to collapse
ok I did that now it says no command on the recovery and no TWRP. Now what?
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.

Dm verity corruption [SOLVED]

I was using a gsi image then I decided to go back to stock rom
I used after sales tools made for transsiom devices(infinix, Tecno,Itel)
After it flashed boot and recovery and on getting to super image it showed an error message 'sending failed' this file doesn't match with the one in the device
Now when I try to power on it tells me
Dm verity corrupted
I can't access fastboot nor recovery
If I press power button to continue it remains stuck on boot logo
Please this is urgent
The device is not mine
Re-flash Stock ROM using ADB Sideload method.
jwoegerbauer said:
Re-flash Stock ROM using ADB Sideload method.
Click to expand...
Click to collapse
Please how
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-NAME-OF-STOCK-ROM-ZIP-FILE>
adb reboot
jwoegerbauer said:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-NAME-OF-STOCK-ROM-ZIP-FILE>
adb reboot
Click to expand...
Click to collapse
Thanks
Will try it
I solved it by flashing empty vbmeta using
fastboot --disable-verity --disable verification flash vbmeta emptyvbmeta.img
Click to expand...
Click to collapse

Categories

Resources