Related
here's the tar.md5 for gt-n8013 4.1.2
please hit the "thanks" button if this helps you...
*edit*
Now available from SamMobile:
http://www.hotfile.com/dl/189250443/e35a3d8/N8013UEUCMA3_N8013XARCMA3_XAR.zip.html
Just curious is this routed or modified in any way?
Sent from my GT-N8000 using xda app-developers app
ckavvouras said:
Just curious is this routed or modified in any way?
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
this is the tar.md5 straight from kies. you can use cf-auto-root to root:
http://forum.xda-developers.com/showthread.php?t=1957002
I am rooted with the German 4.1.2, how do I install the US version? I am a noob so sorry for my ignorance in advance.
I was on Deodexed N8013 ROM by Darkman LK8.
I downloaded the link, extracted using ex file explorer, flashed it with mobile Odin,
And baaaaaaaang JB4.1.2
Wonderful, amazing Rom
Facebook and YouTube added to multi window.
N.b no need to to factory reset if coming Darkman N8013 Rom, just wioe davlik.
Sent from my GT-N8013 using Tapatalk 2
mohammedsarhan said:
I was on Deodexed N8013 ROM by Darkman LK8.
I downloaded the link, extracted using ex file explorer, flashed it with mobile Odin,
And baaaaaaaang JB4.1.2
Wonderful, amazing Rom
Facebook and YouTube added to multi window.
N.b no need to to factory reset if coming Darkman N8013 Rom, just wioe davlik.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
I have the file downloaded and tried to use Odin but it fails every time. What am I doing wrong or not doing at all?
You need to extraxt the file from zip format. I did it using mobile odin, retained root and still have all my apps. THANX OP!
Have you extracted the RAR file to MD5.TAR?
and whats your original Rom?
Sent from my GT-N8013 using Tapatalk 2
mohammedsarhan said:
Have you extracted the RAR file to MD5.TAR?
and whats your original Rom?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
This is the message I get:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry to be such a pain. I am using the German 4.1.2. I installed it using Odin. I find the file in the PDA section on the right side of Odin and click start.
tarheels55 said:
This is the message I get:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Sorry to be such a pain. I am using the German 4.1.2. I installed it using Odin. I find the file in the PDA section on the right side of Odin and click start.
Click to expand...
Click to collapse
It seems that you don't have Samsung USB driver installed. Connect your tablet in the normal mode to ur pc ( not download mode) the drivers should be installed automatically.
If not, you can google it, and install them before going to download mode.
About coming from german Rom, I think it will be flashed successfully, without Data Wipe. I'M NOT SURE , AS I DIDN'T TRY IT. I tried PREVIOUSLY flashing N8013 LK8 Deodexed Rom over German N8010BLK9, Succeeded without data wipe. Then, before a while, I flashed this Wonderful 4.1.2 ROM.
Sent from my GT-N8013 using Tapatalk 2
Hmm.. anyone try just pushing this from Odin without a data wipe? As in, if you are on the N8010 4.1.1 ROM, were you able to push this without messing up..?
This downloaded an empty zip file. I tried it 3 times to check. Anyone else experience this issue?
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
Can someone throw up a mirror?
Any chance of it working on GT-N8010?
I'll upload to mediafire once i download it.
Sent from my GT-N8000 using Tapatalk 2
Tried 4 times now to download and failed every time. Guess i'll wait for someone else to upload it.
I'm flashing this using PC odin and it's stuck at system.img
Help?!?!?
I have that problem from time to time when flashing with odin, changing pc usually Fixes the problem
Sent from my GT-N8000 using xda app-developers app
Alright so I unplugged it then had the "firmware upgrade encountered an issue please select recovery mode in kies and try again" error whenever I boot, so I tried to get it to download mode and it worked and odin recognized it, reflashed the rom and it worked
Q9Nap said:
here's the tar.md5 for gt-n8013 4.1.2
please hit the "thanks" button if this helps you...
http://www.adrive.com/public/U7ukpH...013XARCMA3_813049_REV00_user_low_ship.tar.zip
Click to expand...
Click to collapse
Thanks!! Flashed it with mobile Odin and worked great.
Sent from my GT-N8013 using xda app-developers app
I tried to flash my 8010 and I got a FAIL at the end. I tried again with the same results. It also increased my binary count so I wouldnt suggest trying this if you have the 8010.
gpgalanis said:
I tried to flash my 8010 and I got a FAIL at the end. I tried again with the same results. It also increased my binary count so I wouldnt suggest trying this if you have the 8010.
Click to expand...
Click to collapse
It's likely to have a different boatloader, so that's prob why it failed.
Sent from my GT-N7000 using Tapatalk 2
This has been a long day...
I previously rooted my N900V Note 3 using the Root_de_la_Vega method. Everything was fine until last night when I stupidly accepted the OTA update from Verizon. I lost root because I forgot to persist Super User. Without thinking I started to reroot using the original Root_de_la_Vega method. The ODIN attempt failed.
This is the message stream from ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> SingleDownload.
<ID:0/004> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the top of my Note 3 it says SECURE CHECK FAIL : cache
My phone will now only boot into ODIN download screen, and gives me the message: "Firmware upgrade encountered as issue. Please use Software Repair Assistant & try again."
My guess is that I have tried to flash/download a mismatched ROM.
Any suggestions on how to get past the ODIN boot screen and back into normal operation?
Any help would be appreciated, obviously...
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
How/where do I find the PIT file?
http://forum.xda-developers.com/showthread.php?t=2483380
NeoMagus said:
http://forum.xda-developers.com/showthread.php?t=2483380
Click to expand...
Click to collapse
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
cmubigguy said:
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
Click to expand...
Click to collapse
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
NeoMagus said:
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
Click to expand...
Click to collapse
I guess I'll just wait for a safe way to root post-OTA. I can live with no root for a while. Thanks for helping out, I shot you some cash for your time and not making me feel like a complete idiot.
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
I just tried what rhymes with bingo, and it didn't work. It's likely because I just took the OTA straight away without using Kies or unrooting through SU. What was your unroot/re-root method?
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
NeoMagus said:
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
Click to expand...
Click to collapse
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
cmubigguy said:
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
Click to expand...
Click to collapse
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
NeoMagus said:
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
Click to expand...
Click to collapse
Do now. It turns out I needed to reboot my laptop after I installed Kango.
I'm back rooted!
I wasn't previously rooted. I took the OTA then rooted with bingo. Then installed safe strap with no problems.
Sent from my Galaxy Note 3
NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
This worked for me, I flashed the pit for MJ7 and was able to get out of soft brick
Had the same issue, resolved with .pit solution above. Can we include a note in the N900V Root de la Vega instructions? IE: If you have update to Baseband version N900VRUBMJ7, attempting to flash through Odin will fail on cache writing.
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
kalagula said:
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
Click to expand...
Click to collapse
After you install Kango, don't enter the download mode, just boot the phone as normal and make sure USB debugging is on. Attach the phone to Kango, and it will download and install the necessary drivers. Once those are done, you can attempt to root, but it likely won't take. Restart your computer, and then reattach the phone. Try to root method again, and it should work. That's what worked for me.
cmubigguy said:
Try to root method again, and it should work.
Click to expand...
Click to collapse
Yeah, mine just sits there for a while, after which it says "ROOT failed! NotSupport". Bummer!
Edit: after 5 tries, it worked. Still got the ROOT failed error, but I did get root! Thanks for your help.
Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks
FreeeMans20 said:
Cheers!
I recently flashed CyanogenMod 11 on my N9005. The thing is i'm not happy with it and i want to revert back to a stock rom. So what i was wondering is if i have to revert to the exact old version (4.3) or i could flash a stock KitKat firmware from SamMobile and how can i do that? I read a thread where a guy bricked his phone when trying with cwm cause he had some files missing. I know most users are sick of noobs like me asking this kind of questions but i would much appreciate if someone could help me out.
Thanks
Click to expand...
Click to collapse
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
http://nasirtech.blogspot.co.uk/2014/03/n9005xxuenb7-android-442-kitkat.html
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.
Cheers
vtec303 said:
Follow the instructions on the link, also there is a link on that page which takes you another page how to root N9005XXUENB7 which is the latest firmware for samsung galaxy note 3 SM-N9005. Please make sure you follow the instructions carefully and you have the right model international Note 3 SM-N9005,
The above method is for bringing the phone to factory stock. If you just want to revert back to a samsung rom and your phone is rooted with custom recovery, which I presume it is, you can just flash a samsung rom of your choice there are plenty to choose from and every rom thread have instructions how to flash their rom
Hope this helps, all the best.
Click to expand...
Click to collapse
Cheers man. I'm downloading as we speak. Hopefully i'll come back with good news.
No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.
Problem in Odin
vtec303 said:
No problem mate, I am sure the process will go butter smooth but let us know if you come across any problems , all the best.
Click to expand...
Click to collapse
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?
FreeeMans20 said:
So, like yesterday, Odin fails on me. At the very end. When the green loading bar is full and it seems like it's going to succeed, the last line says failed. The phone has CWM 6.0.4.7 flashed and CF AutoRoot. Any ideeas?
Click to expand...
Click to collapse
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Thanks
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Downloading as we speak. I'll give it a try when done. I'll let you know!
Same
vtec303 said:
ok that NB7 is failing on me as well for some reason, but in the mean time to get your phone back on line download NB4 (link below) and flash using odin 3.07, thats what I did and got no errors phone booted with no problems, if it takes too long to boot after flashing or goes in a boot loop enter recovery mode (home+power+vol up) and do data/factory reset and clear cache but that will wipe the internal storage, hope this will work
http://samsung-updates.com/device/?id=SM-N9005
Click to expand...
Click to collapse
Same thing. This is what i'm getting every time i try to flash a ROM.Any other suggestions? Vtec303, can you please tell what are the exact steps you took to flash it? Thanks
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005AUTENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk
Another thing is your phone a 16GB model ?, or is it 32 or 64GB, cheers.
It's actually 32GB. I'm just after realizing. Would that be the reason why it's not working?
Sent from my SM-N9005 using xda app-developers app
Thanks
vtec303 said:
ok sorry to hear that mate, give one more try with NB3, hopefully that should work, fingers crossed
If that fails than try this:
http://forum.xda-developers.com/showthread.php?t=2613374
That guys phone is a Hong Kong model but the files he is using to flash are compatible with international Note 3
SM N9005.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks man. FeralFire's tutorial helped me a lot. That was the only way i could flash a custom ROM. And thanks for opening my eyes and reminding me about the size of my phone. For some reason, i got stuck to thinking that my device has only 16GB. Cheers and a big Thanks for your help!
No problem ur welcome, I am glad your phone is back online mate and I hope it stays that way , all the best, tc
Sent from my SM-N9005 using Tapatalk
Hello,
I am trying to update the recovery on my wife's S4.
I'm following these instructions, but I can't seem to get it to work in either Terminal Emulator or ADB. Any instructions will be much appreciated.
Originally Posted by stevey500 View Post
I am on locked-bootloader MF3.
I have had a broken/non-bootable recovery menu since I started tinkering with modifying MF3 bootloader.
I followed this guide and did it all within my stock rooted touchwiz rom using terminal emulator and it worked perfectly. I didn't even have to run the last .sh, just simply dd'd the stock recovery.img image to its appropriate location.
So, bootable people with MF3 bootloader and broken recovery menus... do this:
http://d-h.st/AuY put this image file on your internal storage.
Run this command in ADB (type adb shell to get to shell) or go to terminal emulator and enter this:
su -c "dd if=/storage/sdcard0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
You should have a fully working stock recovery menu now.
Click to expand...
Click to collapse
tarikakleh said:
Hello,
I am trying to update the recovery on my wife's S4.
I'm following these instructions, but I can't seem to get it to work in either Terminal Emulator or ADB. Any instructions will be much appreciated.
Click to expand...
Click to collapse
What boatloader/baseband are you on. Also what version of android. Depending on what you're on this may not apply to you.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
When you say update, do you mean flash the stock recovery or a custom one? Because this method is only to restore the stock recovery. You can't get a custom one.
Sent from my SGH-I337 running GPE
drock212 said:
What boatloader/baseband are you on. Also what version of android. Depending on what you're on this may not apply to you.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't have the phone with me right now, but I know it is 4.2.2 MF3.
DeadlySin9 said:
When you say update, do you mean flash the stock recovery or a custom one? Because this method is only to restore the stock recovery. You can't get a custom one.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
Stock recovery. I am trying to update without losing data. I was advised to unroot, then update OTA but update wasn't working, no response when checking for update.. Problem is at one point I tried to flash TWRP through Goo and I broke stock recovery, which I need now to update.
tarikakleh said:
Stock recovery. I am trying to update without losing data. I was advised to unroot, then update OTA but update wasn't working, no response when checking for update.. Problem is at one point I tried to flash TWRP through Goo and I broke stock recovery, which I need now to update.
Click to expand...
Click to collapse
There's somewhere around here where someone posted just the recovery partition of the odin tar file. That can be flashed through odin and you'll regain your recovery. The reason ota doesn't work is because it needs recovery to install... Google search how to recover stock recovery for nb1 or whatever bootloader you're on and an XDA thread should come up
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
There's somewhere around here where someone posted just the recovery partition of the odin tar file. That can be flashed through odin and you'll regain your recovery. The reason ota doesn't work is because it needs recovery to install... Google search how to recover stock recovery for nb1 or whatever bootloader you're on and an XDA thread should come up
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
su -c "dd if=/storage/sdcard0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.
tarikakleh said:
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.
Click to expand...
Click to collapse
Ok cool you found the tar file... This can be flashed through odin actually and it will restore your recovery without touching anything else or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions. Before placing there though just rename the img file to recovery or just leave it as is and remember it. The string would be as follows
Su -c dd if=/storage/sdcard0/whatever you named the duke. of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give that a try again since its a tar file it can be flashed through odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
tarikakleh said:
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.
Click to expand...
Click to collapse
The .tar.md5 file looks like it's an Odin flashable file. To use the dd command you need the .img file. recovery.img I'd probably in the.tar.md5 file but I'm not familiar with it. Do you have a link to the mf3 tar file?
Sent from my Nexus 5 using XDA Free mobile app
drock212 said:
Ok cool you found the tar file... This can be flashed through odin actually and it will restore your recovery without touching anything else or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions. Before placing there though just rename the img file to recovery or just leave it as is and remember it. The string would be as follows
Su -c dd if=/storage/sdcard0/whatever you named the duke. of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give that a try again since its a tar file it can be flashed through odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome thanks! I'll let know what happens. Need to get my hands on wife's phone first.
jd1639 said:
The .tar.md5 file looks like it's an Odin flashable file. To use the dd command you need the .img file. recovery.img I'd probably in the.tar.md5 file but I'm not familiar with it. Do you have a link to the mf3 tar file?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the link. http://d-h.st/AuY
drock212 said:
...or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions...
Click to expand...
Click to collapse
Seems like I need my hand held with every step of this process!
To extract the img from the tar, I did the following:
1) extracted with 7-zip
2) left me with a "recovery.bin"
3) dropped that file into sgs2oext4
4) in diskinternals linux reader, I select "mount image"
For step 4, I don't get a mount.
I think the problem is with step 3, the recovery.ext4.img file is 0KB, I've left it running on sgs20ext4 for at least 30 minutes and nothing changed.
How am I screwing up?
tarikakleh said:
Seems like I need my hand held with every step of this process!
To extract the img from the tar, I did the following:
1) extracted with 7-zip
2) left me with a "recovery.bin"
3) dropped that file into sgs2oext4
4) in diskinternals linux reader, I select "mount image"
For step 4, I don't get a mount.
I think the problem is with step 3, the recovery.ext4.img file is 0KB, I've left it running on sgs20ext4 for at least 30 minutes and nothing changed.
How am I screwing up?
Click to expand...
Click to collapse
You might only be able to use odin to flash since its a tar file already
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
You might only be able to use odin to flash since its a tar file already
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will this preserve the data/settings on the phone?
tarikakleh said:
Will this preserve the data/settings on the phone?
Click to expand...
Click to collapse
I read on another forum where the same tying happened to another guy and he flashed just the bootloader through odin and it did not touch any of the other partitions (data/settings) but since I have not done this myself I can not guarantee it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
If you flash recovery in Odin it will not wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you flash recovery in Odin it will not wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Tried flashing using ODIN 1.85 and I get FAIL!. "Auto Reboot" and "F. Reset Time" are checked.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf3-recovery.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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tarikakleh said:
Tried flashing using ODIN 1.85 and I get FAIL!. "Auto Reboot" and "F. Reset Time" are checked.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf3-recovery.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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try a different usb port and cable. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try a different usb port and cable. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...
tarikakleh said:
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...
Click to expand...
Click to collapse
Try odin 3.09 could just be the version of odin being weird
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 10:13 PM ---------- Previous post was at 10:03 PM ----------
Ok dumb question but I have to ask... You put the phone in download mode (power off... Then power on holding volume down home key and power) then plugged it in while odin was up? If so then try this
http://forum.xda-developers.com/showthread.php?p=46775016
Stock recovery img file for mf3 and adb instruction on how to install
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:13 PM ----------
tarikakleh said:
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...
Click to expand...
Click to collapse
Found it!!!!! Ok using odin 1.85 you can flash each part of the firmware separately. Put phone in download node plug into pc while running odin and flash just the recovery but put it in the recovery slot of odin
http://forum.xda-developers.com/showthread.php?p=46943588
This helped me when I did the same thing as you while on mf3
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I'm not exactly green her, but i tried to run wicked v4 rom using safestrap to install. I am soft bricked, am able to acces recovery, download mode. I'v searched and downloaded, redownloaded, and downloaded again a list of packets that, when used with din will allow me to down grade to mk2 i believe so that i can access my device and start the process over again. I can not for the life of mrick my deice that has been down 2 dayse find the right mirror that will allow me to unbrick my device that has been down 2 days. help please, and it is appreciated.
p.s
i can not access the SS home screen and i do have a nandroid back up. thanks in advance
half way there
got beyond that point.. now odin keeps failing during the flashing process.
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What firmware version where you on? You may not be able to flash mk2
Sent from my Nexus 5 using XDA Free mobile app
frmware
jd1639 said:
What firmware version where you on? You may not be able to flash mk2
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i was on i337nc1 firmware......
i had tried to flash wicked rom, and it is sayng that i need to connect to kies to reinstall custom firmware but kies is not registering the phone at present
zavien said:
i was on i337nc1 firmware......
i had tried to flash wicked rom, and it is sayng that i need to connect to kies to reinstall custom firmware but kies is not registering the phone at present
Click to expand...
Click to collapse
Alright, some of this will help http://forum.xda-developers.com/showthread.php?p=55338138
Download the nb1 tar file. Flash that in Odin
Sent from my Nexus 5 using XDA Free mobile app
thanks
jd1639 said:
Alright, some of this will help http://forum.xda-developers.com/showthread.php?p=55338138
Download the nb1 tar file. Flash that in Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
downloading it now!!! much appreciated in advance