Android Nauget " No Command" Message - Android Q&A, Help & Troubleshooting

Hi
I have a trouble if you can help.
I have SM-J701F mobile model. when ever I updated it, the process in recovery installing system update goes to 32 percent and then shows erasing and phone restarts and then Android pic appears with "No command" and every thing stop here. after a period of time it goes to black screen.
Any option I tried to execute in black screen like wipe/cache or other options, it says "e misc partition could not find" even turn off or reboot failed and "e misc partition could not find" appears .
I 'd like to mention that When I used odin tool to install my firmware model to my phone at first try I chose CSC firmware file instead of Home CSC file. Then I tried to repeat the firmware installing process again but with choosing Home CSC file this time. but the problem remains.
How I could solve this problem ? and what is the reason for that ?

Related

Galaxy doens't start anymore - application installer stopped

Hello,
I have a big problem with the I9300 from my mother-of-law.
Her Galaxy is neither modified, nor rooted or anything. So it's stilll stock.
Now her I9300 won't boot correctly anymore.
When she starts it, it lasts much longer than normal to boot. When unlocking, an error message pops up immediately "Application Installer stopped" (angehalten), when clicking ok, it comes another time then it reboots completely.
When going into "Android system recovery" and wiping data/factory reset, there still comes an error message when I reboot (error) and the same procedure appears.
> It lasts a long time to boot > after unlocking the error message appears (Application installer stopped and it reboots immediately).
Does anyone have an idea what the issue might be and what I could do?
Flash a new Rom?
(P.S. sometimes it doesn't start at all an just shuts down and the battery is empty - even though it was still 77%).
Edit:
Sorry, I made a data / f factory reset another time and now it finally seems to work, unfortunately with all datas erased..
You should flash newest firmware for your country via Odin and it should work correctly

Evercoss A28b Stuck At "Setup Wizard Has Stopped" After Factory Reset

After factory reset I get "setup wizard has stopped" but I'm not able to flash my rom
Hi all
this is my first post so please be nice to me if I do something wrong.
Ok, where to begin with my long list of problems...
1. I have an Evercoss A28b bought in Indonesia but manufactured in China. It has Mediatek 6972 and SW version is ALPS.JB3.MP.V1.40 (that's what I could find in the phone's factory mode)
2. I rooted it 2 months ago and put all my apps and data on it from my old phone with Titanium Backup. I had some minor problems in the beginning but fixed them all and the phone was running smoothly.
3. This morning I froze "Go Launcher Z" because I didn't like it anymore and wanted to try how my phone looks withour it. Since the moment I froze the app nothing happened. I couldn't access the home screen or the app drawer but only my recently used apps when pressing and holding the home button.
4. I wanted to reboot my phone but it kept booting and booting, saying "android is upgrading" all the time. After one hour I took out the battery and now it's dead.
5. I tried to reset it into factory mode and first it seemed to work because it asked me to do all the settings like language, google account etc. As soon as I was finished a window appeared with "unfortunately setup wizard has stopped" and now I can't even see my homescreen or anything. My screen is black apart from the battery, wifi and SIM icons in the top right corner.
Now, what I tried to do:
1. I googled and found a few solutions saying I should flash my rom. I googled and found the sp flash tool and a rom for my phone.
2. SP Flash Tool did not recognize my phone and there was no scatter file in that ZIP file that I had downloaded.
3. I downloaded MTKdroidtools to try to generate a scatter file from my phone and a lot of different drivers but none of them made my phone connect with DroidTools.
4. So I went back to SP Flash Tool and googled for hours in order to find a scatter file and make my phone connect with SP Flash Tool. I managed to find another rom, this one had a scatter file in it and I also managed somehow to connect my phone with SP Flash Tools. It was only recognized after I had selected the scatter file and pressed the download button though.
5. SP Flash Tools brought an error message saying my pmt has changed and I need a new one or something like that. Unfortunately I can't even re-do this to give you the correct error message because I can not connect my phone to the PC any longer. Everytime I do this with battery or without it keeps connecting and disconnecting all the time.
6. I am at my wits ends and don't know what to do any more.
Please help

android.process.acore

i recently flashed a new firmware on my sony xperia z2.
everthing went good.
i started up my phone and as i wanted to type in my sim code there was the error Unfortunately,android.process.acore has stopped for a millisecond and then my phone rebooted again and again and again.
pls i wanted also flash another firmware but the same thing happened.
Please Help.
Did a forum search and tried every solution I could but this is where I am at......D6503
Same problem as OP
Had working MM (niaboc79's found @ http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770) but for some reason without the included recovery.
Decided I would install [NUT]'s Z2-lockeddualrecovery2.8.26-RELEASE.combined in preperation for future flashes.
This lead to a Bootloop.
Then I flashed D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf via Flashtool.
This helped me passed the initial Bootloop, all looked good, got the usual "program optimizing" load up.
System booted, albeit in Spanish, to language screen.
After that I got a few errors such as "unfortunately media...gmail...stopped" which allow me to press "OK"
then the "unfortunately,android.process.acore has stopped" message which is where the system freezes and reboots.
If I leave it alone and don't touch it, it just boots for 5/10 seconds before freezing and rebooting.
I tried flashing a different ftf however since flashing D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf all my settings have been reset, so USB Debugging etc is no longer checked which means it will not allow flashing.
I have access via Fastboot and Flashmode but I am unsure what I can do with these to restore a working system.
While phone is booting Flashtool reads my device correctly (model, firmware) and informs me I do not have root access, Busybox any longer.
It does give me the option at this stage, via now accessible tabs in Flashtool, to "root," "ask root permissions," and "install apk" but nothing I do works.
One one occasion, not sure what I did as I seem unable to repeat it, but it said I did infact HAVE root access. At that point I should have clicked on Flashtools "install recovery" or "root" tab but unfortunately didn't.
What are my options here? Is there a solution I can perform myself at this stage?
Thanks in advance
UPDATE:
Tried again for the 600th time, this time took my memory card out and it seems to have flashed the "...264" rom.
Select all wipes when flashing a new firmware.

[Solved] SoftBrick, Odin saying "Complete(write) operation failed"

Hi there,
My S9+ (SM-G9650) is softbricked right now, due to a attempt on flashing the Pixel Experience ROM in it. After a few tries, using the "High on Android" tutorial for this kind of procedure, I gave up, seeing that my phone did not correctly flash it, and every time I booted it up, the Samsung logo appeared, with the opened lock with the "CUSTOM" warning below it, and the warning "Set warranty bit: kernel" on the top of the screen (or sometimes with the "Set warranty bit: Recovery" message instead, when I boot into recovery mode). I also can't seen to rid myself of TWRP, since every time I boot into recovery mode, TWRP is there.
So I wanted to undo all that I have done by flashing the stock firmware for the device through Odin 3.13.1. But I keep getting the same error message, a few seconds or a minute later the flashing process is started. It says "Complete(write) operation failed".
I am familiar with adb and fastboot, as well as flashing images to phones like Essential Phone, but I am at a loss with this one. I have tried following some tutorials, but they all say the same thing, and it is not working for my case. Btw, the name of the zip file I downloaded and tried to flash is SM-G9650_1_20180418174053_asu7y86t8u_fac.zip (oreo 8.0.0), if this information is of any help.
Any thoughts? Or advices?
Edit: fixed it already. Guess I had the wrong file

fail to open recovery_cause(No such file or directory)

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.

Categories

Resources