...........reflash rom will reset your boot animation if you get stuck in a boot loop while making boot animations
plz delete this post i solve the problem i was having
public acess said:
...........reflash rom will reset your boot animation if you get stuck in a boot loop while making boot animations
plz delete this post i solve the problem i was having
Click to expand...
Click to collapse
well - as part of messing with your bootanimation.zip you probably should have saved the original as a backup, if you enter a bootloop you can just remove the new one and put the old one back.
that also helps.
Even if you just remove it, it will still boot. Just be a black screen for a while
Sent from my PG06100 using XDA App
I did a backup of the boot ani.zip but the problem I was having was that when I would boot it would start the boot animation then freeze an reboot the phone and I don't know the cammand line to delete the file from fastboot. So I reflashed the rom and it reset the bootani.zip file to stock
Sent from my PG06100 using XDA App
adb shell rm /system/customize/resource/bootanimation.zip
Sent from my PG06100 using XDA App
Dosent my phone have to be fully booted for me to use adb cmds because it wouldn't fully boot and can I replace cmd: adb shell with cmd: fastboot to get the same results and thank you for the information
Sent from my PG06100 using XDA App
public acess said:
Dosent my phone have to be fully booted for me to use adb cmds because it wouldn't fully boot and can I replace cmd: adb shell with cmd: fastboot to get the same results and thank you for the information
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
You can use adb commands while the phone is booting. Usually like 10 seconds after it powers on.
Or in recovery after you mount /system
Sent from my PG06100 using XDA App
Related
My atrix is unlocked. As i was flashing ken's Alien ROM something went wrong and now my phone will not boot past the Dual Core Technology Screen
Daking12794 said:
My atrix is unlocked. As i was flashing ken's Alien ROM something went wrong and now my phone will not boot past the Dual Core Technology Screen
Click to expand...
Click to collapse
just boot back into CWM, wipe everything (Dalvik, cache partition & format data), then re-install ROM, and retry booting.
i am unable to boot into anything besides fastboot and RSD
Then fastboot the gingerbread. Img files. Or rsd to the preunlocked sbf or id try fastboot -w that'll wipe everything
Sent from my MB860 using XDA Premium App
Whenever i try to RSD any sbf it says "Chipset type 53 is not supported" and i am unable to find the img files
Daking12794 said:
i am unable to boot into anything besides fastboot and RSD
Click to expand...
Click to collapse
If you can boot to the fastboot menu, you can get to the recovery menu... just volume down until you see Android recovery, then volume up to enter.
Sent from my MB860 using XDA Premium App
Daking12794 said:
Whenever i try to RSD any sbf it says "Chipset type 53 is not supported" and i am unable to find the img files
Click to expand...
Click to collapse
Im not home now but somewhere in dev section look for kens gingerbread beta 4 NOT alien. it'll take you to the briefmobile site to download. There are img files at bottom of the page
Sent from my MB860 using XDA Premium App
Swiftks said:
If you can boot to the fastboot menu, you can get to the recovery menu... just volume down until you see Android recovery, then volume up to enter.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
When I try to boot into Android Recovery it says
"Magic value mismatch:
%s
Critical failure: Unable to start kernel.
Failed to Launch Recovery (0x00000002)."
Daking12794 said:
When I try to boot into Android Recovery it says
"Magic value mismatch:
%s
Critical failure: Unable to start kernel.
Failed to Launch Recovery (0x00000002)."
Click to expand...
Click to collapse
Well, if you can boot into fastboot, you can fastboot install RomRacer's recovery. Then try.
Sent from my MB860 using XDA Premium App
Boot into fastboot. Connect to computer. Open. Command prompt and use fastboot to erase recovery, system, preinstall,system,boot, user data and cache. Then use fastboot to install the new rom racer recovery. Boot into recovery and install your rom.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Boot into fastboot. Connect to computer. Open. Command prompt and use fastboot to erase recovery, system, preinstall,system,boot, user data and cache. Then use fastboot to install the new rom racer recovery. Boot into recovery and install your rom.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're a life saver. I had the same problem, tried your method and it took care of the recovery problem. Thank you very much, man.
So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?
Grona said:
So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?
Click to expand...
Click to collapse
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium
phordych05 said:
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2
Grona said:
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.
comminus said:
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.
Click to expand...
Click to collapse
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2
Grona said:
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In your OP you stated:
Grona said:
...My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery...
Click to expand...
Click to collapse
So, hopefully you can still get there.
Kernel problems won't affect fastboot. Generally speaking, the only way you wont be able to get to fastboot is with bootloader corruption or hardware failure, neither of which sounds like your issue.
so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?
Grona said:
so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?
Click to expand...
Click to collapse
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4
comminus said:
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4
Click to expand...
Click to collapse
So after flashing the boot.img from the cm10.1 nightly I'm getting a garbled screen after the CM boot screen, any thoughts?
Sent from my One X using Tapatalk 2
Boot to recovery and wipe cache/dalvik. Reboot and try again. If that fails to resolve the issue, try flashing the entire cm10.1 nightly from recovery.
Sent from my Nexus 4
hi.
i had rooted my htc magic mytouch 3g and after period its unable to boot in recovery mood again.
im a computer technical support and a beginner with android.
and thanks for your help.
If you can boot into bootloader use fastboot to flash a new recovery, or if your os is still functional and the ROM youre using has the flash_image binary then you can do it through a terminal as well
Sent from my Nexus 4 using xda premium
no image
hi.
thanx alot for your help but when i turn in fast boot its tells :no image found, many times.
and this time its unable to normal boot. only in fastboot mode.
thanx again.
That no image is normal, its looking for factory ROM/test/etc on SD card
After it finishes scrolling through the text you would then make sure your in fastboot mode and flash the recovery here if needed or boot to the recovery. Then flash ROM
More info on fastboot here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
I wiped everything with no rom or backup on my device (d800 using cwm touch) I get a unauthorized mssg when I try adb devices while it bootloops& no device found when in adb sideload, I can't authorize it cause I can't get past the bootloop... Any ideas? Been reading all day/night...
I don't think anyone has gotten adb sideload working for our phone as far as I can tell, anyone know how to authorize adb from only recov or bootloop? Or if you could restore a recovery made using a diff recov?
Sent from my G2 using xda app-developers
Can you get into fastboot or download mode?
Sent from my Nexus 5 using Tapatalk
I get into download but then it says firmware update don't unplug usb n it says root in red at the bottom but it just hangs there at 0% ... And idk if fast boot works, the phone comes up unauthorized in adb.. Would fast boot still work with it not being authorized?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
How do you get into fastboot on this device anyway? I can only get to cwm recovery and a download mode that tries to download a firmware update every time I do..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Im unable to flash kdz since my build.prop is recognized as pixel XL. Also my TWRP bootloops into my ROM which the system UI FCs in the phone setup. Anyone had a similar problem?
Sent from my Nexus 5 using Tapatalk
You can replace the build.prop using adb commands from TWRP.
make sure system is mounted as writable in TWRP and on the computer do
Code:
adb pull /system/build.prop
Then make your needed changes. Then do
Code:
adb push build.prop /system/
and that will replace the one on the phone with the one you just edited.
me2151 said:
You can replace the build.prop using adb commands from TWRP.
make sure system is mounted as writable in TWRP and on the computer do
Code:
adb pull /system/build.prop
Then make your needed changes. Then do
Code:
adb push build.prop /system/
and that will replace the one on the phone with the one you just edited.
Click to expand...
Click to collapse
Thanks for the reply , TWRP doesn't stay on long enough to allow me to do a adb command. As soon is it starts it boots to rom.
Sent from my Nexus 5 using Tapatalk
Robert235 said:
Thanks for the reply , TWRP doesn't stay on long enough to allow me to do a adb command. As soon is it starts it boots to rom.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hmmmm... And you guys on TMO cant use fastboot flash commands can you?
Unfortunately I don't think so , when I try them it says Failed!
Sent from my Nexus 5 using Tapatalk
Robert235 said:
Unfortunately I don't think so , when I try them it says Failed!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What DLL are you using to flash on LGUP? It shouldn't matter what your Build.prop says since it can be fully corrupt and still work.
with the LGUP tool it didn't require a .ddl, however, the LG flash tool I used LGUPc.ddl extracted from the kdz but the setup failed.
when you boot up can you access device even tho its force closing at main screen
can you speak to the phone using adb commands while on the startup wizard?