So I followed a guide (can't post links but basically I installed Busybox and Terminal Emulator, then used
Code:
dd if=/sdcard/backups/logo.bin of=/dev/block/mmcblk0p11
) to modify the Android boot logo. I made a backup of the logo on my PC, then proceeded to replace the system file. Then I rebooted. Now, logo isn't updated and after the logo it switches to boot animation but is just stuck there. So I install ADB and boot into recovery mode but I can't do anything there because my device is missing an "enter" button. So using ADB, I replace the original backed up file with the system one with
Code:
adb push logo.bin /dev/block/mmcblk0p11
. Now it won't even make it to boot animation, just stuck at starting logo. I can still connect using ADB though. Any way I can recover the device without a hard reset?
Related
Hi Guys.
I don't know if this is the right forum, please tell me if so.
I think that I've screwed up bigtime when i tired to upgrade my recovery image. Here is what happende.
I have rooted my Hero a long time ago, so what i did was trying to follow this guide for installing the latest recovery image: http://forum.xda-developers.com/showthread.php?t=645253
when i tired to flash the recovery image using this command: flash_image recovery /sdcard/recovery.img. I was using Terminal Emulator.
What happened was i got a lot of error messages saying that the phone was out of memory. This resulted in that i couldn't get acces to the recovery menu when rebooting my phone and that i cant access my phone rom.
I then tired to flash the recovery image using the installation guide of this thread: http://forum.xda-developers.com/showthread.php?t=561124
The thing is that i can see that the phone is mounted through the "fastboot devices" commando
When i try to flash the recovery image using fastboot i get this error message:
C:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.001s
HELP! What can i do? Is my hero 'saveable or is it bricked?
//Mads
First of all its not bricked don't worry. Do you still have old recovery of Amon_Ra or not ? If have than put latest version of Amon_Ra recovery into your sdcard & reboot your phone into old recovery of Amon_Ra Than just follow these commands
Code:
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
when its done just type adb reboot . your phone will reboot
Hope it helps
Hi, it's good to hear. I think that my old recovery mode was screwed up during the attempt to upgrade. because if i tries to boot into it it just stops at the HERO bootscreen and goes no futher. If i just try to boot normally it goes to a black screen and then nothing else happens. Tried to let it boot for 30 min without anything happening.
The only thing i can access is fastboot.
when i try adb shell it says the following:"
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
you need to update your drivers that means you are not having latest drivers .. there was a thread i guess download drivers & check how to set up correct adb drivers on windows .. & by the way do you have installed HTC Sync ? make sure you have installed HTC Sync because it finds all htc drivers i guess than try
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Thx for the help, but that didn't work either.
I found this guide http://forum.xda-developers.com/showthread.php?t=714519 which did the work. So now i'm back at 1.5 for a little while, just need to root right away The good thing is that my phone is working
Thx for the help.
Glad to hear it Men .. Well come abroad
Hi,
I just flashed Cyanogemod10 to my Artview AT9C-A10W (CEMA10N7 clone) (Allwinner A10) and tablet stuck on spinning Cyanogemod logo.
I tried recovery mode but stuck on spinning Cyanogemod logo.
I can connect with ADB but "ADB reboot recovery" doesn' work too.
ADB devices --> 20080411 device
ADB reboot --> reboots tablet but stuck on spinning logo.
ADB reboot recovery --> boot but stuck on spinning logo.
/mnt/extsd --> d--------- system system
/mnt/sdcard --> d--------- system system
and I'm unable to change them
su --> permission denied
fastboot devices --> no result
fastboot reboot --> waiting for devices (forever)
Any ideas?
Many thanks!!!!
Quote
MultiQuote
Edit
Report
I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Is there anyone who can help me?
mikewootc said:
I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Click to expand...
Click to collapse
Is there anyone who can help me?
I had try to upgrade firmware with my pc
Solo1977 said:
Dear sir, you should try to connect pc with you phone and upgrade firmware
Also you can modify phone settings, swap positions for flash memory and external sd card
Click to expand...
Click to collapse
First of all,
I have tried to connect pc with my phone by fastboot. And I have tried to flash the original version of recovery by using command:
fastboot flash recovery recovery.img
And it says success, but when I reboot the phone, it still boot into the old version recovery(which is 3rd party version).
Secendly,
I have tried to upgrade firmware from SD card, and it tell me success and no effect when reboot.
Is there anything I can do else?
HEllo everyone i have an S5 g900f. I recently flashed stocked rom in at after the custom rom crashed,but the phone is stucked at samsung logo and recovey mode is not working(using buttons).Is there any way to wipe cache without using recovery or any method to enter recovery
You can try via adb/terminal. Assuming the device has "USB Debugging" enabled, open terminal/cmd and type: adb reboot recovery.
If you have a working custom recovery placed somewhere, place it in the root folder where your adb is located, open terminal and type: adb reboot bootloader -this will boot your device into fastboot, then type:fastboot boot "name_of_your_custom_recovery.img"
If you do not know what you're doing, better not do it. Always create and take a backup.
Goodluck
Hi all,
I have a stock/non-rooted lenovo A7-50 A3500-F, for which I have downloaded the original firmware files (Lenovo_A3500-F_MT6582_A442_01_34_140904.zip).
I've unpacked and modified the boot.img, modified default.prop to set ro.debuggable=1, repacked, and flashed back to the device via fastboot:
- adb reboot bootloader
- fastboot flash boot boot-new.img
After rebooting, the device is stuck in a bootloop (the lenovo logo shows up for a while, then all blank, then again the logo, goes on forever).
The only thing I can do at this point, is to enter the stock recovery mode. Since adb is not available, I cannot find an external way to enter fastboot mode so that I could reflash boot.img (holding the power button and vol-up keys doesn't do anything - bootloop goes on).
So I am looking for a way to reflash the original boot.img somehow. While in recovery, the only thing that appears to be available is adb sideload, and the recovery option "apply update from adb" (or sdcard). I've tried to generate a signed zipfile that should update boot.img with the expected structure (followed some instructions and tried out f-zip, but it doesn't work (the recovery screen after adb sideload uploads the file shows "Error." and no other info).
If you have any suggestions or other ideas on how to restore the original boot.img it would be most appreciated.
Thanks!