Can't boot Android or recovery mode - Galaxy Note 10.1 Q&A, Help & Troubleshooting

I have a Samsung Galaxy Note 10.1 GT-N8010. One day it suddenly stopped booting Android and wouldn't pass the first screen (it didn't even reach the one with only the Samsung logo, only the one that says "Samsung GALAXY Note 10.1"). I booted into recovery mode and tried to factory reset, but I got this error: "E:failed to mount /efs (invalid argument)." So I followed this guide: https://forum.xda-developers.com/t/how-to-fix-e-failed-to-mount-efs-invalid-argument.2858056/
Here is where the problem begins. When I rooted to remove the factory mode (just following the guide), I did it using CF-Auto Root. But then my tablet stopped booting to Android (again, not passing the first screen), and when I try to boot into recovery mode, the CF-Auto Root screen boots instead (even after flashing stock firmware and TWRP). On this screen, it says the following:
CF-Auto-Root
Copyright (C) 2011-2016 Chainfire
Detecting devices . . .
- Recovery: /dev/block/mmcblk0p6
- System: /dev/block/mmcblk0p9
- Cache: /dev/block/mmcblk0p8
Preparing cache . . .
Mounting . . .
- System
- Cache
Rooting (SuperSU) . . .
Restoring stock recovery . . .
Cleaning up . . .
Rebooting in 10 seconds . . .
Then nothing happens. It still doesn't boot into Android, and if I try to access recovery mode, I get to the same CF-Auto Root screen. I can only access Download Mode, but I don't know what to flash to solve the problem. As I said, I tried flashing the stock firmware and TWRP (when I did that, Odin said PASS!).
I have been using Odin 3.10 and flashing this firmware https://sfirmware.com/es/samsung-gt-n8010/ (ARO). I also tried with a firmware downloaded through Frija (probably the same one).
I think that's everything. If I missed any information, please let me know.
Any help is welcome!
Thanks,
Whilz.

