• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stuck in recovery mode

  • Thread starter Thread starter Deleted User
  • Start date Start date
Use an Md5 check to varify the downloaded firmware. It should be provided from the site you got it from. Look for md5 or hash tag. 32 digit code of numbers and letter. I run an app on android called md5 Im pretty sure you can find a program to do te same on pc. If this results do not match. You download is corrupted.
 
MrJavi said:
Use an Md5 check to varify the downloaded firmware. It should be provided from the site you got it from. Look for md5 or hash tag. 32 digit code of numbers and letter. I run an app on android called md5 Im pretty sure you can find a program to do te same on pc. If this results do not match. You download is corrupted.
Click to expand...
I don't think it's corrupted
 
ocnbrze said:
is there anyway you can show us the output odin gives you with the Complete(Write) operation failed? maybe a screenshot or photo of it?
Click to expand...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2715 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
 
It is very important to download the correct firmware for your device and will simply say compatibility. To my knowledge wiping cache from recovery will not be the cause of a bootloop. Be a rooted user and flashing and moding I am very familiar with recovery. lol. If you are able to boot into stock recovery if yu look at the bottom of te initial page it may show soe error "DN-verity ,fail to mount efs, DRK fail or something else.
 
ocnbrze said:
odin can be finicky. maybe try a different version. also i would try a different cable.
Click to expand...
I tried loads of different cables and still got the same error. Any version of odin that isn't so finicky?
 
MrJavi said:
ocnbrze always offers good advice and and suggests installing another version of Odin may be the solution to a fail. I have to agree.
Click to expand...
So what odin version should I download? I currently have oden3 v3.13
 
ocnbrze said:
the issue is that it isn't failing at hidden.img but rather at recovery.img which i find interesting.
Click to expand...
I was focused on the complete write opertion fail but as both will recovey.img and hidden.img will end up with fail. Yes you are correct.
 
That where the "finky" part comes in as one verson of Odin may work on my Samsung device but not on yours. Begin with te latest version is a good place to start. As for I use v3.12 and v3.10 installed but v3.12 is my go to Odin.
 
MrJavi said:
That where the "finky" part comes in as one verson of Odin may work on my Samsung device but not on yours. Begin with te latest version is a good place to start. As for I use v3.12 and v3.10 installed but v3.12 is my go to Odin.
Click to expand...
Well what website should I download it from?
 
DrawsomeDrawer said:
The zip file doesn't have a tar.md5 extension. What do I do?
Click to expand...

The site page from that you downloaded the firmwares don't offer Md5? WoW
This is an example of a baseband for y device that provides a md5
Screenshot_2019-10-20-11-10-11.png
 
MrJavi said:
Firmware for your device SamMobile however free downloads a slow, slow, slow but if are able to fine the same firmware that you have already downloaded simply vopy the md5 and compare that with md5 checker. If they match them you have confemation of a valid dwnload.
Click to expand...
You lost me there
 
I tried it using a different version of odin and got stuck on <ID:0/003> NAND Write Start!!
 
You must log in or register to reply here.
Back
Top Bottom