A305G bootloop + damaged recovery - Samsung Galaxy A30 Questions & Answers

Hi, i need your help.
My Samsung Galaxy A30 (A305G) doesn't turn on. It stays in bootloop and if I try to boot into Recovery, it doesn't work. The device has the bootloader locked and it also doesn't let me flash any stock / official firmware.
When I boot into recovery, some letters appear at the bottom of the screen, which say the following:
#no data on recovery_cause#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
E: failed to mount /efs (Invalid argument)
# MANUAL MODE v1.0.0 #
E: failed to mount /cache: Invalid argument
E: failed to mount /system_root: Invalid argument
E: failed to mount /cache: Invalid argument
E: failed to mount /cache: Invalid argument
E: failed to mount /cache: Invalid argument
': Can't mount /cache/recovery/last_locale
after that, it restarts, returns to recovery and repeats the same infinitely, a kind of bootloop but in recovery.
Odin log:
<ID:0/023> Added!!
<ID:0/023> Odin engine v(ID:3.1401)..
<ID:0/023> File analysis..
<ID:0/023> Total Binary size: 5836 M
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Set PIT file..
<ID:0/023> DO NOT TURN OFF TARGET!!
<ID:0/023>
<ID:0/023> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried flashing two stock ROMs (U4 and U5) and Combination firmware U4. Same error.
Thanks in advance.
favr3k

Related

[Q] [HELP] Samsung Galaxy S Anycall M110S Nandroid Backup/ Soft Brick