Good afternoon. I cannot guarantee that this will help you, as I have not encountered this problem and have not used these instructions. But maybe this will help you.
I found these instructions on the russian forum of the platform our devices are built on (n80**, i9300, etc.)
I will give the translation in this post and links to the original posts.
Spoiler: E:failed to mount /efs (Invalid argument) and how to deal with it!
Original post: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry26179020
According to the instructions, you need to flash I9300_Repair_efs.tar.zip efs image via Odin3. IMEI and S/N will be lost, so you will have to think about restoring it.
Spoiler: Error "E: unable to mount /efs (Invalid argument)" or "failed to mount /efs..."
Original: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry24433995
Attention! This method will not raise IMEI and S / N without efs backup. If you do not have it, then you can only download your phone, but there will be no network.
Tested on SGS III​
1. If you currently do not have root rights, then download them from the link from the topic header, the version for installation via Odin, install.
2. Download Custom recovery. Also versions for Odin (.tar.md5), install.
3. Download AROMA Filemanager
4. Install the File Manager through the recovery as a normal update.
5. Run the built-in terminal File Manager (press menu / select "open console" or "terminal" from the list).
6. We write commands (after each enter - input):
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
reboot
The commands are taken here - http://forum.xda-developers.com/showthread.php?t=1896470
7. Reboot into the system (reboot system now).
8. We read the instructions for restoring efs (who did what) and restore.
If during loading we see a translucent pop-up window with yellow inscriptions on the desktop
then we decide like this - Club of Samsung Galaxy S III lovers (Post # 16738476)
Spoiler: Problem Solution: failed to mount /... (Invalid argument)
Original: https://4pda.to/forum/index.php?showtopic=343514&st=8900#entry38837011
There's quite a lot of information here that I'm not moving here. Perhaps you can learn something for yourself by translating the page into the right language.

Related

Bricked my Spica i5700?

I had installed Samdroid Turbo Frozen Eclair, APPS2SD and Ext2/Ext4 and working ok. Today I started flashing a full kitchen of Samdroid from recovery, but the phone has locked in the "copying files..." process. Now I can't boot and recovery shows:
************************
Can't mount CACHE:recovery/log
Can't open CACHE:recovery/log
**** ATTENTION ****
SYSTEM: detect FS failed!
Fallback to RFS filesystem
*************************
I tried to apply a ZIP with the cooked flash, but the same error message is shown. I tried to install original Android 2.1 from Odin, but the Phone seems not to be in Debug mode (Odin doesn't find the phone).
Can anybody help me? Thank you
PS: Sorry for my bad English
I think you need to change ur file system back to RFS first.
But not sure though..
¡Solved!
The recovery menu didn't work and the firmware on my phone was not ok, so I couldn't format or do anything.
I found the solution following the 3 steps (and downloading exactly the files the author mention) on the article at
"/it/samsung-i5700-galaxy-spica-android-2-1-flashing-guide/" at "londatiga.net"
(sorry the forum doesn't allow me to publish URLs)
Spica recovery
You have to start from Lehsak's ODIN mod and then CM or Samdroid then it will be ok. I also had the same issue

[Q] E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory)

Hi Friends,
I am new to the XDA community and was driven here as a lot of my friends recommended this.
I recently installed the InDroid 4.0 on my Samsung Galaxy I5801 handset. Everything went fine, no problems. After that i wanted to upgrade the version from 4.0 to 4.1, but the upgrade method didn't work.
I would get the following error :- E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory) .
I have searched the forum and trust me, if there was a tool on this website which would tell you how long I have been searching, it would be nothing less than 8 hours straight.
I have read thru the forums about fastbooting and other options.
To begin with, I tried formatting my phone completely, used another SD card but I would get the same error. My phone is rooted but that error seems to keep popping up.
I get the following when I reach my Recovery Screen :-
------------------------------------------------------------------------------------
Android System Recovery
Samsung Recovery Utils – For BML-
Enter : ok key, select
Reboot system now
Apply sdcard:update.zip
Wipe data factory reset
Wipe cache partition
Finding the update package…
E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory)
E: Can’t mount SDCARD:Update.zip. Installation Aborted.
------------------------------------------------------------------------------------
I followed the steps exactly as in the InDroid forum and also, I downloaded the videos off youtube, just in case, but no go.
I am faced with two issues:
1) With this update, my memory card would never show up in the PC.
2) I cannot upgrade the versions.
Is there any way that I can directly go to version 4.4 instead of following the upgrade path?
Is there any way that I can upgrade by resolving this issue.
I am back to my factory Default Installation and the memory card works fine and everything else works fine.
I know that you guys are professionals and busy, but Any help would be Really appreciated. I could just back away to the factory ROM but i don't want my efforts to go waste.
Please Help.
Regards,
Shashank Raj.
Samsung I5801.

[Q] Installing CWM Recovery (and CyanogenMod) via Odin/ROM Manager not working?

I'm quite new to all of this flashing stuff-- sorry if I sound like a complete newbie.
So I'm trying to get CyanogenMod on my Samsung Mesmerize (Galaxy S), though to no avail. I tried to follow the guide on the wiki located at http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide though it's not working. I can't even get CWM Recovery on it.
To get CWM Recovery, I'm following http://forum.xda-developers.com/showthread.php?t=734166 -- it says flash back to a stock kernel first, which I did via Odin and by following http://forum.xda-developers.com/showthread.php?t=881064 (I downloaded the "EC10 Full Froyo Restore Package"... not sure what the difference is between that one and EE19 but it seems to work.)
I'll go over my steps from the beginning, starting from when I'm flashing back the stock kernel on my phone:
Flash back stock kernel (EC10 Full Froyo Restore Package) using Odin (I've also tried flashing the EE19 one)
It starts up after this, however it briefly displays "FOTA wipe failed" in red and "wipe_data failed" in yellow (along with some other stuff too, but no other errors - when I use EE19 these errors occur as well)
It starts up into the default Android system recovery - I choose reboot system now
Root my phone using SuperOneClick ('yes' to install Busybox prompt)
Insert SD card, Download & install ROM Manager from the Market (following this guide which I linked up above)
Select "Flash ClockworkMod Recovery" (Current/Latest Recovery: ClockworkMod 2.5.1.2)
Select "Galaxy S i9000"
Superuser prompt appears, I click accept
ROM Manager freezes for a bit, then displays "Successfully downloaded ClockworkMod recovery!"
Choose "Backup Current ROM" - freezes for a bit, then phone begins to restart... enters default Android Recovery mode:
Install from package... Finding/opening/verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted.
When I reboot and enter the recovery mode by holding volume-power-home,
it displays "E:Can't mount /dev/block/mmcblk0p2 (No such file or directory)" at the bottom.
Also, when I try to "wipe data/factory reset" in the stock Android recovery mode, it gives this error:
E:Can't mount /dev/block/mmcblk0p3 (No such file or directory)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
I also know there's a "Manual Flash Overrride" option in ROM Manager - could I flash CWM Recovery manually and go that route somehow?
My final goal is to get CyanogenMod installed on my Mesmerize, though-- however, I need CWM Recovery to do that. Any ideas as to why CWM Recovery isn't getting installed, and how to fix the mmcblk0p2 error message in recovery mode (and if that's affecting anything)?
Thanks!
MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Yes, and i will add ROM manager only works for Mesmerize MTD systems, and CM7 IS MTD. SO, technically you need to be on CM7 already to use ROM manager.
You don't need to use ROM Manager period.

