No Command after flashing - T-Mobile Samsung Galaxy S7 Questions & Answers

My son got a used 930T. I managed to flash CRJ1 onto it via Odin a couple of weeks ago. Other than getting hot/laggy it was otherwise OK.
He showed me earlier tonight that it was stuck on the No Command screen.
I managed to get it back into Download mode and pushed CRJ1 again. Odin said it was successful and it kind of went through the steps. But it got to the point where it said it was installing a system update (while in Recovery) for a few seconds and then keeps going back to the No Command screen.
I somehow managed to get it to give me a MANUAL MODE screen that reads, in part:
#fail to open recovery_cause(No such file or directory)#
(there are multiple of all of these)
Failed setting up dirty target
Couldn't create verity device!
Fail to mount /system
I've never run into anything like this before..

More:
I was using the files from SM-G930T_1_20180625111401_xf3965I42.zip. Trying the Binary 8 files now.
The xf3965I42.zip files show as CL13718910_QB18653810
The Binary 8 files are CL14365146_QB20116095

Even More:
Binary 8 files not working either. I'm back to the "Installing Update" pretty much immediately followed by "No Command"

..trying CRL1..

Ok, everyone can ignore this whole thread. I documented this here basically in case anyone else runs into the same situation. CRL1 appears to have fixed the issue. This time, things were different.
After flashing in Odin (I was using 3.13), I got the following happening:
Erasing
Installing System Updates (got to 32%)
Erasing
Reboots into recovery again
Installing System Update (shows this for about 3 seconds)
No command
This time, it finally got into recovery after sitting on the No Command screen for about 10 seconds. Before, it would just loop between rebooting to Installing Updates and No Command - it would not show me the recovery options.
This time, I was able to wipe cache and factory reset.
I'm back in business!
Mods - please close this thread.

Related

[Q] Boot freezes/crashes after flashing images