Good Day Folks.
So yesterday I was flashing my Samsung Galaxy S M110S (Korean Version)
with a stock rom
(M110S-Gingerbread-HOME-IMAGE-REV03-VG26-1812-USER.tar) and installing
Tegrak Kernel V29.
Everything works smoothly until I flashed a ClockworkMOD Recovery not
intended for my phone(sorry I was foolish and flash a CWM meant for
other device) then when I open my device I am always brought to this
(Samsung Stock Recovery)
Samsung utils blah. blah.
# MANUAL MODE #
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy kernel file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid Argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
blah.blah
Click to expand...
Click to collapse
I am only allowed to navigate with 3 options; Reboot, Wipe Data, Wipe
Partition. Rebooting only brings me to the recovery, both wipes
provides the same error.
So I try to flash again with the same stock rom and ODIN keeps on
throwing me this:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Left with no idea, I flashed an iCarus SpeedMod kernel(via ODIN) to see
what will happen. Luckily the recovery is now CWM and I was entitled
with so many options. One of this is the Backup/Restore option so I
think that if I have the right backup files stated below, I can put it
into the internal SD card(I have access) and launch the Restore
option to bring my phone back to life.
cache.img
data.img
dbdata.img
nandroid.md5
and all the other files you get when backup-ing files using CWM.
I am asking for your full help. Please be noted that my device:
Can access Download Mode
Can access Recovery Mode(no function)
Can be recognized by ODIN and be flashed.
...and is in need for a very big help!
So for those of you who has a nandroid backup(if my terms are correct)
of a Samsung Galaxy S M110S or has an idea to resurrect my device I
will be very thankful.
And If I can add I can also select Apply Update Via ZIP. Does that mean
I can also apply zip updates? If yes, where can I find those?
please help me with this one.
gertnilo said:
please help me with this one.
Click to expand...
Click to collapse
Seems an old post (just came across this ....anyway
You need to flash files from the repair kit, download from links below

[Q] Problem booting - Please help

Hi, I've searched for something similar to this for reference but to no avail. I desperately need some help.
My Galaxy Note was running ICS, the German stock version which was downloaded from odin at time of release. A couple of days ago, I rooted my phone using CWM.zip and SU-Busybox-Installer.zip which were downloaded from here, though I'm not sure that's what's causing the problem.
First thing this morning, my phone wouldn't get past the logo screen when trying to switch it on, so I went into recovery mode where I saw the following text
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
I was unable to find someone else with this problem so I unrooted the phone using CWM.zip and SU-Uninstaller-signed.zip, but it still wouldn't boot, then I had a look in the advanced options of CWM and the top option there was 'Reboot Recovery' so I thought I would give that a try as it seemed safe enough, but it's still running after several hours, this is what I've now got on my screen
ClockworkMod Recovery v5.0.1.5
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
87000
The 87000 figure started at 1, and is still rising. Is there any intelligent person who could help me, I would be very grateful.
Okay, well, I ended up just switching the phone off to get out of 'Reboot Recovery', but I've still got the same text on my recovery screen
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
Does anyone know what should be done?
Why dont you try and flash a stock rom from gb using pc Odin. And then go from there
Belfia said:
Why dont you try and flash a stock rom from gb using pc Odin. And then go from there
Click to expand...
Click to collapse
Thank you for that suggestion, I should have thought to try that myself, unfortunately, it didn't work.
Odin seems to have stuck at this:
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> factoryfs.img
<ID:0/018> NAND Write Start!!
Actually, I've just noticed you said
flash a stock rom from gb
Click to expand...
Click to collapse
so should I try to find/install a gb rom first, then reinstall the ICS rom?
Yes thats what I meant.
I've tried to flash a stock gingerbread rom, and still no success, slightly different to how it previously stopped though
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA6_N7000XXLA4_N7000XEULA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> cache.img
<ID:0/019> NAND Write Start!!
I am feeling so down right now, I need my phone, and there's a lot of non backed-up data on it.
Does anybody have any suggestions?
I'm sorry but it looks like you managed to brick your phone. There are several threads on how to recover from that. Try them, thats the best tip I can give you.
StewB said:
Does anybody have any suggestions?
Click to expand...
Click to collapse
Well, you can try to search the correct .pit file for your note (16 or 32 gb) and then flash again a stock ROM using pit you've downloaded and selecting re-partition option also.
Sent from my n7000 using tapatalk 2
[XIX]Secutor said:
Well, you can try to search the correct .pit file for your note (16 or 32 gb) and then flash again a stock ROM using pit you've downloaded and selecting re-partition option also.
Sent from my n7000 using tapatalk 2
Click to expand...
Click to collapse
Last night I tried this, and shortly after starting, progress stopped, with the top left box of odin showing 'Set Partition'. I decided to leave it overnight, during which, the phone battery had died. I tried it again with a full battery, and it's stopped in the same place as before
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Set PIT file..
<ID:0/019> DO NOT TURN OFF TARGET!!
I'm running out of hope as I really thought this would work
I would recommend you try flashing back to Abyss 3.9 Kernel, as per Rocket ROM OP. Follow instructions carefully and ensure flash into Recovery before flashing ICS. I am on RR 4.1 using this method (twice) and all ok.
TempusFudgeIt said:
try flashing back to Abyss 3.9 Kernel, as per Rocket ROM OP. Follow instructions carefully and ensure flash into Recovery before flashing ICS.
Click to expand...
Click to collapse
I've been searching for a while for the instructions which you mention, could you please post a link.
Thank you to all who offered advise, however, nothing which I tried worked, so my phone is now with a Samsung Service Centre and I'll hopefully get it back soon without have all my data wiped.
I'm not going to be a one thread member though, I will stick around in this forum, even if it's just an occasional post.
StewB said:
Okay, well, I ended up just switching the phone off to get out of 'Reboot Recovery', but I've still got the same text on my recovery screen
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_install
Does anyone know what should be done?
Click to expand...
Click to collapse
I have exactly the same problem and i need help too
Stevoxda said:
I have exactly the same problem and i need help too
Click to expand...
Click to collapse
It seems like you are using stock recovery. What ROM you are on ? Is your device rooted ? Do you have CWM installed ?
If you have CWM installed
Go To Recovery
Mounts and Storage
Format System
Format Data
Format Cache
Reboot Recovery
Now flash Abyss
Wipe Cache/Dalvik
Wipe Data
Flash Rom
Reboot System
Stevoxda said:
I have exactly the same problem and i need help too
Click to expand...
Click to collapse
Did you try the advice posted by sahilarora2003?
When I got my phone back from the Samsung Service Centre, everything was gone, it was like having a new phone again (not what I wanted). I did manage to get some things back using a 'MyBackup Pro' backup, but I did lose quite a bit. I hope you're luckier than I was :fingers-crossed:

Help internal mmc block !! galaxytab P1000

recently my galaxy tab keep crashing till it suck in the startup in a flashing logo of samsung
i tried odin never works then i went to samsung maintenance they say u hav to change the motherboard !!
i really dont think the problem from the board i really hope it can be fixed by using some kind of software
here is the text that i got from the recovery mode
--verfing internal mmc block
E: failed to mount mmc : open file
internal mmc checksum verify failed.
#MANUAL MODE#
--updating application ...
E: failed to mount /preload (no such file or directory)
E: install_application_for_customer:cant mount / preload
your storgare not prepare yet , please use UI menu for for format and reboot actions .
--Appling multi-csc...
installing multi -csc
multicsc : scan access to ojxcom .
multicsc : opera mini[lib] reset .
appliedthe CSC-code 'xss'.
successfully applied multi-csc .
Click to expand...
Click to collapse
I think the problem should be solved if you restock to stable gingerbread.. .
Sent from my GT-P1000 using xda app-developers app
tnx for the reply
i tried gingerbread it never works :/ kies cant open the tab my rom was froyo 2.2
He meant you should flash GB using Odin, not upgrade via Kies.
Follow my signature, download Overcome's PDF guide, and GB-Stock-Safe-v5 (it has all the tools you need in it).
Open the guide, jump to page 7, put tab to download mode, and flash according to that guide.
so no need to kies. cuz when it happen i tried other tut required kies i couldn't pass the first stage in oden then it bricked
i'll try it hope it will work tnx guys
sorry guys same result
it failed in the end of first stage
i got this message in odin
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> movinand.mst
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks like a bad internal sd chip.
Follow ChrisCTX's guide...search for it
Sent from my GT-P1000 using xda app-developers app

Flashing ROM is failed

Hi,
I have Samsung Galaxy S3 I9305 LTE phone made in Vietnam. Initially I got the Samsung Logo stuck issue. In the stock recovery mode i got the following error.
"E:failed to mount /efs (Invalid argument)".
I tried to wipe cache partition and checked. but no luck.
Then I rooted the phone using the following file:
CF-Auto-Root-m3-m3zh-gti9305.tar.zip
Then i installed the CWM recovery using the following file:
CWM_touch_6.0.4.7_i9305.tar
Then I went to CWM recovery and did the following things:
back up to /SD card
wipe data/factory reset
format /system
format /data
wipe dalvik cache
then First I tried to flash the 2 ROMs(I9305XXUFNL1_I9305H3GFNL1_I9305XXUFOA1_HOME.tar.md5 and I9305XXUFNL1_I9305ORLFOB1_I9305XXUFOA1_HOME.tar.md5) . Both are installed. but logo issue was still there. Then I found the ROM(I9305XXUENH1_I9305FTMENJ1_I9305XXUENG1_HOME.tar.md5) using KIES using model no and serial no.
I flashed that ROM using ODIN and ROM installation is failed. Following is the ODIN Log.
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> tz.img
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed.
Then I went to Android Recovery Mode and still I'm getting the following error:
"E:failed to mount /efs (Invalid argument)".
Note: I did not do any mount in recovery mode
Please help me on this.

Note 9 SM-N960U Flash Issues

Greetings all,
I'm attempting to flash my SM-N960U from ATT to Verizon. I've tried the Verizon version: SM-N960U VZW, which passes in Odin but the phone fails to mount the data. I get the following message on the phone:
/////
#Reboot Recovery Cause is [[odin]RebootRecoveryAfterOdinDL]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
-- Resizing...
E: failed to mount /data (Invalid argument)
can't mount '/data', rc = '-1'(Invalid argument)
:failed the resizing-data
\\\\\
I tried the stock version SM-N960U1 XAA - which fails. From what I've researched online, the SM-N960U version should be able to work on Verizon when flashed successfully.
Odin log:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7107 M
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any feedback.
Don't think you can because one is GSM and the other is CDMA.
Sent from my SM-N960U using XDA-Developers Legacy app

Categories

Resources