Related
Hi guys,
Got my Korean LTE (SHV-E250s) yesterday and thought I'd root it so I can install a new English OS on it (Cleanrom Ace 4.5).
I followed Chainfire's thread on how to root my phone (http://forum.xda-developers.com/showthread.php?t=1933542).
So, first I downloaded Odin3 v1.85 and CF-Auto-Root-t0lteskt-t0lteskt-shve250s.zip.
Extracted both and managed to install CF Auto Root with SuperSU v1.05.
Sweet, everything was going well.
Then I found Cleanrom Ace 4.5 and its thread (http://forum.xda-developers.com/showthread.php?t=2055170).
So I installed Goomio from the play store and downloaded the current version of "twrp".
Now, here is where I stuffed up bad because I didn't make a backup.
I copied the zip file of Cleanrom Ace 4.5 onto my micro SD as well as the internal storage.
I booted the phone into twrp and went to factory wipe and reset. I got a little bit worried here because this is where things go wrong.
I went ahead and did it, rebooted to twrp again and installed Cleanrom Ace 4.5.
I got to the options and it was looking hopeful. Chose stock or custom animations to boot up, apps to install, etc.
Then it went to installation screen showing the progress and it stayed on 0.0% when it was trying to install the boot up animations.
After about 2 minutes or so it would reboot. I would try and install the ROM again but each time I got the same thing.
I tried rebooting normally but then twrp told me that I didn't have an OS to boot to. Uh oh.
After doing another wipe and reset, I could access the download mode (vol down+home+power) and the other mode, which I'm not sure if it's recovery mode? (vol up+home+power).
I tried using Odin3 v1.08, v.3.04 and 3.07 to load up some stock ROMs (N7105ZHDMB1_N7105ZZHDMB1_N7105XXDLL5_HOME.tar.md5, N7105XXDMB2_N7105TMHDLK8_N7105XXDLL5_HOME.tar.md5, and N7105XXDMB2_N7105VNZDMA2_N7105XXDMA1_HOME.tar.md5).
I tried using different USB ports and different computers. Each time I would get a red 'FAIL' screen in Odin3.
Below is an example of the message I'd get from Odin3 v3.07:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105ZHDMB1_N7105ZZHDMB1_N7105XXDLL5_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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? My phone gets stuck on the "Samsung Galaxy Note II" window and doesn't progress. I hold down the power button and it just reboots to the same window. I can get to download mode and what I think is recovery mode.
Any guidance is very appreciated. I have read around the threads and I know this isn't a hard brick so there may be some way to resolve this.
Cheers
Maybe this will help you or wait for Dr.Ketan to help you is a real doctor.
http://forum.xda-developers.com/showthread.php?t=2143515
adinfsfocus said:
Maybe this will help you or wait for Dr.Ketan to help you is a real doctor.
http://forum.xda-developers.com/showthread.php?t=2143515
Click to expand...
Click to collapse
Hi there, thanks for the link. I'm glad your issue was resolved.
However, I don't think I created a backup, so I couldn't just do a backup through recovery.
I can't reinstall any of the stock firmware I've downloaded as it says 'failed' every time in Odin3.
Update: I can't get into recovery mode now.
1. Even I had the same situation wen I ran megawipe script but stock rom installation in download mode gave life to my phone...
So first try installin wit different versions of odins and roms..
2. May be the whole internal memory lost all the partitions into which the files could be flashed.. 'wipe data factory reset' in recovery would have put them back ..but since ur phone recovery too is lost search for a tool which can put them back as I remember readin about such a tool... will search too..
Sent from my GT-N7100 using Tapatalk 2
maloolaba said:
Hi there, thanks for the link. I'm glad your issue was resolved.
However, I don't think I created a backup, so I couldn't just do a backup through recovery.
I can't reinstall any of the stock firmware I've downloaded as it says 'failed' every time in Odin3.
Click to expand...
Click to collapse
Try instal a costom recovery after you instal costom recovery with Odin (make a full wipe,format system,partition,wipe cache and dalvik) then download a costom rom and put on external SD card if you have if not borrow one or buy one and instal the rom from external Sd card.
I hope you solved.
adinfsfocus said:
Try instal a costom recovery after you instal costom recovery with Odin (make a full wipe,format system,partition,wipe cache and dalvik) then download a costom rom and put on external SD card if you have if not borrow one or buy one and instal the rom from external Sd card.
I hope you solved.
Click to expand...
Click to collapse
Would I still need GooManager or Terminal Emulator to install a custom rom like twrp? Because I can't install apps like GooManager or Terminal Emulator as my phone is bricked.
edit: Tried installing TWRP recovery using this hxxp://androidlegend.com/install-twrp-recovery-2-3-1-1-on-galaxy-note-2-n7100/ but Odin3 kept crashing every time I hit "start". I don't know if it's because my phone is an SHV-E250S and not a n7100 or what?
double edit: Update. I can get recovery mode again! Weird.
Options are:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
So I went ahead and selected "wipe data/factory reset". Rebooted and still the same.
Oh man!
So I've tried the method in this thread (http://forum.xda-developers.com/showthread.php?t=2040264) for Verizon Note 2 and I had a minor progress.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The progress bar underneath where it would say PASS or FAIL actually said something, ie. Boot, which is something that hasn't happened with the stock ROMs I've tried in the first post. Now I just need a stock from for the SHV-E250s that will work!
Upon rebooting, it adds to my flash number, so it is writing, but not completing the install.
Has anyone got any ideas I can try?
maloolaba said:
Has anyone got any ideas I can try?
Click to expand...
Click to collapse
Try contact dr.ketan is a master:good:
http://forum.xda-developers.com/showthread.php?t=1896696
After wipe data/factory reset in recovery did u try changing into download mode n flashin rom through pc odin ???.. plz try it if u have not..
Sent from my GT-N7100 using Tapatalk 2
hkkanha said:
After wipe data/factory reset in recovery did u try changing into download mode n flashin rom through pc odin ???.. plz try it if u have not..
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did just that. Still no luck. Is this possibly because there isn't much support for the SHV-E250s in terms of recovery ROMs and Odin3?
A recovery ROM for N71000 was able to begin writing on my phone, thus increasing flash count, but failed at the beginning in Odin3.
I don't know if it's a ROM problem or a phone problem or an Odin3 problem?
Noob here, btw.
these stock ROMs that you have tried are not for galaxy note 2 korean version/shv-e250s..
try this latest stock ROM/firmware for shv-e250s : E250SKSVME1_E250SSKTVMAA_SKT.zip
get it from sammobile
m41n54j4 said:
these stock ROMs that you have tried are not for galaxy note 2 korean version/shv-e250s..
try this latest stock ROM/firmware for shv-e250s : E250SKSVME1_E250SSKTVMAA_SKT.zip
get it from sammobile
Click to expand...
Click to collapse
Please help, i really need pit file for SHV-E250s. I softbrick my phone. Please
tuannghia1985 said:
Please help, i really need pit file for SHV-E250s. I softbrick my phone. Please
Click to expand...
Click to collapse
Plz donot Install N7100 or N7105 Stock Rom on your SHV-E250S, Download Samsung Official Stock Rom from the link given Below and flash it through PC ODIN http://www.sammobile.com/firmwares/1/?model=SHV-E250S&pcode=SKT#firmware
I figured I would post this as a basic how to for people who brick their phones because they are in a similar situation.
Sprint Samsung Galaxy Note II SPH L900
Used this root method because it was for Samsung Note II owners who already had Android 4.3.*,
http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-sprint-sph.html
Installed TWRP but it didn't stick to Download mode. I could boot into TWRP when my phone was up even after rebooting but could not boot the device directly into TWRP to access my custom recovery image.
Installed Perseus and Macks Rom AllStar V5.0 after saving them to my SD Card and did this after booting into TWRP from within my stock ROM.
Like an idiot I didn't read all the comments on ChainFire 3D when I was searching root 3d because I'm on a big kick right now of making it all 3d like.
Instead of flashing ChainFire 3d from recovery I used my in rom option since I had all my root programs running nicely and thought why not its just a button click instead of rebooting into TWRP. There was my mistake.
Alright so now I am bricked out of my phone in a boot loop. Nothing is happening but ChainFire said when you install not to freak out if your phone hangs for awhile, pull the battery after two minutes. Well I did and still bricked in a boot loop.
Scour the forums and Internet because I know I still have access to my phone through Odin. I don't have debug mode turned on so I can't even create an ADB shell to my device. That was my first through, run ADB shell, launch TWRP and restore my custom recovery. Would have worked except I had no way of getting to TWRP. Tried installing the Samsung ToolKit. Couldn't recognize my device.
Opened Odin back up and thought why not try to flash TWRP and have it reboot, maybe TWRP will launch. Well I don't know if that would have worked or not because every time I tried to reflash TWRP Odin encountered an error.
Alright, abandoned that idea and did some more research. I knew I could still flash to my phone but I didn't have anything to reset the caches to install another ROM and I didn't want to install something else where things could go potentially worse. I needed my damn phone back. Boom! Found some very helpful articles on restoring to stock and found the stock recovery one click solutions.
I am making this so lengthy in case you are going through something similar where you are stuck in a boot loop, locked out of TWRP but can still flash to your phone with Odin.
These two threads were massive help and they take you to the file locations:
http://forum.xda-developers.com/showthread.php?t=2116490
http://www.sxtpdevelopers.com/showthread.php?t=154
I restarted my phone in download mode which was a little tricky because when I put the battery in it would start booting. Had to make sure volume down, home and power were pressed while sliding the battery in. It's tricky but you can do it with one hand and use the other to insert the battery. Don't give up just because if you put the battery in your phone automatically boots!
I used this specific file. http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
I didn't know if my phone was MA5 or MA7. I was worried that something would be off if I downloaded the wrong one but I chose MA5 oneclick exe and it did the trick. I used the Rooted version that didn't delete my data so when the phone came back on all my changes were still there. Everything from the kernel was gone but my settings and etc were unaffected.
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
So anyways, there are some resources and an additional thread. I'm pretty tech savvy but when the damn thing bricked I wasn't for sure what to do. Hopefully this is semi helpful for someone.
*Cliff Notes:
If you brick yourself out of your Sprint Samsung Galaxy Note 2 (II) and you can't access recovery, go download one of these oneclick solutions from sextape or garwynn (big ups to you guys) and reflash it from download mode using their programs. If you rooted your phone using Odin you will feel right at home with their software and it is no big deal. Phone will be back up in no time.
Edit: So after I got back to my stock ROM and tried to reflash my previous roms they wouldn't stick. E Signature verification kept failing but I still had root. Used CWM Recovery straight out of the app store and rebooted in recovery. Wiped everything. Used the esignature toggle and disabled it. Bam was able to reinstall roms and I am back to tinkering
The title was misleading. I thought you meant a hard brick. What you encountered was a soft brick aka bootloop. Thanks for writing it up for the noobs though.
Sent from my SPH-L900 using Tapatalk 4
Yes title is misleading but great post for us thats need it
Thank u much for ur time to make this
SGN2
I bricked my sph l900 also..I had 4.3 rooted then went to jellybomb had a back up of my 4.3 rooted. Flashed back to it and it's now stuck in note 2 animation. Can't get into recovery or adb. Plz can anyone help ?
Sent from my SM-N900P using xda app-developers app
Is there a fix ?
Sent from my SM-N900P using xda app-developers app
odin oneclick failure
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<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 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>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
kevo7000 said:
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<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 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>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use the original Samsung USB cable.:good:
new battery issue
gizmoscoop said:
You need to use the original Samsung USB cable.:good:
Click to expand...
Click to collapse
I used every cable I owned oven the original cable for my Note 2. I ended up taking it to sprint and replaced it. With this new note I've had two batteries completely fry. 100 % but will not power on without charger.smh
What is it that you did when the onclick kept failing?!!?
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
I keep running the NA5 Stock NoData exe and it keeps failing
It maybe a noob question, and I maybe in the wrong section, but here it goes
I own a T-Mobile Galaxy s4 (m919)
Whenever I tried to install any rom by using CWM or twrp,
I always get
Kernel Is not seandroid Enforcing........ etc.
and then it restarts and takes me to the recovery again
Whatever rom I try to install, I end up at this.
Currently I am on 4.4.2 M919UVUFNK2 rooted with CWM
Please help me, I am really crazy about the 5.0 roms :crying::crying::crying:
Unfortunately I just got myself in the same boat as you, I tried to ODIN the phone back to stock per this guide; http://forum.xda-developers.com/showthread.php?t=2258628
This has been unsuccessful, the phone keeps booting looping these messages.
Update CWM or TWRP to latest version. Try formatting system partition from "advanced wipe" and reboot back into recovery to try flashing.
As for Odin restore. Don't try flashing an image that contains a bootloader older than what is on the device.
If (full) MDL has been flashed MDB will fail...and so on. Try the 4.3 or 4.4 restore image instead.
noticed it was the MDL restore guide being followed. So if it is failing try 4.4.2 or 4.4.4 odin image
The message is normal. For the reboots, update recoveries to latest version
Finallyy!!!
Thanks a lot everyone, I didn't know that updating recovery will fix the issue. I thought that whatever version of recovery it is, it is gonna work.
I was about to sell this phone, but you guys saved it
Thanks again
gurnted said:
As for Odin restore. Don't try flashing an image that contains a bootloader older than what is on the device.
If (full) MDL has been flashed MDB will fail...and so on. Try the 4.3 or 4.4 restore image instead.
noticed it was the MDL restore guide being followed. So if it is failing try 4.4.2 or 4.4.4 odin image
Click to expand...
Click to collapse
What does MDB stand for?
Additionally, although a 4.3/4.4.X rom is recommended; is there anyway to have Odin successfully flash from Android 4.4.2 (M919UVUFNB4) to Android 4.2.2 (M919UVUAMDL)? Perhaps by flashing the bootloader first?
XDAUserWork said:
What does MDB stand for?
Additionally, although a 4.3/4.4.X rom is recommended; is there anyway to have Odin successfully flash from Android 4.4.2 (M919UVUFNB4) to Android 4.2.2 (M919UVUAMDL)? Perhaps by flashing the bootloader first?
Click to expand...
Click to collapse
No. You can flash an MDL rom, but not firmware
serio22 said:
No. You can flash an MDL rom, but not firmware
Click to expand...
Click to collapse
The baseband M919UVUAMDL is only a rom? Why is it not considered a firmware? Moreover, what is the difference between a rom and a firmware?
trying to untangle the mess I seem to have made
I have the same problem as the OP and have been trying to flash back to stock. Problem is that I spend the time to download these huge files only to have them end up as a ".7z" file - which is not recognized by Odin.
I finally found one that (within the zip file) had an ".md5" file. In the process of 'unzipping' this file as we speak. *keeping my fingers crossed*
I remember reading somewhere that this had something to do with the Samsung Knox program and "tripping the knox counter" or something like that. I found forums that also said programs like Triangleaway don't work with Knox-infused devices. Is this true. . . ?
I am starting to feel like I should have paid the $40 bucks to have one of those prefab 1-click ("guaranteed") programs do this for me.
So the first scary thing was when I set the PDA in Odin (v3.07) to the .md5 file, it apparently had to do a check of its own:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.....I say "scary" because it took a while and I was not prepared for it (I thought the program had locked-up). Then again I guess anything takes a while with a 2+GB file. :silly:
So I got the phone into download mode and clicked Start, then saw the following:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> aboot.mbn
<ID:0/010> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)Based on that (and the big red "FAIL!" in the top left corner), I had the sneaking suspicion that the program was not quite as successful as I had hoped, so I unplugged the phone (the process had not been gong on for very long).
As soon as I unplugged the phone, I got that error saying there was some sort of problem with the firmware download and that I should use Kies to restore my phone. I thought "YAY! Let's let Samsung clean up my mess!!" But oh no... Kies wouldn't have anything to do with my (now) modified phone and said it was (now) not compatible.
So I tried the Odin thing again (still in process) and noticed what I thought was a graphical error of some sort under the "Do not turn off target !!!" message. I do believe that this is actually the initial tippy tip of a progress meter that is just moving at about the speed of congealed phlegm (again, as everything takes a long time with a 2+gb file).
So that is where I am for now. I figure I'll give this thing 30-40 min and see if this tippy-tip would-be progress meter becomes something a bit more profound. The problems that I have (above the obvious) at this point are:
Odin has marked this as a "FAIL!"
Odin's message box lists this as "All threads completed. (succeed 0 / failed 1)
Odin appears to not be doing anything at the moment and is waiting for my next move
The progress meter (wannabe) is not progressing
There is some microprint in the top left corner of my phone screen that reads:
(red text)ODIN MODE
(white text) PRODUCT NAME: SGH-919
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CS8-CONFIG-LS8: 0X30 (not sure about the 8s - it is very hard-to-read)
(grey text)WRITE PROTECTION: Enable
eMMC BURST MODE: enable (not sure about the "eMMC", again hard-to-read; also interesting to see the lower-case e's here)
(red text)START [224 1440]
SW REV. CHECK FAIL : fused : 5 , Binary : 1
My hopes are not high, but I will keep the faith for now to see if that progress meter grows up and makes something of itself in this world of ours. I am not sure if it is just my innately blind sense of optimism, however it seems that the tippy-tip has become a little larger in the time that it has taken to type this posting.
Then again, my marker may have just shifted. I guess we will just have to wait and see.
It is just barely 7am now and I think I need a beer already.
---------- Post added at 07:32 AM ---------- Previous post was at 07:23 AM ----------
As I am reading my posts I am getting the nasty feeling that this has seemed to turn into a thread hijacking... I will move this onto a new post and post the link here if you would like to respond.
My apologies to the OP.
---------- Post added at 08:24 AM ---------- Previous post was at 07:32 AM ----------
I created a much more detailed (and long-winded) discussion here. Please post any comments/replies there.
Again, apologies to the OP.
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Downgrade !
bawalker said:
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Click to expand...
Click to collapse
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Iceburn1 said:
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Click to expand...
Click to collapse
Well that just totally sucks. I was hoping to get down to 5.0.1 to use chainfire root. The Beastmode root kernel patch seems to have slowness and lag issues introduced after installing that kernel patch which I really wanted to avoid.
I used to do roms and such back earlier on in my smart phone days, but I've found Stock to be best, even with touchwhiz. When I root I just want root access, maybe twrp, but even that's not a requirement as the only things I use are wifi tether when on job sites and titanium backup to freeze things like knox, remove bloatware, etc. That's all I ever use root for. So I'm kinda bummed right now over not downgrading. What is Samsung thinking?!
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Kernel+Rom
bawalker said:
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Click to expand...
Click to collapse
Im using stock rom Hybrid 3.0...http://forum.xda-developers.com/note-4-sprint/development/rom-t2956667....with emotion kernel.....http://emotroid.com/touchwiz-kernel/, use app called Synapse to control kernel, link is below emotion kernel to playstore. You said you liked stock, and this will give you that and the emotion kernel is great, no lag for me at all, use synapse to fine tune it.
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
hbs131415 said:
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
Click to expand...
Click to collapse
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
samep said:
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<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> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<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> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hbs131415 said:
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<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> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<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> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what does your phone display indicate when you get this failure?
Just an observation, I think you're trying to Odin KitKat which may not be possible in Odin if you've updated to Lollipop 5.1 Other 5.0 stock tars attempted may also get blocked to downgrade of bootloader as well like my SM-N910P will. My phone won't get as far as yours did when Odin of KitKat or Android 5.0 stock tar is attempted so that may not be the issue; maybe you haven't had that phone upgraded beyond beyond Android 5.0 yet?
If you had updated to Android 5.1 or higher, you might consider trying a newer stock tar, 5.1 or higher.
They're may be a more logical reason given on your screen at time of failure.
Sent from my SM-N910P using Tapatalk
here the message in the phone
here screenshoot
samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
hbs131415 said:
here the message in the phone
here screenshoot
Click to expand...
Click to collapse
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
TheMadScientist420 said:
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
Click to expand...
Click to collapse
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
samep said:
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
TheMadScientist420 said:
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
Click to expand...
Click to collapse
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
samep said:
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
TheMadScientist420 said:
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
Click to expand...
Click to collapse
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
samep said:
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
TheMadScientist420 said:
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
Click to expand...
Click to collapse
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
samep said:
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried most of that. This thing does have a weird battery issue. Its no loss to me. I got this thing cheap the other day. I keep getting failed to repartition errors. Which seems to come back to the fail to mount system.
I hate to buy a battery. I dont buy cheappies. Due to high failure quality rateS.
I used the pit from samobiles.
Even factory recovery will wip cache. But thats when i get the failed to mount system
new update so i flashed the developer firmware minus the system and data parts. so basicly modem and other partitions included in boot and that takes every time now it litrely fails when i try to flash something to the system partition. when i flash twrp i get failure says no pit for mapping.
even the pit files is failing says there is no pit partition
id say im donr now just saw a mmc read fail on device in dl mode
So somehow I deleted everything on my device except for TWRP. I have a refurbished sapphire black 64gb Tmobile s6 edge. Is there a way I could restore it back to normal?
Commanderdrag said:
So somehow I deleted everything on my device except for TWRP. I have a refurbished sapphire black 64gb Tmobile s6 edge. Is there a way I could restore it back to normal?
Click to expand...
Click to collapse
What do you mean by "normal"?
Do you restore all the files that were deleted?
No, unless you made a back folder on another storage area, like a usb-otg flash drive or copied to your pc, those file are gone!
Have you deleted everything including the OS? Meaning your phone will not boot up?
If so, then you will need to download either the full odin tar file to Flash the stock rom using odin with your pc or download, transfer to your phone and flash a custom rom.
That's basically it.
Unfortunately unless you backed up your personal files from your phone that are lost forever.
It sounds like maybe you recently got the phone and hopefully didn't have much on it so take this as a lesson and definitely be careful when checking things in TWRP.
Good luck and sorry to hear that.
There isn't much as far as development in the Tmo S6 Edge forum, but you can check the Tmo S6 Flat forum or check the International Flat S6 forums.
My OZOP Rom is actually build from official Tmo S6 Edge firmware and would suit your devices compatibility perfectly.
Also pretty much any Flat rom will work on your device, just make sure you go slow and read all the instruction and steps posted my the OP.
We write these steps for you, we know how to install our work so again, the instructions are written for users benefit and we take no enjoyment in writing this stuff, especially if you don't read it and post problems!
Major no no! But happens all the time! Very annoying!
stangdriver44 said:
What do you mean by "normal"?
Do you restore all the files that were deleted?
No, unless you made a back folder on another storage area, like a usb-otg flash drive or copied to your pc, those file are gone!
Have you deleted everything including the OS? Meaning your phone will not boot up?
If so, then you will need to download either the full odin tar file to Flash the stock rom using odin with your pc or download, transfer to your phone and flash a custom rom.
That's basically it.
Unfortunately unless you backed up your personal files from your phone that are lost forever.
It sounds like maybe you recently got the phone and hopefully didn't have much on it so take this as a lesson and definitely be careful when checking things in TWRP.
Good luck and sorry to hear that.
There isn't much as far as development in the Tmo S6 Edge forum, but you can check the Tmo S6 Flat forum or check the International Flat S6 forums.
My OZOP Rom is actually build from official Tmo S6 Edge firmware and would suit your devices compatibility perfectly.
Also pretty much any Flat rom will work on your device, just make sure you go slow and read all the instruction and steps posted my the OP.
We write these steps for you, we know how to install our work so again, the instructions are written for users benefit and we take no enjoyment in writing this stuff, especially if you don't read it and post problems!
Major no no! But happens all the time! Very annoying!
Click to expand...
Click to collapse
I have backups of the original files on my device so I'm not worried about that, I have been trying odin and TWRP flashing and neither have worked, to clarify the phone would show the s6 edge logo go black and repeat until eventually going to TWRP. after I had booted it to TWRP once when I press power off in TWRP it would show the log go black and then go into TWRP. in TWRP I able to boot it into a download mode it only showed the ""Downloading . . ." and "Do not turn off target" and an error in the top left saying "SW. REV. CHECK FAIL. DEVICE: 4. BINARY: 1" From this screen I plugged it into my computer and tried to flash a stock rom and odin would give me the error
"<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
Once this failed I was able to turn off the phone by holding volume down + home + power. it then showed the charging image even after unplugged until I held volume up + home + power for it to boot into download mode, this time saying
"ODIN MODE
PRODUCT NAME: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0500)
RP SWREV: B:4 K:3 S:3" in the top left corner
after trying to flash the same rom with odin I got the same error in odin as the one before and another line on the phone saying "SW REV: CHECK FAILED DEVICE: 4. BINARY: 1"
UPDATE: I reinstalled the firmware using ODIN, and found the problem I was getting in download mode was due to the firmware being wrong/not compatible. the firmware that did work is found here: http://www.sammobile.com/firmwares/confirm/89343/G925TUVS4EPH2_G925TTMB4EPH2_TMB/ (posting for anyone who has this problem in the future.)
thanks to stangdriver44 for the push in the right direction.