Hello, I'm having some problems with my Nexus 5 LG-D820 32GB
Here is everything I did in order:
1 - Was using stock 4.4.4
2 - Tried to install OTA lollipop following this:
1) Install Minimal ADB and Fastboot.. This will allow you to run commands on your phone.
2) Install Android USB Drivers. This will add the proper driver to recognize your device.
3) Install Universal Android USB Driver. This will automatically add the driver when you go into recovery mode. It's a different driver than the one above.
4) Open Minimal ADB and Fastboot (your phone should be plugged into your USB now)
5) Make sure your phone is recognized (enter 'adb devices'. A long number plus the word "device" should show up).
6) enter "adb reboot bootloader"
7) Use the volume rockers on your phone until it says "recovery mode," then hit the power button.
8) When you get the android with the exclamation, hold power and tap volume up. Don't hold, just tap it.
9) Use the volume rocker to choose "apply update from adb."
10) Go back to the minimal adb and fastbook command prompt, and enter "adb sideload filename.zip". Filename should be the path and the name of the zip file. You can rename the zip file so it's easier to type in. You can also type in "adb sideload" then just drag and drop the zip file into the command prompt if you'd prefer.
11) It should now sideload. Once it finishes on your screen, it will go back to the bootloader and you should reset your system once it's finished.
12) Watch in anticipation as your apps get optimized.
13) Play with your phone.
Click to expand...
Click to collapse
3 - It apparently worked, no errors or anything. But, when the phone tried to boot, it got to the upgrading android screen, with the optimizing apps list (1 of 82), it kept freezing, crashing, showing graphical glitches, and rebooting.
4 - I went into recovery and did a full reset/wipe, thinking it might have been because of an app it was trying to optimize. It still did the same thing.
5 - I thought it might have been happening because I was trying to upgrade OTA instead of a clean full install, so I got the factory image from the google page and tried to flash it following this:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Click to expand...
Click to collapse
6 - Apparently it went ok, no errors or anything. But the same thing kept happening, it got to the optimizing app screen and would glitch up
7 - I got scared and tried to flash 4.4.4 back with the method in number 5. It worked, the phone was finally usable again. Thinking I had a way to always reset, I decided to keep trying to flash 5.0
8 - Tried again method number 5 with android 5.0, still glitched at optimizing apps
9 - Tried using Nexus Root Toolkit v1.9.4 to flash android 5.0, no apparent error, but got the same results at the optimizing apps screen
10 - Tried using Nexus Root Toolkit v1.9.4 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
11 - Tried using the method in number 5 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
12 - ??? I don't know what to do now. I was thinking of trying to flash 4.4.3 using the method in number 5 to see what happens >_>
Any help is appreciated, does anyone know why it kept freezing and showing graphical glitches at the optimizing app screen? Am I doing something wrong? The thing that bugs me is that every attempt went nicely, it isn't like I couldn't flash the images. I did flash them with no apparent error but they didn't work..
Thanks for any help
Hi,
I still have not been able to successfully boot into any usable version of android, they keep freezing and restarting the phone, but no errors appear during the flashing process. Can anyone shed some light?
Thanks
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
RoyJ said:
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
Click to expand...
Click to collapse
The animation is different, twirling pseudo 3D balls for 5.0 and 4 2D balls meeting in the centre for 4.4.4
And every time it stops at a different point. Right after I flash is when it goes the furthest, and then it goes less and less each subsequent boot
I really don't know I think I'll try flashing using the LG Flashtool to see if anything changes
It didn't work... I'm basically out of ideas
Guess I'll try the same things I've already done but with another computer, in the off chance the pc was corrupting something
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
mr2620 said:
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
Click to expand...
Click to collapse
At least you can revert to 4.4.4, mine freezes on the balls/once it did on the initial screen
Using another PC just made things worse, it froze while writing the system image and now the usb recognition is flimsy, sometimes it says the pc can't recognize the device when plugged in and sometimes it works, but now I can't flash things anymore
Welp. It's a less than a month old phone too, and I really think it's gone
Mine has froze a couple of times at that screen as well. I was able to force it into recovery mode with the power and volume down buttons and I was able to use the soft brick function in the toolkit to get it back to 4.4.4.
Sent from my Nexus 5 using XDA Free mobile app
Well I was able to flash 4.4.4 again ( I guess it's really hard to get it completely bricked, always when I thought it was gone it was able to get to fastboot mode)
But it still freezes on the balls / starter config screens
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
You said you tried LG Flashtool and that didn't solve the problem either?
I haven't tried the LG flash tool. I'll have to try that tomorrow.
Sent from my Nexus 5 using XDA Free mobile app
mr2620 said:
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, most problems are people receiving errors/not being able to complete flashing the images. What's crazy about this is that we follow the correct procedure, get no errors or anything, but it doesn't work
I'm still unable to boot. Will try contacting Google soon.
I still have been unsuccessful as well. I'm getting a replacement phone from Google. Should have it next week.
Sent from my Nexus 5 using XDA Free mobile app

[Q] Need help getting vacation pics off a Nexus 5 thats stuck on boot animation

My girlfriend took a bunch of pics on vacation with her Nexus 5, which now that she's home, won't boot, but instead just shows the flying coloured dots animation till the battery runs out of juice. The photos were not auto-uploaded or anything like that, they only exist on the phone.
It's a stock android, no mods, not unlocked, not rooted. Pretty sure it's on version 5.1.0 (LMY47D)
I can get it into fastboot and recovery modes. I can run fastboot and ADB from my (windows) computer to the phone (ADB only available in sideload mode from phone recovery boot's "Apply update from ADB" option).
I've tried using fastboot to boot other images on it, but that fails because the phone isn't unlocked (which I could do but that would wipe the photos)
I can try an ADB sideload (tried with zips from LMY47D, LMY47I, and LMY48B. They all fail at 0% transfered with the phone saying E:Footer is wrong E:signature verification failed
I've done plenty of Google-ing to get this far, but I'm out of ideas on how I can get the photos off the phone before factory resetting it.
Sounds similar to what happened to my girlfriends phone. I was able to get it started following this video https://youtu.be/8g4gXoSNh3Y
Worth a shot if you haven't tried already
Have you tried using adb pull while in recovery to pull the photos off?

Can't boot into recovery - Galaxy S7 G930

Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying:

Recovery Mode "REMOVED"

The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?

My Google Pixel seems bricked - Could someone confirm there is nothing I can do ?

Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device

Categories

Resources