https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Edit: Please do not try to flash the .Zip in recovery.. this is just a compressed file. Unzip and you can flash this using ODIN..
I recommend a factory reset before flashing..
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It literally just came out today for the SM-G920T so my guess is this is stock.
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
tflogic said:
what would be the best way to flash this if i'm on a custom ROM right now?
just regular flash through ODIN?
Click to expand...
Click to collapse
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
magda623 said:
Put the .tar into PDA and flash. You'll have to install your recovery again through ODIN also. I haven't been able to find a root unless you use a universal kernel in the s6 thread or in the unified development thread. I'm DL'ing now. I'll post after I try a few kernels compatible.
Click to expand...
Click to collapse
according to this post, SuperSU Beta seems to be working fine.
tflogic said:
according to this post, SuperSU Beta seems to be working fine.
Click to expand...
Click to collapse
Possibly. However, there is no recovery for our device listed on the recovery page. The fact that recovery breaks the boot.img without root sounds shaky though. I'll try it a few different ways. DL is done. Flashing now.
Zaphodspeaks said:
https://www.androidfilehost.com/?fid=24499762635997683
I posted it in the Marshmallow Update Thread..
I thought it would get lost in the mix so I wanted to give it's own thread..
Click to expand...
Click to collapse
Think I flash this on my.metro pcs version I flashed the tmobile 5.1.1 update on my metro pcs version it's basically the same phone
Maddball said:
Stock, rooted or details?
Sent from my SM-G920T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is 100 percent stock.. from Sam Mobile..
Hell it came out early this morning.. No one has had the time yet to make a custom version..
I don't recommend updating from a Custom ROM..
If your 100 percent 5.1.1 Stock you can flash this with ODIN with no problems..
Oh its a Zipped .Tar file.. Don't try to flash the Zip.. Again do NOT try and flash the .Zip.. it will fail and you will be stupid to try..
https://support.t-mobile.com/docs/DOC-21138
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
i have a sm-g920t with an argentinian sim my firmware is G920TUEU3COK1. Can i use my SIM in this firm?
adidas123 said:
Pros:
- Fast
- Beautiful UI
- New functions
- Ram Management has been fixed
- Better battery life
Cons:
- Lost some important functions
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Which functions? I haven't noticed anything missing so far.
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Hi,
I tried to flash this using odin but it did not work so I went ahead and used Samsung Smart Switch that automatically downloads 6.0.1 and flashes it. The process, however, failed and now the phone (G920T) is stuck on a blue screen that says, "An error has occurred while updating the system software. Use emergency recovery function in the Smart Switch PC software." (image: http://i.imgur.com/t401aO6.png). Rebooting the phone takes me to the same place. I'm, however, able to get into download mode. I have tried the emergency recovery in download mode as specified by this video: https://www.youtube.com/watch?v=mi7O0OvnS2E, but it still fails, giving me this error: http://i.imgur.com/t401aO6.png. Could someone help me get my phone working?
A few notes:
- My previous firmware was 5.1.1 stock, however, I had flashed a rooted kernel using odin.
- Within download mode, it says the following: swrev b:3 k:2 s:2
Thank you in advance.
EDIT: flashing with odin gives me this error: http://i.imgur.com/oGZiCow.png
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
You using an older version of ODIN
Try Odin3_v3.10.7
Need help, Im looking for the latest modem and bootloader for this. Just the bootloader and modem. Thanks!
Zaphodspeaks said:
You using an older version of ODIN
Try Odin3_v3.10.7
Click to expand...
Click to collapse
Thanks. That worked. I didn't know there was a newer version available.
I don't suppose there will be a recovery-flashable version of this one, will it?
HKSpeed said:
I'm having trouble flashing this in Odin (3.09). It gets stuck at NAND Write Start! I tried several times. I even waited 15 minutes, but no progress. Is this because the TAR file is 3.6 GB? My computer recognizes my phone's USB connection. Earlier tonight I flashed a TAR file for my Galaxy Tab S without a problem. So weird. I tried different USB ports and reinstalled the drivers.
Here's what ODIN shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU3EPD1_G920TTMB3EPD1_G920TUVU3EPD1_HOME.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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
Click to expand...
Click to collapse
Maybe try redownloading the file and unzipping again
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
BigDaddy38 said:
Maybe try redownloading the file and unzipping again
Click to expand...
Click to collapse
What Odin Are you using?
Related
Hi all,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
denti said:
Hi all,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?
Click to expand...
Click to collapse
Try flash gb rom. http://androidadvices.com/update-galaxy-note-n7000-gingerbread-xxlc1-236-firmware/
Moved To Q&A
Please post all questions in the Q&A section
azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Do this....
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Flash Full GB STOCK ROM via PC ODIN and start again...
Also sounds a little bit like you were on ICS an have flashed a GB Kernel and rebooted....
denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Its a kernel only.. Download full GB rom here.
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-N7000 using XDA Premium App
Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you
denti said:
Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you
Click to expand...
Click to collapse
Read this carefully and understand. Is your device 16 gig? If yes. http://nguyenkieuhung1984.blogspot.com/2012/01/how-to-installflash-samsung-galaxy-note_09.html?m=1
Read 3C
azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Triangle away won't work on GB roms.
Try to reflash CF kernal using PC odin..
Fix it?
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.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..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
replied to PM
Here a SS
Cheers Dr. K
Was looking for just that kind of assurance
I pulled the cable and all is well, Probably something rogue running on my PC as I've used the image to flash before loads of times..
Oh well, I'll wait until I finish work and try again
Yeah this is common, nothing serious.
pit mapping starts everytime, even you dont select pit.
cheers !
dr.ketan said:
Yeah this is common, nothing serious.
pit mapping starts everytime, even you dont select pit.
cheers !
Click to expand...
Click to collapse
Well I spoke too soon!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.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> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.bin
<ID:0/005> modem.bin
<ID:0/005> Sbl.bin
<ID:0/005> cache.img
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
Stuck here for an age now...FFS
So......
I've not got an expensive paperweight it would seem?
Any ideas guys, I've offered alot in the past and this is purely trying to flash a GB Stock ROM i've used a thousand times in PC Odin....
Could it be a comms error? My laptop is ****e...
Flash Pre rooted ROM from my signature.
Phew All sorted...
My advice is don't do **** on a HP laptop hahaha
Nah - i think I lost connection once or twice - AzzleDazzle on his IIRC was a saviour - cheers for the replies - I'm back - I'm Stock - and I am updating...
So in effect - this was a massive PC issue....
As I said - Dr. You're always as asset to have on hand and sorry if I spammed ya PM's - was just having a heart attack there for a few..
Without succes
Do have the same problem on my Note 2 and tried to fix it as shown, but withoiut succes. Hope Dr. Ketan, you or another Android cardiologist may help me, Please.
CJSlim79 said:
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.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..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
Click to expand...
Click to collapse
i am stuck there too.
i just wanted to ask....
WHEN IM STUCK THERE...I NEED TO UNPLUG REBOOT THE TAB AND GET BACK TO DOWNLOAD MODE AND RECONNECT WHILE ODIN IS STILL RUNNING ON PC....right?
but odin doesnt recognize the device again...
please help.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
CJSlim79 said:
Hmm this is odd..
Flashed this GB Stock via PC Odin many times and competes without issue, Tried it today and I am currently stuck at Get PIT for Mapping... It;s a single file ROM I am trying and no I have not selected to use a PIT file or repartition or anything...
Everything is the same as normal,
Phone just shows in Download mode but with no activity...
Any ideas? Am I safe to do a battery pull / disconnect it at this point? Do I wait? Its been like this for half hour or soo..
Very strange..
This is where I'm stuck -
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKKA_N7000CPWKK3_N7000XXKK5_HOME.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..
From the above - it has not started any "Push" activity yet and there's nothing showing (Progress bar or anything) on the phone so I assume it's cool to pull the cable.. Just wondering if anyone else had this issue...
Fix Info
If you're like me and a little worried about things like this then it's best to ask - As i stated, from my understanding here, ODIN had NOT started any NAND write.
This was resolved by unplugging the USB > ODIN immediately turned to "Failed" > Rebooted phone > Rebooted PC > Success..
I DO NOT recommend unplugging USB from ODIN without either A} Knowledge or B) Advice
If it HAS started to write and you're stuck somewhere other than this (Factory_FS / Data IMG etc), seek advice.. and most of all 'Search before asking....'
Thanks all
Click to expand...
Click to collapse
i am stuck there too.
i just wanted to ask....
WHEN IM STUCK THERE...I NEED TO UNPLUG REBOOT THE TAB AND GET BACK TO DOWNLOAD MODE AND RECONNECT WHILE ODIN IS STILL RUNNING ON PC....right?
but odin doesnt recognize the device again...
please help.
You need to restart both the phone in download mode and close odin and then restart odin
Sent from my GT-N7000 using xda app-developers app
Get PIT for mapping..
(Get PIT for mapping..)
You need to check cable or to replace cable some samsung needs original cable.. thats it
CJSlim79 said:
Phew All sorted...
My advice is don't do **** on a HP laptop hahaha
Nah - i think I lost connection once or twice - AzzleDazzle on his IIRC was a saviour - cheers for the replies - I'm back - I'm Stock - and I am updating...
So in effect - this was a massive PC issue....
Click to expand...
Click to collapse
:good: Thanks a lot! Stuck for days on end trying to root my Galaxy S3 t999 when I ran across this. I switched from my HP laptop over to my Dell desktop setup and everything ran perfectly on the first try! I was pulling my hair out trying to figure out why Odin kept failing and I couldn't root. Don't know what's up with those HPs.
Solution
You need change other cable. This will change problem
i tried and OK !
delete
Error odin invalid ext4 image firmware italy to germany(BTU)
Hello i have the simil problem with my galaxy note 4 (SM-N910F) (I'm italian), i try to flash firmware italy in my phone because i have the germany firmware (BTU) but odin screen error invalid ext4 image, i have read tha t the problem is the pit or the partition in my phone. what should i do for flash my firmware in my phone thanks a lot.
Post odin log
Sent from my SM-N910G using xda premium
Odin: invalid ext4 image and the odin in desktop on my computer write fail and the smartphone don't reboot
Sent from my SM-N910F using XDA Free mobile app
Copy paste full error log from odin
Sent from my SM-N910G using xda premium
So I've been using 4.4 SlimKat for quite a long time now and it has been running quite well. But earlier today out of nowhere the phone started to overheat like crazy and shut down.
I let it cool off for a bit then turned it on, and it got stuck on a bootloop on the Samsung logo.
Recovery works but whenever I try to flash or wipe anything, I get "unable to make /cache" and "Can't find log file" and formatting cache using make_ext4fs and it gets stuck on that.
And I tried installing the stock ROM using ODIN and that didn't work as well, It got stuck on "nand write start!!"
So, Does anyone have an idea on how I'd be able to fix that ?
FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still stuck on "NAND write start!!"
Usamovic said:
Still stuck on "NAND write start!!"
Click to expand...
Click to collapse
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.
Usamovic said:
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.
Click to expand...
Click to collapse
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
How many times have you written the same post..? Ha ha... I counted 10...
nokiamodeln91 said:
How many times have you written the same post..? Ha ha... I counted 10...
Click to expand...
Click to collapse
And will continue !
Sent from my GT-N7000 using Tapatalk 2
I blame Phil.
Sent from my Nexus 5 using Tapatalk
AndroidSlave said:
I blame Phil.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It seems Phil is not having time to monitor all his threads.
forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.
Usamovic said:
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.
Click to expand...
Click to collapse
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
Usamovic said:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
Click to expand...
Click to collapse
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still the same problem.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLT9-ORA-5.11.2.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> PhilZ-cwm6-XXLTA-ATL-5.11.2.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.
Usamovic said:
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.
Click to expand...
Click to collapse
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.
nokiamodeln91 said:
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.
Click to expand...
Click to collapse
Yeah, I reboot every single time.
Usamovic said:
Yeah, I reboot every single time.
Click to expand...
Click to collapse
Alright... Try another PC and cables if possible.
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
master-i said:
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
Click to expand...
Click to collapse
If you have TWRP installed, you can just ADB the file over. Easy.
If you only rooted and want to preserve your KNOX flag, you need to ODIN back to stock and then re-root. It's not destructive, so it's not nearly as bad as it sounds
I don't have twrp for now but can i Install it on download mode ? I just tried to install it and it stop on Start upload (on odin)
Follow these instructions. Download ODIN from that link too
http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706
Do i lose my data? and where Can I find the [Unified Driver Installer] on step 2?
No you won't lose your data at all, you will lose root, but all you need to do is re-root the phone.
http://developer.samsung.com/technical-doc/view.do?v=T000000117
I think it's easier to flash only the build.prop no? is it possible?
Thanx to help me bro!
No at this point, IMO, this is the easiest way to get you back to where you were. I assume you're on the stock ROM just rooted.
Yes, I were on the stock room just rooted by PingPong. Hope it will not make my phone slower or make it crash more often... :/
Yeah just ODIN back to stock, then re-root using PingPong, it's really not as bad as it sounds. All of your apps and user data including all settings will still be there.
@se1000
Please look this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Have you had your phone in download mode for a while? If so, try rebooting the phone
se1000 said:
Have you had your phone in download mode for a while? If so, try rebooting the phone
Click to expand...
Click to collapse
Of course I just retried again same error... I can't understand because I see the 0:COM3 on Odin...
Are you using the ODIN from the link? I had problems with other versions
se1000 said:
Are you using the ODIN from the link? I had problems with other versions
Click to expand...
Click to collapse
Yes the V3.10
Were you trying to run ADB earlier? Try rebooting the PC
I closed and reopen Ondin on Administrator and now it's blocked with: <ID:0/003> SetupConnection..
Try a different USB cable or different USB port. Seems ODIN can get a bit finicky
I rebooted PC and my Phone and unplugged and still the same
maybe it's because i tried to install twrp?
Shouldn't matter, as long as you're in download mode and ODIN shows light blue it should work
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything
Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too