Galaxy S7 G930F stuck on "No Command" screen after trying to flash back stock
Hello All,
First of all thank you all for your posts. I'm reading XDA forums for years and use rooted phones with custom ROMs thanks to the info you are all posting here
I've recently received a brand new S7 SM-G930F.
First thing out of the box I wanted to get rid of Google and Samsung bloatware and flash LineageOS (like I've done with previous phones), but ended up as a hopeless lady stuck in a boot loop
This is what happened:
Flashed a brand new S7 SM-G930F (Android 8.0 installed) with TWRP (3.2.3), LineageOS (14.1-20181011-nightly), Magisk (17.1), Xposed.
I then restored a TWRP backup from a S7 SM-G930FD (same LineageOS, but from a dual sim version phone).
Initially everything worked fine, then I noticed the SIM card is not recognised and that the baseband version is "unknown".
Also, every time I connected to my Wifi network while the other S7 SM-G930FD was connected as well, the last was disconnected.
Diving into XDA forums! Reading and reading, I figured the only way to fix it is to run a TWRP backup, wipe everything and flash a stock firmware on my device. Then flash TWRP again and either restore LineageOS backup or starting from scratch (without wiping system to keep the baseband version).
Things went down south when I tried to flash stock with Odin 3.12.3 (never did I ran into trouble doing this before!).
Flashing did not pass.
Downloading a different stock image from SamMobile and flashing, this time it did pass, but had another problem:
After flash the phone showed an "Installing software update" on a blue screen for about 30 seconds.
Then the message has changed to "Erasing" for about 5 seconds more.
Eventually received a blue "No Command" screen with a yellow warning symbol.
Tried to reboot. Then clear cache and reboot. Then wipe data. Tried to flash another stock image from SamMobile (different carrier), again getting to "No command" screen.
Did that with several stock images from different carriers, both with Android 8.0 and 7.0. All resulted with a "No command" screen.
I then flashed TWRP once again through Odin.
Wiped the phone and install LineageOS. Works! :victory:
LineageOS boots fine, just not recognising the SIM (as before). Also when I go to Settings → SIM cards, I have SIM 1 and SIM 2. Both are not recognised, but this is not a dual SIM phone
Relaxing that the phone can still function, I tried once more to flash stock through Odin.
Flashing did pass, phone rebooted, got an "Installing software update", message which changed to "Erasing", then I've received an "Error" screen. Looks exactly as the "No command" screen.
Now whenever I'm rebooting the phone it is stuck on boot screen. Although I can still get into recovery or install TWRP via Odin.
This is Odin's message when flashing stock fails:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a photo of the message I see when booting into recovery.
Text of this message here:
Code:
Installing system update
Error!
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File-Based OTA
Supported API: 3
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
When I click Mount /system and reboot nothing changes.
Device technical info:
Device out of the box:
Android version: 8.0.0
Baseband version: G9730FXXU2ERD6
Kernal version: 3.18.14-13438344-QB18292513; [email protected]#1, Sat May 26 15:53:42 KST 2018
Build number: R16NW.G930FXXU2EREM
Knox version: Knox 3.1, Know API level 25, TIMA 3.3.0
Device after flashing TWRP/Magisk/Lineage:
Android version: 7.1.2
LeneageOS version: 14.1-20181011-NIGHTLY-herolte
LineageOS API level: Guava (7)
Device after flashing stock firmware again:
samsung/heroltexx/herolte
8.0.0/R16NW/G930FXXS3ERI1
Hope there is a genius here that understand how I can fix this. I was assuming that going successfully back to stock will sort the baseband version/kernel and the phone will read the SIM card again, but I may be wrong?
Please share your insights!
Thank you :angel:
I have the same problem
To get back phone you flash original firmware and after that flash
no-verity-opt-encrypt-6.0.zip from somewhere on this forum.
Probably your /efs is damage
After flashing some firmware original/ and roms I've get working phone but not for long. After some time once it was 2 weeks once after 2h I get network error and no sim errors like you did.
Odin is shown flashing U2 firmware to S3. The firmware should be U3, S3, or higher (newer)
New firmware might require Odin 3.13.1.
Unzip the firmware with a different archiver.
Ensure the firmware download hadn't been interrupted.
I do not recommend anything EFS (backup is ok) unless sure (a data wipe or firmware change should be enough).
Thanks you both for responding!
@jaqjacek, I have flashed no-verity-opt-encrypt-6.0.zip after installing TWRP. These problems occurred after.
Could it be that the SIM problem started do to restoring a LineageOS image from a Galaxy S7 Dual SIM (G930FD)?
@Bryan48765, all U3 firmware are from South America countries. I have tried before S3 firmware, and have tried it once again, using Odin 3.13.1.
The result was the same.
Here are some details:
Flashing stock through Odin 3.13.1 - PASS :victory:
Phone reboots, blue screen with "Erasing" message, then "No command" screen:
Screenshot of recovery right after (DMVerity success):
Phone stuck on boot screen. Only can reboot into download mode, then rebooting into recovery. While reboot I get a blue screen with "Installing system update" message:
"Installing system update" changes to an "Error" message (wasn't fast enough to get a screenshot). But this is a screenshot of the recovery after (DMVerity fail):
Does this makes any sense?
Try smart switch!
jackherer72 said:
Try smart switch!
Click to expand...
Click to collapse
Yeah tried that but Smart Switch doesn't seem to pick up the fact that my device is connected. I can only get to recovery/download modes so I guess that's why..
Any idea if I can switch back to LineageOS and flash modem/baseband only?
Or do you think that after switching back to LineageOS and booting the system Smart Switch will then be able to read the phone?
OK made some progress and posting here just in case anyone else will ever run into this mass
To get myself out of this mass I:
- Flashed TWRP, mounted system and EFS, flashed no-verity and cleared dalvink/art cache. BTW data wouldn't mount so changed data file system to FAT and then to EXT4, data then mounted OK.
- Then Samsung screen appeared and system booted (yay!).
- Phone didn't read sim just like Lineage couldn't. When checking the device information I now see my other phone (s7 dual sim) model number, serial number, no IMEI and no baseband.
So in short, my issue here all seem to have started when I (stupidly) flashed S7 Duo (SM-930FD) TWRP recovery file on my new non-duo S7 phone (SM-930F). The fact that both use the same file of LineageOS firmware doesn't mean I could do that and expect the rest of the phone to work properly.
Questions for you:
- I have a TWRP backup of before flashing the Duo restore file, do you think that will revert back to original model & serial?
- If no, I guess I will now need to root the device and manually change back to my model number (from SM-930FD to SM-930F) and serial number so that my phone won't have identity issues anymore
Did any of you guys do it before?
Found this tutorial: https://www.techgainer.com/change-fake-android-device-model-number-and-brand-name/
Does that make sense or am I about to brick my phone again?
hello;
plz did you foundany solution??? i have the same probleme ...
- cannot flash stock firmware
- imei: 00000000000000
- sim card don't works
however i can flash costum rom
g930f u3 bricked after trying to flash combination file to get duel sim , and finaly i gget no sim looool
any solutions?
Guys, I have the same issue, can someone help me ?
Stuck on NO COMMAND after flashing stock rom .
Please help !
Had the same "No command" problem (and a corrupt recovery) and installing Samsung firmwares via Odin did not help.
But after I installed a TWRP-x.y.z.herolte.img.tar on AP with Odin I could boot into Recovery and install Lineage normally.
Related
I have an S6 that I believe is soft bricked. It will only boot to the android recovery screen. I have access to the downloader as well as the recovery. The error I've been getting is "dm-verity verification failed... Need to check DRK first..."
Model Number: SM-G920VZKAVZW (Verizon)
Current ROM: 6.0.1
Not rooted
My wife received an OTA update to 6.0.1 the other day. Since then the phone had been very slow. I did a wipe cache partition. Now on bootup I get the "dm-verity" error. To make matters worse, there are a lot of unbacked up photos and such that I'm desperately trying to keep if at all possible.
I downloaded the stock 6.0.1 firmware from sam-mobile that matched what I had on the phone (the top of the recovery screen had listed out 6.0.1 and the PDA number so I matched it up). I flashed via Odin and got Pass at the end. On bootup I was sent back to the recovery screen with an error I believe still saying dm-verity check but then "failed setting up dirty target". I rebooted again and I'm back to the standard dm-verity / check DRK error.
Any suggestions on what I can do and still keep my user data? Thanks!!
Bump... Help!
Hello there guys. i have an "E: failed to mount /efs (invalid argument)" problem to my s7 G930F Exynos.
The phone is NOT rooted. Had NOT activated OEM unlock or USB debbuging.
I tried to flash the stock rom and i succeeded but the problem is still there.
I dled and flash the G930F_FD_Factory_Binary and i succeeded but the problem is still there.
I tried to flash a custom recovery like TWRP but Odin fails every time on both stock rom and Factory Binary (i guess the lack of OEM unlock or USB debbuging causing that).
I managed to access ADB command while on Factory Binary only but still didn't manage anything at all.
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
I am out of ideas. I sent the phone to Samsung Service but cause of a small damage in the down right corner they ask me 250 euros to fix the damage and the /efs problem. They told me that they cannot fix the /efs problem alone.... Why ? Do not ask me.. It's their procedure
So... i need your help :/
I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.
RiTCHiE007 said:
I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.
Click to expand...
Click to collapse
i cannt install TWRP
soulremover said:
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
Click to expand...
Click to collapse
Can you do a factory reset from the stock recovery? It may be worth a try, but I think it won't help.
Likely, the EFS partition got corrupted for some reason. And as far as I know, this isn't easily fixable. This partition contains the IMEI and other information, and is encrypted + secured by certificates. One can't just copy the EFS from another phone.
Maybe the Samsung service is the only option .
Or try to root it so you have system access and then you can see if you can get to the efs folder and then try the permissions. But its weird that you get this by just flashing stock with odin. Only thing i would do is use kies to revert back to stock rom and see what happens
I'm having the same problem
I'm having the same problem, have you solved it yet?
Thx!
same problem here. can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked
Can you use adb ?
SrKag said:
can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked
Click to expand...
Click to collapse
If flashing the stock ROM (maybe try different versions) and doing a factory reset doesn't solve it, send it in for warranty.
Don't try flashing TWRP or rooting - it won't work if you didn't enable OEM unlocking (= disable the FRP) in the developer options before. With FRP enabled, the device runs only stock software.
And as I stated before: Even if you would have full access to the phone's memory (via a debug interface of the CPU) and therefore could flash whatever you want, there is no known way to repair the EFS. It is encrypted and device specific to prevent "bad guys" from changing the IMEI.
But still, I find it really bad that flashing stock firmware via Odin can damage the EFS partition.
Yea try to flash a stockrom with the samsung KIES tool and if that doesn't work then send it back.
Nothing will work I no I had the efs problem can u use adb?
Sent from my Samsung Galaxy S7 using XDA Labs
Hi I hope you can help......I have this ERROR & I tried several ways to fix it Running the EFS Professional.exe as Administrator.....& it keeps telling me I don't have enough storage & I deleted a bunch of apps & data from phone /sd but I keep getting this error unable to back up certain partitions
dd:writing'/sdcarrd efsprobackup/temp/userdata no space left on device
887462+0records in
887461+0records out
363504025 btes (3.4gb) copied,94,239635 seconds,36.8 MB/s
exitcode=1
now I tried odin method & it says invalid binary,......plz assist.......I tried flashing firmware N910TUVS2EQB1_N910TTMB2EQB1_N910TU VS2EQB1_HOME.tar.md5 bl/cp but it didn't work
Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.
thehost said:
Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.
Click to expand...
Click to collapse
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
http://efs.firmware.ir/g930fds/
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck
asgharSo said:
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
.................................................................................................
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck
Click to expand...
Click to collapse
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?
thehost said:
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?
Click to expand...
Click to collapse
For your flash you should use this ROM.
And you need twrp to restore the efs file.
Requirements and how to use efs in the posted efs post.
I tried the rom you posted, no effect, then tried TWRP ... FRP ON blocks the install ? can not install it
hi . . how to fix sm-n935f note 7 fe .. failed to mount efs , failed to find misc partition . . rmm state : prenormal .. stuck at boot logo .. any solution to fix it ?
i am also having same problem. I am unable to resolve the issue. i had tried all the solutions, which are posted here nothing worked. At last i gave in service center, to flash the stock rom. The mentioned it can't be done and there is a problem with board. Board has to replaced.
Kindly suggest the solution for it. Thanks in advance.:fingers-crossed::laugh:
maybe try this:
https://forum.xda-developers.com/ga...covery-official-twrp-herolte-t3333770/page125
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
darkalez said:
Click to expand...
Click to collapse
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
MAX 404 said:
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
Click to expand...
Click to collapse
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
darkalez said:
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
Click to expand...
Click to collapse
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
darkalez said:
I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
Click to expand...
Click to collapse
DroidHackeR said:
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
Click to expand...
Click to collapse
MAX 404 said:
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
Click to expand...
Click to collapse
Looks like OP has tried ODIN already
/data is likely encrypted, so it's not surprising that it doesn't mount, but it looks like you may have corrupted your EFS somehow. This is actually really REALLY bad. The EFS is device unique and by design irrecoverable. Previous Samsungs could regenerate it if you wiped it from recovery and then flashed stock with Odin, but AFAIK this hasn't worked since the S5. If you decide to wipe it make sure you dd your existing partition first, but if that doesn't fix it you may need to take it to a service centre and pay for a repair
Always backup the EFS first before flashing ROMs
flashing stock won't fix IMEI. Looks EFS is broken.
Try to find some1 with box.
*Detection* said:
Looks like OP has tried ODIN already
Click to expand...
Click to collapse
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
MAX 404 said:
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
Click to expand...
Click to collapse
BTW, to address that error he needs to format data. But backup his stuff 1st.
starche_old said:
BTW, to address that error he needs to format data. But backup his stuff 1st.
Click to expand...
Click to collapse
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
MAX 404 said:
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
Click to expand...
Click to collapse
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
starche_old said:
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
Click to expand...
Click to collapse
Hi
No really , as long as you dont use the data partition with TWRP is not necessary , check their thread , that step is no longer listed on the OP
1 In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2 Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
3 Extract Odin_3.12.3.zip to your computer.
4 Install Samsung Mobile Phone Drivers for Odin to find your device.
5 Download a .tar image of TWRP for herolte.
6 Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + v[Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
7 Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
8 Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
9 At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
10 If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
11 Go to [Reboot] -> [System].
12 Wait 2-5 minutes for your device to finish setting itself up
As i said in stock ROM , custom roms may vary
Regarding IMEI you are totally right if he does not have a EFS back up
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
starche_old said:
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
Click to expand...
Click to collapse
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
As I SAID I can't flash stock firmware with odin, because of efs folder problem.... I already tried it.
I haven't got a rom installed on my s7 and I can't flash any, it'll not boot.
I gived it to a local shop.... I wait for his reply
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
Try this guide to repair your efs.
Might be worth looking into re-partitioning here
If you can get into download mode, then there is always hope! Please excuse me if I missed any info, didn't read through the whole thread. Good luck! :good:
MAX 404 said:
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
Click to expand...
Click to collapse
Agreed.
And sorry everyone for off-topic
@darkalez: Since you have TWRP, you can flash other ROMs without any problem. I guess there are .ZIP files with stock ROM, although that won't reflash the recovery.
Why do you want to flash stock? If it's just to use that ROM, then do so via TWRP. Else you are in loss.
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
nickglas said:
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
I'm going to take a guess here, you had the device rooted and then you tried to apply an OTA stock update while the device was rooted? Tyically, stock OTA updates can't be applied to devices that have been rooted because the updates require the device to have an unmodified system partition(no root) and they require stock recovery instead of custom recovery. There are "some" devices that can apply stock updates while rooted, but those are few and far between.
If that is what you did, you need to do some searching for repairing failed OTA updates on rooted devices.
Sent from my SM-S767VL using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction:
This is the Official LineageOS 17.1 thread for the Moto G6 Plus, codename evert.
Information:
Official Wiki || https://wiki.lineageos.org/devices/evert
Installation
How-to || https://wiki.lineageos.org/devices/evert/install
Downloads:
Builds || https://download.lineageos.org/evert
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android Pie (9.0) Stock Firmware
Reserved
Reserved
what's wrong with my phone and how do I fix it when installing lineage17.1 ....? Because I always lose IMEI and Wi-Fi and I can never recover (is restarting alone too) only on 17.0..(only lineage 17.0 I can recover IMEI and Wi-Fi) And going back to stock 9 I also can't...
Thanks for the project and support!
(Google Translator)
SamuelYNWA said:
what's wrong with my phone and how do I fix it when installing lineage17.1 ....? Because I always lose IMEI and Wi-Fi and I can never recover (is restarting alone too) only on 17.0..(only lineage 17.0 I can recover IMEI and Wi-Fi) And going back to stock 9 I also can't...
Thanks for the project and support!
(Google Translator)
Click to expand...
Click to collapse
Sounds to me like your /persist partition is full.
Check this thread for more info, including how to fix it so you can get back to flashing ROMs or stock or whatever you want [emoji6]
Thaaaaaaankssss.
It worked
Okay, tried to upgrade, while I tried from the default Android Recovery that came with LOS 16, I got this error:
Code:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
E:Error in /sideload/package.zip (Status 1)
So then I tried to boot TWRP from an image through ADB and did the ADB sideload from there. It seemed to have gone well, with the exception at the end, where it complained that it could not find the /cache partition. (I've chose in TWRP to wipe the Dalvik and normal cache, so I assumed it wasn't a big problem).
After rebooting, I noticed the phone was stuck at the boot animation (the one with the swiping circle) and did not progress from it after leaving it 20+ minutes. I then tried to boot into recovery, and I did notice the new Lineage recovery. I tried doing an ADB sideload from there, but that also gave me an error with the signature mismatch. I then booted yet again into TWRP to try to install the zip file through TWRP directly as I have downloaded the zip files to the phone storage. While trying to access the phone's storage (data partition), I noticed all the folders and files had garbled filenames (random strings of letters and numbers). So then I went on to download the zip file again on an mSD card, and tried installing it through TWRP, and after restarting, I still am stuck at the boot logo.
Considering the filenames in the data partition were garbled, I assume it has something to do with the fact that the data on the phone was previously encrypted, and the upgrade didn't take that into account. Also noticed that on the second time I booted into TWRP, it no longer asked for the encryption pattern/PIN as it did prior to the upgrade.
Are there any steps I can take to fix this?
EDIT: If it requires wiping the data partition, is there some method of recovering the data?
Any big changes from the unofficial (at the time) 03/12 build? (I think that's the one I flashed last week)
From stock g6+ RETEU XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16
Steps taken:
0. fastboot set_active a
1. fastboot flash boot_a lineage-17.1-20200403-recovery-evert.img
2. Reboot to new recovery
3. adb sideload copy-partitions.zip
3. Factory Reset / Wipe Data + Wipe System from Recovery
4. adb sideload lineage-17.1-20200403-nightly-evert-signed.zip
5. reboot from recovery
Failed Result:
At this point usb-c cable is still connected and lineage continues to load
After asking for simcard pin and proceeding through lineage initial setup (date time etc.) cellular radio is disconnected and unable to connect no matter what. The IMEI is in place, the sim is detected and unlocked with pin code. Tested with single and dual sims in all configurations, phone purchased new in Germany, Vodafone.de sims.
The wifi works fine.
Almost immediately after unplugging the usb-c cable the shutting down spin dialogue appears and the phone reboots to recovery "Can't load Android system. Your data ma......"
Eventually the phone boots again but if the usb-c cable is not connected it shuts itself down within 30 seconds of booting, and the modems continue refusing to connect.
After reflashing the stock rom XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16 everything works fine as normal, stability and connectivity returns.
Same thing happens if open_gapps-arm64-10.0-nano-20200403.zip is sideloaded.
Any tips?
dm-verity" warning at boot
Hello to you,
Is there a way to get rid of dm verity warning at boot after flashing lineage os v17.1, rom works verry good,
Have not seen any problems yet, using with minimal google gapps.
Thank you
Hi there. First, I'd like to thanks to Jleeblanch for the great job of bring the experience of Android 10 to the oldschool Moto G6 Plus!
The ROM is awesome, I really like it. The only feature that is not working for me is the mobile network (mobile data). The first release (April's 1) had the bug of the sound calling that wasn't working, but it was done after the nightly update. So, could you please fix the mobile data bug?
Thank you in advance. Great job!
riancarlos18 said:
Hi there. First, I'd like to thanks to Jleeblanch for the great job of bring the experience of Android 10 to the oldschool Moto G6 Plus!
The ROM is awesome, I really like it. The only feature that is not working for me is the mobile network (mobile data). The first release (April's 1) had the bug of the sound calling that wasn't working, but it was done after the nightly update. So, could you please fix the mobile data bug?
Thank you in advance. Great job!
Click to expand...
Click to collapse
Try changing your preferred network type. When i flashed my phone it said "Global" and had no signal, but then i changed it to GSM/WCDMA/LTE and everything it's working except for VoLTE
La rom está perfectamente funcionando , aunque no inicia si se instala pixel gapps
hmillos said:
Try changing your preferred network type. When i flashed my phone it said "Global" and had no signal, but then i changed it to GSM/WCDMA/LTE and everything it's working except for VoLTE
Click to expand...
Click to collapse
I've tried to change the network type to GSM/WCDMA/LTE, but it didn't work, among others, but it all fails. After that, I did an update to April's 4 nightly version that just came out (with the change "sdm660-common: Force enable mobile network settings v2"), but nothing happens here. My G6 Plus stills lacking the mobile data.
Thank you for trying to help. Still waiting for a solution :good:
andoruB said:
Okay, tried to upgrade, while I tried from the default Android Recovery that came with LOS 16, I got this error:
So then I tried to boot TWRP from an image through ADB and did the ADB sideload from there. It seemed to have gone well, with the exception at the end, where it complained that it could not find the /cache partition. (I've chose in TWRP to wipe the Dalvik and normal cache, so I assumed it wasn't a big problem).
After rebooting, I noticed the phone was stuck at the boot animation (the one with the swiping circle) and did not progress from it after leaving it 20+ minutes. I then tried to boot into recovery, and I did notice the new Lineage recovery. I tried doing an ADB sideload from there, but that also gave me an error with the signature mismatch. I then booted yet again into TWRP to try to install the zip file through TWRP directly as I have downloaded the zip files to the phone storage. While trying to access the phone's storage (data partition), I noticed all the folders and files had garbled filenames (random strings of letters and numbers). So then I went on to download the zip file again on an mSD card, and tried installing it through TWRP, and after restarting, I still am stuck at the boot logo.
Considering the filenames in the data partition were garbled, I assume it has something to do with the fact that the data on the phone was previously encrypted, and the upgrade didn't take that into account. Also noticed that on the second time I booted into TWRP, it no longer asked for the encryption pattern/PIN as it did prior to the upgrade.
Are there any steps I can take to fix this?
EDIT: If it requires wiping the data partition, is there some method of recovering the data?
Click to expand...
Click to collapse
Try to wipe/format data/
Those numbers and that **** it means that all your OS is encrypted in your device, solution? Try to use ADB Sideload and install everything you need, Bootlogo, gapps, magisk, etc,
Boot problem
ORWPBE0I0lcloXXWctG2 said:
From stock g6+ RETEU XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16
Steps taken:
0. fastboot set_active a
1. fastboot flash boot_a lineage-17.1-20200403-recovery-evert.img
2. Reboot to new recovery
3. adb sideload copy-partitions.zip
3. Factory Reset / Wipe Data + Wipe System from Recovery
4. adb sideload lineage-17.1-20200403-nightly-evert-signed.zip
5. reboot from recovery
Failed Result:
At this point usb-c cable is still connected and lineage continues to load
After asking for simcard pin and proceeding through lineage initial setup (date time etc.) cellular radio is disconnected and unable to connect no matter what. The IMEI is in place, the sim is detected and unlocked with pin code. Tested with single and dual sims in all configurations, phone purchased new in Germany, Vodafone.de sims.
The wifi works fine.
Almost immediately after unplugging the usb-c cable the shutting down spin dialogue appears and the phone reboots to recovery "Can't load Android system. Your data ma......"
Eventually the phone boots again but if the usb-c cable is not connected it shuts itself down within 30 seconds of booting, and the modems continue refusing to connect.
After reflashing the stock rom XT1926-3_EVERT_RETEU_DS_9.0_PPWS29.116-20-16 everything works fine as normal, stability and connectivity returns.
Same thing happens if open_gapps-arm64-10.0-nano-20200403.zip is sideloaded.
Any tips?
Click to expand...
Click to collapse
I did the same as you, after flashing lineage os 171, i flashed minimal google gapps, then teset the phone from within recovery. I came from stock pie eu version, dual sim phone. I have used lineage recovery to flash lineage os v17.1, no problems at all with rom, only boot message is nerving.
charwed said:
I did the same as you, after flashing lineage os 171, i flashed minimal google gapps, then teset the phone from within recovery. I came from stock pie eu version, dual sim phone. I have used lineage recovery to flash lineage os v17.1, no problems at all with rom, only boot message is nerving.
Click to expand...
Click to collapse
Out of curiosity which 17.1 build did you flash exactly? 20200403? Did you use nano or micro gapps? XT1926-3 is your model no?
I had 2, what appeared to be separate problems:
the usb-c disconnect shutdown which is independent of sims card configuration
the 2x modems not enabling
Neither of which were present when re-flashing stock eu retail, and I went back and forth 3 times to confirm.
I can't understand if it was a problem with the modem partition or other firmware partitions, as those don't get touched when you sideload Lineage? Only Boot + System correct?
ORWPBE0I0lcloXXWctG2 said:
Out of curiosity which 17.1 build did you flash exactly? 20200403? Did you use nano or micro gapps? XT1926-3 is your model no?
I had 2, what appeared to be separate problems:
the usb-c disconnect shutdown which is independent of sims card configuration
the 2x modems not enabling
Neither of which were present when re-flashing stock eu retail, and I went back and forth 3 times to confirm.
I can't understand if it was a problem with the modem partition or other firmware partitions, as those don't get touched when you sideload Lineage? Only Boot + System correct?
Click to expand...
Click to collapse
did you flash the copy-partitions.zip ?
Info about flashed rom
i have used the one dated april 4
from the official lineage website, now i have updated to
lineage_evert-userdebug 10 QQ2A.200305.003 dfee070f5c. i did used the
minimal gapps beta. package. from the cyanogenmod website. i did flashed copy partitions AB after flashing lineage recovery from the official lineage website.
hmillos said:
did you flash the copy-partitions.zip ?
Click to expand...
Click to collapse
Yep, the first thing I did after entering the recovery, and it appeared to succeed each time.
I saw in the changes from 0403 to 0404 version:
sdm660-common: Update to clean Jasmine qti-telephony-common android_device_motorola_sdm660-common
sdm660-common: Force enable mobile network settings v2 android_device_motorola_sdm660-common
Sounds like it could be related, so maybe that fixed it, will test later.