Related
Hello,
I have Android 2.1(Eclair), when I start my mobile, its show a Android logo with '!' (Recovery Mode)
Its show E:Can't find MiSC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
I am already try to reboot, wide data factory reset option.
please help me - how can I reflash my mobile?
More info please
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
demoneyes905 said:
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
Click to expand...
Click to collapse
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Hm....Adb
kunnusingh said:
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Click to expand...
Click to collapse
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
demoneyes905 said:
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
Click to expand...
Click to collapse
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
kunnusingh said:
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
Click to expand...
Click to collapse
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
theimpaler747 said:
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
Click to expand...
Click to collapse
I have no access to USB debugging so I can't use adb command and my phone always start in recovery mode, show only 4 options.
How can I install CWM recovery mode?
It is possible to reinstall whole OS?
Same Problem with HTC Hero, after one click (z4root) root
Hi @ all,
i have the same problem with my hero, and every solution that i can find is using fastboot, but with Eclair i cant´s use it.
So please help.
Here is some dato of my hero:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
Radio-6.35.15.11
1. If your USB debugging is enable then you can fix your problem.
2. official update.zip can fix your problem.
You can't do anything(but your mobile company can help you)
1. Your mobile company not release any update for your device
2. If USB Debugging is disable
I send my Micromax Mobile on 08 Feb, 2011 and Still no info on my device, Micromax = Poor Quality Support, Wastage of money.
@Micromax - Please close your company.... and move your company to your own country....
I tryed to fix it with every update.zip I found in web by
downloading the zip
rename to update.zip
format sd card
copy update.zip to sd card
start in recovery mode
try to start update
... and get a varification failed error
Has somebody a working update.zip, or can say where can I get it and if my steps are right?
1. If your update.zip is not official(signed) then you can't update your device.
Download this and rename this file to update.zip and retry.
Its a signed update.zip
http://www.filecrop.com/40683206/index.html (Link is valid for 30 minute)
If not work then just find your radio update in this list..
http://www.filecrop.com/update-Hero.html
Thank you very much, I will try it tonight.
Damn, now I get a
"failed to verify whole-file signature" error???
What´s wrong now?
Maybe I need a Certificate to put on my sdcard for the whole file?
HTC Hero Problem Solved
I have solved my Problem.
I downloaded the original RUU from shipped-roms.com, swtiched to Fastboot Mode and installed the RUU. And voilà, Hero is new again.
E:Cant mount/cache/recovery/last_log
any one plzz help me..
i have a micromax a60 brought in 2011
i want to update my ph 2.1 to 2.2(Foryo)
but i get a error on recovery mode..
E: Failed to find cache partition to mount at “/cache”
E:Cant mount/cache/recovery/last_log
E:cant open/cache/recovery/last_log
E:Failed to find cache partition to mount at cache.
Then i try to install zip from sd card, choose zip from sd card select Jet 2.1.zip. It ends up at.
assert failed: write_raw_image(“/tmp/boot.img”,”boot”)
E:Error in sdcard/installations/Jet 2.1.zip (status 7).
Installation aborted.
i flesh my phone throw android download toll but he is still showing this message.. plz help me...
& it won't let me install a .zip from sdcard..
ClockworkMod Recovery - for I9003 by Skin1980
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount cache/recovery/last_log
E:Can't open /cache/recovery/last_log
-- Installing: /sdcard/I9003JPKP5.zip
Finding update package..
Opening update package..
Installing update..
Installation aborted.
How could I fix this? Thanks!
Did I kill my phone?
jayroolz said:
& it won't let me install a .zip from sdcard..
ClockworkMod Recovery - for I9003 by Skin1980
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount cache/recovery/last_log
E:Can't open /cache/recovery/last_log
-- Installing: /sdcard/I9003JPKP5.zip
Finding update package..
Opening update package..
Installing update..
Installation aborted.
How could I fix this? Thanks!
Click to expand...
Click to collapse
Are u trying to install cwm? Just flash cf root, its much simpler. Flash via PDA in odin
Cheers
Sent from my GT-i9003 powered by MIUI
jayroolz said:
& it won't let me install a .zip from sdcard..
ClockworkMod Recovery - for I9003 by Skin1980
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount cache/recovery/last_log
E:Can't open /cache/recovery/last_log
-- Installing: /sdcard/I9003JPKP5.zip
Finding update package..
Opening update package..
Installing update..
Installation aborted.
How could I fix this? Thanks!
Click to expand...
Click to collapse
Try removing the battery!
Or the best thing is you do a full wipe in recovery and enter download mode and then flash any stock rom!!
And then flash any kernel for recovery! Mine is uc v9!!
This will fix your problem..
bscraze said:
Are u trying to install cwm? Just flash cf root, its much simpler. Flash via PDA in odin
Cheers
Sent from my GT-i9003 powered by MIUI
Click to expand...
Click to collapse
dude am trying to flash the stock rom but it won't let me
I can't go to download mode to use odin :/
rohan. said:
Try removing the battery!
Or the best thing is you do a full wipe in recovery and enter download mode and then flash any stock rom!!
And then flash any kernel for recovery! Mine is uc v9!!
This will fix your problem..
Click to expand...
Click to collapse
It won't let me wipe data/factory reset
it won't format /cache & /datadata !
your subject and words are two different things. you are going into recovery and attempting to flash a zip, but it fails. your subject said your phone won't start, and instead goes into recovery.
don't take offense, but "all bases have to be covered" since you're a new member, so:
do you know the difference between recovery and download mode?
how many times did you try going into download mode? it doesn't always happen on the first attempt.
if it's still failing even after 5 very careful proper tries that would put another phone in download mode, did you try removing the battery? how long did you remove the battery for before trying to go to download mode again?
Try again. Boot into downloading with volumedown+home+power
Sent from my GT-I9003 using Tapatalk
hi jay it sounds like ur partitions r messed up, that u cant access ur Cache partition
Solution :- Repartition & flash XPQ back.
1) Put ur phone in Download Mode
2) start Odin in ur PC then connect ur phone to PC (Odin should detect ur Com No.)
3) Click Pit then select "latona_20110114.pit" file
(Re-Partition, Auto Reboot & F. Reset Time should be ticked/Checked)
4) Click Start (Wait till it Says Pass) (Ur Phone will Restart to a Black Screen)
5) Remove & put ur battery back to ur phone.
6) set it back to Download Mode
7) Click Reset in Odin (Re-Partition should be unchecked).
8) Click PDA button and select this file: CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5
9) Click PHONE button and select this file: MODEM_I9003XXKPE_REV_00_CL1041909.tar.md5
10) Click CSC button and select this file: GT-I9003-CSC-MULTI-OXAKPE.tar.md5
(Auto Reboot & F. Reset Time should be ticked/Checked)
11) Click Start.(Wait till it Says Pass) (Ur Phone will Restart, wait till ur phone starts shows the settings page. then restart to Download Mode)
12) Repeat Step 1 to 11
13) Click reset
14) Click PDA & "Select I9003XXKPQ_I9003XXKPQ_I9003SERKPQ_HOME.tar.md5" file
15) Click Start. (Wait till it Says Pass) (Ur Phone will Restart, wait till ur phone starts shows the settings page)
16) Done.
Required File
1) Odin & "latona_20110114.pit" files Attached
2) XXKPE & XXKPQ from here
Thank you everyone for your help
actually, I noticed a post here on the forums saying that if I remove the battery, press the combos, then insert the battery while pressing the buttons for download mode.
I tried it & it worked !!
I flashed JPKP5 since it has arabic support then flashed cf root
Everything works fine now I have a rooted phone, trying to flash MIUI on it.
Hope it works.
Thanks again guys for helping I really respect.
Can't find alternative download link.
I have searched the internet for any other download link for xxkpe firmware (since hotfile is closed) but could not find any. I will be very thankful if anyone of you could provide an alternative working download link.
Greetings;
Go to Sammobile website. Search for your device and then pick the ROM you need.
Alternatively I recommend DDLF2 Full ROM. (Found in XDA Forum)
http://forum.xda-developers.com/showthread.php?t=2837212
Please press Thanks Buttons if this helped you, as this will keep me motivated to continue helping people.
Sent from my GT-I9003 using XDA Free mobile app
Hi
This is my first message. Sorry for my bad English.
I'm live in Turkey. I bought on December 2011 a GT-P6210 from USA. Therefore my tablet has no warranty in Turkey.
The software/firmware is original. No root.
Today my tablet freeze on boot screen, it could not boot up, not close, battery does not charge.
I tried Android system recovery, but failed with many error message,
i e
"E: failed to mount /cache (No such file or directory)
E: can't mount /cache/recovery/command
# MANUAL MODE #
-- Updating application...
E: Failed to mount /efs (no such file or directory)
...."
The links of screen photos are below (because this is my first message, I can't share links directly)
i25.photobucket.com/albums/c59/hatipoglu/20120811_175038.jpg
i25.photobucket.com/albums/c59/hatipoglu/20120811_175943.jpg
i25.photobucket.com/albums/c59/hatipoglu/20120811_180020.jpg
I tried "reboot system", "wipe data/factory reset" and "wipe cache partition", but failed. Because I can't close the device, the device battery discharge.
What can I do yet, before the battery completely discharged? Can odin help me? An orginal ICS firmware update? I think nothing can't be mount by the system?
Thanks
Edit (SOLVED): Original USA firmware (GT-P6210_XAR_1_20111110151418) flash with Odin, only PDA and without "re-partition" don't help
I found this: http://forum.xda-developers.com/showthread.php?t=1681047
I can't found pit file for 6210, I use 6211 pit file. Select also bootloader, PDA and CSC. Reflash and my device resuscitated
[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
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.