Hi,
I woke up this morning and found my phone stuck on the startup logo.
I tried removing the battery and wipe the cache but it won't go past the start up logo.
I don't care about the phone, I wanted to change it anyway but I would like to retrieve some data before. So I haven't try the factory reset yet. Is there a way to save some data ? (my contacts and some data from note everything and task list mainly).
I afraid to try something and wipe all my data.....
Note : when I go to recovery, It says "failed to mount /efs (no such file or directory)... failed to mount /system ......"
Flash TWRP using Odin. Then boot into TWRP, mount the data partition, connect the phone to a computer, and copy off the data files. Hopefully, this method works for the phone.
You mean I have to install TWRP (? Team win recovery project) on my phone using Odin ? Is that correct and then start the phone with TWRP ?
Does my phone need to be rooted for that ? (it's not).
I haven't use odin or TWRP yet but I will try and tell you if that works.
Any advice for how to use Odin and TWRP for a beginner ?
Thanks
So after making a few more research to understand how to use odin et twrp, I tried to flash twrp using odin but it failed. Here is my log :
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so what do I do now ?
Use the tar version of TWRP, not the IMG version.
I used this file : twrp-3.0.2-0-t03g.img.tar so it should be right
So I finally tried to wipe the data from recovery mode and it didn't work.
Tried to reload the firmware using odin (N7100XXUFOC2_N7100OXAFOC2_N7100XXUFNG1_HOME.tar.md5) and got this :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something else I can do or is this a hardware problem ?
The sboot.bin file is the bootloader for the phone and could be failing due to the following reasons:
the ROM is not for the phone;
need to use a different USB cable and/or different USB 2.0 ports;
the bootloader in the phone is newer than the bootloader in the ROM;
the ROM needs to be flashed with a pit file;
the memory chip is damaged.
Related
This was originally posted in the wrong forum. My apologies.
So after following this link: http://www.cnet.com/how-to/how-to-ro...ung-galaxy-s3/ I have a bricked device.
No matter what I do, Odin seems to fail. This is what I think caused the problem in the first place. Also there is the possibility that the guide is way out of date.
So I was wondering if anyone had any advice on how to proceed? The device isnt mine and this isnt my first time rooting a device. I just have never bricked anything before.
Here is the log from ODIN from recreating the process in the link above
Code:
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is the Log from ODIN from my latest attempt to flash something at it.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing a full image, but it gives this error
Code:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried flashing the "stock" image.
Going to try a different PC tomorrow and hope that I get a different result.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you have an i747 or u747m? Do not flash any more ROMs without knowing the bootloader version installed on your phone. If you phone has a 4.3 or newer bootloader and you try to downgrade it, it will brick your phone.
I recommend that you install the latest version of Philz and flash cm10.2 for the d2att to at least get your phone running so you can determine the bootloader.
audit13 said:
Do you have an i747 or u747m? Do not flash any more ROMs without knowing the bootloader version installed on your phone. If you phone has a 4.3 or newer bootloader and you try to downgrade it, it will brick your phone.
I recommend that you install the latest version of Philz and flash cm10.2 for the d2att to at least get your phone running so you can determine the bootloader.
Click to expand...
Click to collapse
SGH-i747
And the issue I am encountering is a bit bigger than that, I cant install anything. I cant even flash the stock .tar file I found. I cant get ODIN to do anything except fail? I never even got CWM installed.
Can you get into download mode and stay in download mode?
There is not stock tar.md5 ROM you can flash from sammobile because AT&T never made a stock ROM available after 4.1.1.
Did you try to flash Philz Touch for the d2lte in Odin 3.07 using his tar.md5 recovery file? What about TWRP?
No TWRP either?
Can you provide me a link to that MD5
After digging up the MD5 I have got the phone booting again.
Thank you so much for all your help!
Boot loop after factory reset on GT-N5110
I tried to reset the device using Settings>Back up and reset>Factory data reset>Delete all.
Rebooted into a black screen with an Android with a hatch open and a blue spinning thing. It's been stuck in a endless loop of the startup screen with the name and model, which then goes to the Android with open hatch.
I pried the rear cover off and discovered that I don't have any screwdrivers small enough to remove the battery. So I'm wondering if there is any software based fix that I can try.
Holding down Power+Volume Down interrupts the loop and brings up this screen - blogyourearth.com/wp-content/uploads/2012/02/Samsung-Galaxy-S2-Warning-Custom-rom-installation.jpg
I've had the tablet for 2 years, so the warranty is long gone. I'd be open to flashing a Custom Rom/Kernel, as long as I'm able to go back to the default TouchWiz 4.1.2.
Bump/Update
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
emc_2 said:
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
Click to expand...
Click to collapse
Are you able to enter download mode without issues?
pvsgh said:
Are you able to enter download mode without issues?
Click to expand...
Click to collapse
Yes, no issues at all.
emc_2 said:
Yes, no issues at all.
Click to expand...
Click to collapse
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
pvsgh said:
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
Click to expand...
Click to collapse
Have no idea on how to do any of the above, but I'm googling now. Are there any guides/articles on how to do this, that You could point me in the direction of? Since I'm soft-bricked, is there any point in trying to back-up my presumably borked ROM? I've already downloaded my country specific, stock 4.1.2. ROM.
Many thanks for taking the time to help me and I apologize for the noob questions. I know my way around Windows, but when it comes to Android - I'm hopeless
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
emc_2 said:
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
Click to expand...
Click to collapse
OK so now you have a working TWRP recoveryand you also know what was causing ODIN to fail.
Next step would be to install a custom ROM, check the development section.
if you prefer stock then you ODIN your stock tar file which you downloaded.
Using TWRP, I backed up; EFS, Boot, Cache, System and Data. After the backup completed I followed the prompt to reboot and it booted into Android *happy dance*.
looks like all the user preferences are gone. No more password or background pictures and all apps have been removed from their folders. Basically looks like all the apps that I installed are there and any data associated. But all my preferences and set options are gone.
Going through the apps, I remembered that I had rooted using Framaroot. Do you think that may have been the cause for the soft-brick? Should I un-root and then try the factory reset again or just flash the stock ROM that I downloaded?
EDIT: didn't see your reply when I started typing this out. Since TWRP is flashed. Does that mean it has replaced whatever recovery Samsung had in place? If so; does having it installed/flashed increase the chance of a fairly stress free recovery in case of future problems?
So, it turns out pvsgh is pretty awesome!
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
i.imgur.com/j9neU0B.png
emc_2 said:
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Added!!
Removed!!
i.imgur.com/j9neU0B.png
Click to expand...
Click to collapse
You can take a backup that you can use to restore your tablet if you ever get issues again.
Or just follow the same procedure again.
Taking backup is completely a user choice whether he want it or not.
Hi there!
I recently bought a N3N (N7505) :good: for mobile drawing. Since I bought it used, I found KNOX at 0x1 and the 4.4.2 it came with was already annoyingly buggy (lags everywhere, packed RAM & phone app FCs). I did manage to root it through CF-Autoroot (I think?) and even put a custom recovery (TWRP touch v2.8.7.0)
The problem is, everytime I download a ROM from Sammobile (md5 checks confirm undamaged downloads), it fails to flash via ODIN (flashes ALL THE WAY till the end and says FAILED - phone reboots perfectly to previous OS like nothing happened) and I'm wondering if I downloaded the wrong ODIN files, or is there something I'm missing?
So, i'm currently on N7505XXUCNL1 and wondering how I can reflash it (or a similar one) to refresh the phone anew :angel:
ROMz, Y U NO FLASH???
Any advice on what ROM would best suit me to refresh my N3N with???
:victory::victory::victory:Thanks in advance!!:victory::victory::victory:
UPDATE:
When i'm in Download mode, this is the information displayed
ODIN MODE
PRODUCT NAME: SM-N7505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
AP SWREV: (2)
The ODIN log for when I try to flash N7505XXUCNL1_N7505OXXCNL1_TPH is here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The ODIN log for N7505XXUCOE1_N7505SWCCOF1_SWC is here:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I'm stuck on the Firmware update encountered an issue. Please select recovery mode in Kies and try again
can you provide us the log?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
The ODIN failed flash log??
Where do I find that?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
Greetings damadikaz,
I have posted my ODIN logs as an UPDATE on the main post for two separate flashes that both failed.
Any help is greatly appreciated:highfive::highfive::highfive:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
audit13 said:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
Click to expand...
Click to collapse
Oh WOW!!! It could be!
Thank you very much:laugh:
Going to download tonight and flash :good::good::good:
Will return with feedback!
Thanks again good sir! :highfive::highfive::highfive:
Hello XDA, Thank you very much.
So I have a Note 2 (N7100) 3G version running on CM12 (6.0.1) not recently flashed, I have been using for a month or 2 now. Everything seemed great and all.
Until, Last night I had a bit load on my phone, running 3G + Wifi Mobile Hotspot + GAME, and usual (Yeah, it was bad of me :3) suddenly my phones crashes and goes in boot loop. Next thing i did, went into recovery wipe all, reboot, but still boot loop. I then flashed the same ROM I did before (6.0.1) CM12 thinking maybe a fresh flash will work this, but still no luck, rather I was stuck with "patching system image unconditionally" and then verifying something which took forever so i had to pull battery. Now, I need help, Please suggest something. I can still access Recovery.
Regards,
Khurry!
as suggested by one the member here, I downloaded latest firmware from SAM and flashed using ODIN. Logs here
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Still im boot loop. Any suggestion?
Did you perform a factory wipe before booting the newly- flashed rom for the first time?
Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Hello razvanells. Sorry for taking advantage of your topic, but I'm having the same problem as you.
This also happened with the S4 Mini (but I9192 version) of a my friend. This device had no root and had a stock rom. He hung up and did not turn on anymore, locking on the screen Samsung Galaxy S4 Mini I9192. I downloaded the stock rom from the sammobile site and installed it by Odin. The log I received was identical to yours, saying that the installation occurred successfully, but when the device reboots it goes to recovery mode and it does not start, I can only enter the download or recovery mode.
I tried the hard reset and received the following error:
Formatting / data ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formating / cache ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete.
Click to expand...
Click to collapse
I tried to recover the stock rom using Kies but it did not work either.
After a lot of research on google, I found a guy saying he was able to recover a smartphone using TWRP and formatting the memory in FAT and then reformatting it to EXT4 (at that link: http://forums.androidcentral.com/t-...850-encrypted-phone-freezes-when-turning.html).
I tried to install TWRP by Odin, which according to the log occurred perfectly, but after restarting the device the Android default recovery was there (even entering the recovery mode as soon as the phone rebooted).
I tried to install the CWM for Odin, and so it was. Odin's log said it was successful but when the phone was rebooted there was the default Android recovery again (even entering the recovery mode as soon as the phone rebooted).
I have no more ideas, and I wanted to ask if anyone knows how to solve this?
Thank you.
razvanells said:
Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
même problème que vous