So I'm trying to fix this phone for my friend and this was the information he gave me:
-tried to install a beta custom rom (forgot the name sorry)
-installed it but went haywire according to him
-he said he was able to get it back to stock
-tried rooting and installing another rom but thats where he messed up
The phone now only boots into recovery mode without pressing any buttons. If I pull the battery, it also just boots into recovery mode. I can't seem to get into download mode either.
Now heres the real problem. I am able to scroll up/down but I cannot select any of the options with the power button. So what can I do about this?
It says android system recovery <3e> and has some error messages related to mounting sd cards.
I had a problem when trying to root my phone.
I followed all the instructions exactly, but after flashing the kernel with Odin and XWKDD_insecure.tar, then the phone rebooted, it showed the yellow sign and then went on a loading loop (just keeps showing the samsung and carrier logo)
It didn´t reboot back into its OS as it was supposed to.
How do I fix this?
I can turn it off and it shows the recharge icon (when rechargin).
I tried putting into download mode and that does not work, i get a screen saying:
android system recovery (3e)
with 4 options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache partition
Also has a warning
# Manual Mode#
e:falied to mount /preload (no such file or directory)
e: install_application_for_customer: can´t mount/preload
You have to follow the instructions exactly . Do it again from the start .
I tried putting into download mode and that does not work, i get a screen saying:
android system recovery (3e)
PLEASE follow instruction you are putting the phone in recovery mode not download mode .
If a retry fails you will need to flash a new stock rom first .
http://forum.xda-developers.com/showthread.php?t=1075278
jje
Thanks for the quick reply
Problem is, when I used superoneclick the phone was in download mode, problem is now when I press volume+home+power it only goes to the mode android system recovery (3e) not download mode.
How can I flash the phone if I can´t get it back to download mode?
AS i said you are not following instructions .
DOWNLOAD MODE as posted.
HOLD Menu + Power + Volume DOWN down as in the bottom half of the volume button.
Instructions are not use super click in download mode phone should have rebooted .
jje
Thanks again, I did get it back to download mode an retried to use odin as instructed but again when the phone is supposed too boot, it just shows the yellow sign and then goes on a loop.
Can I use XWKDD_insecure.tar with the Korean version of the phone?
Hi. Yesterday i had a problem installing a recovery from Cyanogenmod rom and i got the message of fast booting. I found a tutorial saying how to repair it and i followed it without any problem.
But now, when i boot the phone, y reach the "Android" bootanimation and it stays like that forever. What can be happening now? I had Cyanogen from Mik and flashed a stock froyo (now trying a stock gb, maybe that´s the problem)
Can i save the phone?
Greetings.
After flashing the stock GB, the phone remains the same, staying in the Android bootlogo for ever
Any idea?
You have to wipe data.
Via normal Android recovery? Because when i access to it it shutdowns :S
Yes, but after factory reset, phone should reboot.. For you it only shuts down?
Let´s see, i followed the tutorial and flashed a stock gingerbread (before a stock froyo).
Then, when i access the recovery , a little image with a box, a droid and a bar appears, but then it only reboots. There, when Android bootanimation shows, the phone stays like that for ever and i need to quit the battery.
Edit: I accesed the recovery, but i can´t push any option, only go up and down.
strange.. the bar need to load till end and then the phone reboots.
maybe you have to wait for longer at bootanimation? because the first boot takes longer.
if not, try to flash ROM again, with kdz.
Edit: the menu button doesn't work?
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
Click to expand...
Click to collapse
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Are you able to wipe everything?
data, cache, dalvik cache and battery stats.
No, that menu doesn´t work. I only can wipe cache and factory reset.
It appears the rom is well-flashed, but when it reaches the android logo it goes in a loop.
then wipe data and cache.
It resurrected! :O
I flashed a stock Movistar rom from America and it booted normally! Thank god
But i don´t understand why booted now and not later. Also, i couldn´t do anything it the recovery. Anyway, i can root it again because it´s a froyo.
Thank you.
Greetings!
yeah, it's strange that it didn't boot earlier with other ROMs.
anyway, congratz
GL
Yeah, it´s weird. I´m returning it back to Cyanogenmod 7+francokernel like it was before the brick. I know what made it: install ClockWorkMod Recovery, so i´ll stay with the old recovery i had.
Greetings!
AgumonDX said:
I flashed like 3 different roms and waited in one of them 7 hours to boot. When it access the recovery it appears a warning button and this:
Finding update package
Opening Update Package
Veryfing update package
E: Failed to read footer from /cache/ (is a directory)
E:signature verification failed
Installation Aborted
No, in that recovery i can only go up and down, any other button works. If i push home, the recovery dissapear, but then if i push it again it appears again. That menu offers the option to wipe data but i can´t do it.
Click to expand...
Click to collapse
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
viv_jen said:
well dude
if you would have just toggled the signature verification off
you would have no problem installing the ROM
Click to expand...
Click to collapse
Well I dont know how we turn off signature verification. I faced an idential issue using v10E firmware from this link. KDZ update was not able to find the phone in emergency mode. Second time I tried, it did flash the f/w fine.
I got the triangle with an exclamation mark and a droid below. Recovery menu (pressing HOME button) was useless as I could not select any option with any of the hard keys.
This is how I solved it - rebooted once to recovery mode(volumen DOWN + Home), and face a progress bar for a few seconds - rebooted automatically to the LG sign. This time phone booted fine!
Hi there.
I tried to update a new ROM for my Lenovo A390. But sth was wrong with the phone I suppose. Firstly when I tried to start up with power button and vol+, firstly I got Android human logo with sth twisting next to its belly Then dead android humand with red exclamation mark showed up over. And nothing else happened.
When I was trying to flash custom room with Flash tool, the phone never answered to the 'call' from flash tool (after clicking 'Download' and connecting phone to PC - nothing happens ). So nothing could be done with Flash tool.
The next idea: I found some tips to use ADB and Fastboot. I had boot.img downloaded. It comes from 'A390_AllegroROM_v0.4a_SPFT'.
Then it went like this (in command prompt):
1.adb reboot-bootloader
2.fastboot flash boot boot.img
3. fastboot reboot.
answer for p.2 was OK, OK,
after p.3 as well
Now when try to switch phone on. It shows only lenovo logo and hangs up.
Is there a chance to get the phone working again?
After all this I discovered than when red ex. mark is being showed I can push power button and then I suppose recovery mode is shown?. But weird thing is I can not navigate through it. First option is set. It looks like:
Android system recovery <3e>
Android system recovery utility
Reboot system now(selected)
Apply sdcard: update.zip
Wipe data factory reset
Wipe cache Partition
(and below)
No .zip file in sdcard
So next idea was looking for 'lenovo a390 stock rom update.zip' file . I managed find sth (Lenovo_A390_Miui_Update.zip -> I changed to update.zip). I put it in root of sdcard, thinking that phone need this update.zip to do sth . Indeed, after switching into recovery mode (power + vol+) recovery mode looked similar but instead of 'No .zip file in sdcard' there was a few lines more:
Finding update package...
Opening update package...
Veryfing update package...
E: signature verification failed
Factory update failed.
Any suggestions? Do you think there is a chance to get the phone recovered ?
Hi All
I have samsung A5 2017. When i start my phone it shows no command and it continues to restart after 1 minute.
When i try to open recovery mode i get error "fail to open recovery_cause(No such file or directory)". I have also tried combination of key power and volume up but not getting recovery mode. I think it has been deleted or something else. I am also unable to load firmware.
I also tried to install twrp with odin 3.13 but get error unable to install frp locked.
Please tell me solution how can i get back recovery mode so that i can install firmware.
Please help me for this.
Hey there,
I have a similar issue and I can see your post dates back to 2020. Have you ever found a way?
I'm very curious about solving the issue on mine (I can't reboot at all, can't even access the reboot after getting the "no command" message. If you have any clue on how you accessed reboot mode and can be kind enough to share, this would be really appreciated )
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.