[Q] E: failed to mount /efs (invalid argument)

Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.

Samsung S7 Edge stuck on "Powered by android"

[Problem solved] If anybody faces this kind of problem please notice it is not the problem of Nand-erase but DRK error and flashing with .pit file won't fix your problem. Just go to this discord group, https://discord.gg/Z4UZheJ [permanent] and ask for #Augustin. He will solve your problem 100%. He did for me. Full working network + rooted.
---------------------------------------------------------------------------------------------------
Hello, I was trying to update my s7 edge (SM-G935FD) with Oreo 8.0 from Nougat 7.0 with a custom firmware from sammobile.com.
The used file is: sammobile.com/firmwares/galaxy-s7-edge/SM-G935FD/BNG/download/G935FXXS3ERHD/236500/
But when flashing with Odin I accidentally selected "Nand Erase" option. After the operation completed my phone tried to boot up, showed installing updates, then tried to boot again and now permanently stuck on "SAMSUNG Galaxy S7 edge POWERED BY android".
Still, I can access "download mode" by using "Power + down + home" button and "android recovery" by using "Power + up + home" button.
While loading android recovery screen it shows, "Installing update..." then "Error" with an icon of android eyes crossed.
In my recovery menu, these lines are shown:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
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 mapping: 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 mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[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-permission-permission] fail to mount /system as rwE:[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-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device 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
I flashed with this same firmware to no avail. I have also tired "Wipe data / Factory reset" and "Wipe cache partition". Nothing worked.
Now, other people who have tired this firmware faced the same problem for #fail to open recovery_cause
But, in my case, as bold lines indicates, this is may be due to using "Nand Erase" in Odin.
I do have :
Nougat 7.0 firmware for my device [Please notice that its baseband is U2 - so I can't downgrade bootloader from S3 to U2 hence can't flash with Nougat]
.pit file for my device [not sure about this one - I actually need a valid pit file from the above firmware, others don't seem to work.]
I have tried Z3box / octopus / smart switch samsung software to recognize my device, but they always reply with "Card not found". My Windows treats my device as unrecognized in this situation.
Please help me fix this issue. I just have bought this phone - second hand.
-----------------------------------
Update - I tried to use stock recovery files to flash with TPRW stock recovery. After I did that It started the tprw recovery and I installled two files
1. twrp-3.1.0-0
2.SR3-superuser
It completed and when I selected to reboot my phone, it just won't turn on anymore. I guess it is due to my partition is all messed up. I forced it to start up using my charger cable and plugging it to charging. Using "Download mode" then I tried to uninstall this TPRW and flashed only "AP" with "G935FXXU2ERD5" with odin as I was unable to find any stock recovery for "G935FXXS3ERHD".
Now, I am stuck with U2 bootloader whereas I need S3 bootloader. My phone still doesn't turn on normally. I have to plug it in charging port / USB cable to pc, then it goes straight up to "Android Recovery" and Now shows this:
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 mapping: 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 mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[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-permission-permission] fail to mount /system as rwE:[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-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device 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
Successfully verified dmverity hash tree
E: Failed to clear BCB message: failed to find /misc partition
Please help me. I know I messed up, I shouldn't have used the TPRW recovery. Now I can't even flash with previous G935FXXS3ERHD or any U2 firmware. Please help me. I feel like crying.
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
https://drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
yakapa40 said:
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
Click to expand...
Click to collapse
jaqjacek said:
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
Click to expand...
Click to collapse
Dear all,
I don't know how to say it, but a miracle just happened. My phone was stuck to "Android recovery" mode for half an hour. The charging cable was plugged in - in this time. Right before I am about to disconnect the cable in order to take it to repair shop, it started booting out of nowhere. :fingers-crossed:
Then I set up the device and the device installed applications by itself. God knows what happened but here is my system spec now :
Android version 8.0.0
Samsung Experience version 9.0
Baseband version G93FXXU3ERHC
Kernel version 3.18.91-13895453-QB19588583
Build number R16NW.G93FXXS3ERHD
The TPRW application is also installed.
I don't know what happened but it has managed to boot.
--------------------------------
The problem I faced is, It doesn't let me select any network carrier for my region instead it just says, "Failed to connect! Try again later."
Now I am afraid to even restart the device fearing if it gets stuck in the boot loop again. I am so scared I don't know if I will flash this device with any stock firmware anymore.
And the "Android recovery" option still shows "Installing updates" following with "Error" with android icons eye crossed out + shows previous error messages still the same.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
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 mapping: 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 mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[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-permission-permission] fail to mount /system as rwE:[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-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device 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
Thank you, everyone.
If you could just help me solve my problems I will be always grateful to you guys and this community.
@jaqjacek if you can point out a tutorial to me or just explain the steps elaborately that would be helpful.
@yakapa40 if you can help me how to use those files, please.
My device is now booted up but still showing errors in "Android recovery" option + the sim network doesn't work.
What version of Odin are you using to flash?
quasihellfish said:
What version of Odin are you using to flash?
Click to expand...
Click to collapse
Odin3 v3.12.7 in windows 10. Installed samsung driver both manually and via Smart Switch.
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
yakapa40 said:
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
Click to expand...
Click to collapse
Ok, sir, I will try and let you know. One question though, is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
My android recovery says:
Android Recovery
samsung/hero2ltexx/hero2lte
8.0.0/R16NW/G935FXXU2ERD5
user/release-keys
use volume up/down and power.
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
yakapa40 said:
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
Click to expand...
Click to collapse
Dear sir,
I am still waiting for some kind of help. I haven't flashed my phone with .pit file cause I am too scared that my phone will get stuck in boot loop again. Please, somebody, help me. If I get stuck in the boot loop again, I don't think I can revert back to current position [Cause I don't know how my phone was fixed, it just fixed itself somehow.] and I can't take the stress. Please somebody who is an expert on this matter, please help me. I beg you.
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
ukero said:
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
Click to expand...
Click to collapse
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have poor network connection or GSM singal will be gone thats is the problem that I don't have fix for now.
jaqjacek said:
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have a poor network connection or GSM signal will be gone that's is the problem that I don't have fix for now.
Click to expand...
Click to collapse
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https://www.youtube.com/watch?v=C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
ukero said:
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https: //w w w. youtube .com /watch?v= C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
Click to expand...
Click to collapse
hey, im needing the file. i know how to do. please, help me. im with same issue, but with s7 flat SM G930F
Augustin is the best!
Hey there, I have a very similar problem with my S7 G930F. Could someone help me please? Thanks in advance.
(PS. The discord link is down, so I can't talk to Augustin)
After a lot of problems with my computer @ZeroXO helped me to solve the problem
Issue freeze and restarting
ZoOMBeE said:
Augustin is the best!
Click to expand...
Click to collapse
Can u tell me a way to contact him? the discord's link doesn't work anymore. I'm facing a freeze issue with my s7 edge. I mean It freezes when Im using it and also on TWRP so I can't install anything :c. I already flash stock firmware and it boots successfully , but in about 2 minutes it freezes and restart again. Also it happens in safe mode and recovery. Help me :c

Categories

Resources