[Q] bricked note 3 n900v - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

ok we all know how this happens and some of us actually try everything and read everything before posting...
i have a 900v
i can get it into download mode
i cant get any stock roms to flash
i have run a pit file with odin 3.07 and that worked to get my phone to be able to go into the screen by power vol up and home
so when i power vol down and home i get the odin mode / download screen and i continue and odin recognizes the phone
now when i load odin 3.09 and stock roms from sammobile it errors.
one thing i noticed is the wait time when loading the stock rom to odin. it hangs for a while. odin when flashing in the past was quick at loading its roms.
ive tried mje rom
nc2, nc4 non of which are working with odin at this time.. where did i go wrong.?
here is the log;
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i posted some screen shots..
also i am using the 3.0 cable to a 3.0 slot so it should be proper connections
samsung returned my phone without fixing it because it didnt have an IMEI sticker behind the battery. AHHSOLES it was in warranty.

Try with the 2.0 usb cable.
what rom are you flashing? And what rom you coming from?

Hi.
I had Jasmin room 2.4 I think. I tried to flash back to stock rom. To sell the phone

puchodog1977 said:
Hi.
I had Jasmin room 2.4 I think. I tried to flash back to stock rom. To sell the phone
Click to expand...
Click to collapse
I'm with israfm on trying a usb 2.0 cable and try different usb ports on your computer too (try to stick with usb 2.0 ports because I've read before that Odin doesn't play as well with usb 3.0 for some reason) .
If you're not flashing the pit file together with the stock Firmware, I would try that too. Also, make sure KIES is not running in the background if you have it installed on the computer, and disable any antivirus programs.

I'll report back soon. I switched to a Samsung note 4 USB cord but was still plugged into a 3.0 port I'll move it to 2.0 and try to flash the pit file and stock kit kat verizon rom . The pit file only worked on Odin 3.07 and I thought I needed to use Odin 3.09 for Samsung. Is that right?

puchodog1977 said:
I'll report back soon. I switched to a Samsung note 4 USB cord but was still plugged into a 3.0 port I'll move it to 2.0 and try to flash the pit file and stock kit kat verizon rom . The pit file only worked on Odin 3.07 and I thought I needed to use Odin 3.09 for Samsung. Is that right?
Click to expand...
Click to collapse
The pit file will work with Odin 3.0.9 as well, just load it into PIT file slot and load the firmware into the AP slot.
In Odin, you should have Auto Reboot, Re-partition, and F. Reset Time checked, but all other options should be unchecked. Another important thing I forgot to mention was to Run Odin as Administator.
If you want, you could also try it on Odin 3.10.0, which you can find at this link: Odin 3.10.0.
I've been using Odin 3.10.0 with good results and it might work for you too. (Recognized Contributor -CALIBAN666- uploaded this Odin version on this thread, so hit the thanks but for him if it helps you).

ok. i just needed to flash VZW\N900VVRUDNJ6 apparently the earilier versions wouldnt work. i just worked my way up from the earliest update to this NJ6
thanks guys.. oh btw i used 3.10 odin. worked like a charm

puchodog1977 said:
ok. i just needed to flash VZW\N900VVRUDNJ6 apparently the earilier versions wouldnt work. i just worked my way up from the earliest update to this NJ6
thanks guys.. oh btw i used 3.10 odin. worked like a charm
Click to expand...
Click to collapse
It's good to hear that the phone is working again. I'm not sure if you know, but since you flashed 4.4.4 onto the phone, you won't be able to root it any longer. There's no current root method for anything above 4.4.2. It's possible that a root method may be developed one day, but for now, all you can do is run stock.

Related

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything
Is your device unlocked or branded?
Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.
Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?
Have practically the same situation...
The furthest I've got is the following
Code:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.
Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

Samsung will not touch my brand new S5, rooting gone wrong! HELP NEEDED!

Hi all, I have rooted my galaxys in the past, but I have ran into a problem with this device, I am now only getting ''firmware upgrade encountered an issue please select recovery mode in kies and try again'', I have tried connecting to Kies, but all I get is an error message. I have tried to flash another rom, but I get error messages aswell, and I just stay stuck in the same place .
I have tried to bring my s5 to a local guy who roots and fixes phones, but he could not solve this. Now Samsung will not touch it, as I have voided the warranty.
Please can someone help me, I don't want to loose €400 of a brand new device if someone can help, I will show my appreciation in some way!! Please people, I am so desperate :crying:
Need to ask Qs in the Q&A forum
http://forum.xda-developers.com/galaxy-s5/help
Go to Sammobile .com and download a stock ROM for your model S5
Use ODIN to flash it while the phone is in download mode
Instructions are under the download on sammobiles site
*Detection* said:
Need to ask Qs in the Q&A forum
http://forum.xda-developers.com/galaxy-s5/help
Go to Sammobile .com and download a stock ROM for your model S5
Use ODIN to flash it while the phone is in download mode
Instructions are under the download on sammobiles site
Click to expand...
Click to collapse
thanks for the reply. I tried this and it didnt work, i will upload the error message later, something about not enough storage?
KennethK1992 said:
thanks for the reply. I tried this and it didnt work, i will upload the error message later, something about not enough storage?
Click to expand...
Click to collapse
<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> 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> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is what i get when i try to flash another rom
Which model S5 is it ?
Choose the correct PIT file for your exact model S5 (Example, mine is the G900F), from here
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Extract it, and add it to the PIT section in ODIN, at the same time as you add the stock ROM to ODIN, and flash them both at the same time
Not sure if this is what you have tried in kies3, but this is what worked for me before when things have gone wrong and i had nothing but a samsung paper weight:
Go into download mode and do a firmware upgrade and initialisation through kies3. You will need your serial number and model number( on the white sticker behind the battery. in kies3 go tools> firmware upgrade and initialisation, then follow the on screen steps. I used this when I soft bricked my note 2 when I had it, I personally find it's the best way to restore a samsung device.
If you have any issues, try checking for kies3 updates to ensure you have the latest drivers, and if you can get into the stock recovery on your phone, you could try doing a factory data reset and cache wipe which also sometimes helps.
KennethK1992 said:
<OSM> Checking MD5 finished Sucessfully..
this is what i get when i try to flash another rom
Click to expand...
Click to collapse
The suggestion of @*Detection* will definitely work if done properly, but before doing that you can try this:
Extract the hidden.img from the firmware that you're trying to install, and rename it as hidden.img.tar, now open Odin, and load that file on AP and flash it. After turning on the phone wait around 5 minutes and it should boot up.
got the phone back from SBE (Samsung's Irish Partner) with a chip on it should i try kies3 before going with odin?
using kies3, the program keeps telling me ''device is not supported'' :crying:
KennethK1992 said:
using kies3, the program keeps telling me ''device is not supported'' :crying:
Click to expand...
Click to collapse
You should use Smart Switch.
Uzair40 said:
You should use Smart Switch.
Click to expand...
Click to collapse
what is smart switch? can I do any of this with a Mac? or should I stick with a windows?
Smart switch is for WiFi.... nothing to do with flashing ROMs
Use ODIN and PIT file as I posted originally
*Detection* said:
Smart switch is for WiFi.... nothing to do with flashing ROMs
Use ODIN and PIT file as I posted originally
Click to expand...
Click to collapse
Yea figured that downloading ROM now, what file extension should the pit file be when I download it? thanks for your help!
KennethK1992 said:
Yea figured that downloading ROM now, what file extension should the pit file be when I download it? thanks for your help!
Click to expand...
Click to collapse
ROM should be .MD5
PIT should be .PIT
Extract the PIT file and the ROM once downloaded to get the correct files
*Detection* said:
ROM should be .MD5
PIT should be .PIT
Extract the PIT file and the ROM once downloaded to get the correct files
Click to expand...
Click to collapse
just waiting for the ROM to finish downloading...
which version of ODIN do you recommend I use? thanks again!
The one in the instructions under the download on sammobiles site, I think it's 3.10.7
But you should be able to use any from 3.09 > 3.10.7
Newest generally recommended unless it fails, then try an older version
When you add a PIT file, ignore the instructions about re-partition, it needs to be ticked for PIT, it will set itself up automatically once you add the ROM and PIT
My samsung s5 brick while rooting and I'm downloading rom from sam mobile hope it will work and if not i will try smart switch method
Moa z Bourhani said:
My samsung s5 brick while rooting and I'm downloading rom from sam mobile hope it will work and if not i will try smart switch method
Click to expand...
Click to collapse
What smart switch method?
Smart switch is a toggle switch in WiFi settings, to tell the phone to switch between Data and WiFi to keep the best signal
Where are people getting this crap from?
*Detection* said:
What smart switch method?
Smart switch is a toggle switch in WiFi settings, to tell the phone to switch between Data and WiFi to keep the best signal
Where are people getting this crap from?
Click to expand...
Click to collapse
it seems to be an updated version of Kies, didn't work for me.
KIES added a setting with an identical name as a setting in Android?.... smart move
KIES is all but useless anyway, ODIN for updates, TWRP for backups
KIES says it has backed up fine, but trying to restore the backup, restores next to nothing

[HELP] Trying to root,can't turn on wifi...

So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
SageNightmare said:
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
Click to expand...
Click to collapse
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
sway8966 said:
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
Click to expand...
Click to collapse
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
SageNightmare said:
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
Click to expand...
Click to collapse
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
sway8966 said:
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
Click to expand...
Click to collapse
Yup I tried all of that except a different odin version,but long story short,I managed to go into town and a friend of mine used a different version of odin and got me nice and sorted out,thanks for help btw

Phone won't boot, even into recovery mode

Hi all, im desperate for help here!!
I flashed Dr Ketans Rom to my Note 4 a couple of days ago but decided to try to go back to stock today due to a bug with my email. Anyway, a long story short, my phone failed the flashing process with odin whilst trying to flas the latest stock firmware from sammobile and then my phone refused to start up again.
I now get a screen telling me the firmware up grade process went wrong but I cant even reboot into recovery to install anything else.
I have tried flashing both TWRP and Philz recovery but both just flash the title screen on and off but never load up.
I have tried 2 firmware versions from sammobile and both end in fail, it seems like I cant flash any firmwares with odin which is a right pain because I cant get to recovery to install a zip file....
Please help, Im sooooo stuck!
Edit - this is the log from Odin if it helps anyone... Ive now tried software 4.4.4 also but nothing works.
<ID:0/003> Odin engine v(ID:3.1101)..
<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> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
0-0-0 said:
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
Click to expand...
Click to collapse
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
sudburys said:
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
Click to expand...
Click to collapse
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
0-0-0 said:
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
Click to expand...
Click to collapse
No probs...
Thanks for the try anyway

trying to uninstall cyanogen mod to go to stock

Hey I am trying to uninstall cyanogen mod on my galaxy s4 so that I can return it to stock to sell it. I was following this guide techbeasts.com/how-to-unroot-samsung-galaxy-s4-all-versions/
I downloaded my firmware off of samsungs site the newest firmware available for my phone. I tried to restore it and it gave me an error about xmitdata fail so I had to unplug the phone and try again. Now if I try and boot up the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. If I try and reflash it in odin I get this far now and it freezes...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOH1_I337MOYAGOH1_I337MVLUGOH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
any ideas please? and thankyou!
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
audit13 said:
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
Click to expand...
Click to collapse
Sorry should have put that behind my battery it says sgh-i337m
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
audit13 said:
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
Click to expand...
Click to collapse
yes original cable, it doesn't error it just freezes there. in Download mode it says this:
Odin Mode
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-Config-Lsb: 0x30
Secure Download: Enable
Write Protection: Enable
eMMC Burst Mode enabled
I downloaded my firmware from sammobile.com and looked up the SGH-I337M and chose the one for Fido Canada as that is what I have
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
audit13 said:
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
Click to expand...
Click to collapse
I have tried different port and I don't have another cable, and does that mean I could download like a bell firmware and try that instead?
or is there a way that reinstalling cyanogenmod would fix it and somehow wipe my personal info? that's all I really need to do
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
audit13 said:
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
Click to expand...
Click to collapse
Ok downloading now to try, but ya its freezes the progress bar on phone doesn't move and the Odin app just sits there at aboot.mbn
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
ya I downloaded latest firmware.... and phone encrypted I don't no....
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
audit13 said:
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
Click to expand...
Click to collapse
I will try this now and post back...
I don't think this is good stuck with this....
<ID:0/005> Added!!
<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> recovery.img
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
audit13 said:
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
Click to expand...
Click to collapse
yes, that was while trying twrp, I managed to borrow another cable and got the firmware installed it said passed but phone gets stuck during boot up, I installed twrp now what shall I do install cyanogen again?
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
audit13 said:
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
Click to expand...
Click to collapse
I did a factory wipe and rebooted and it froze ive tried 3 or 4 times now it is upgrading 29/89 will post back if it works..
got it booted up and now its asking for set up, I appreciate your patience and help very much
Flash stock again but do not check anything except f.reset time, flash stock rom, when you see the word pass in the status window, remove USB cable, remove battery and wait 5 seconds, replace battery, boot into recovery, factory wipe, reboot.
thanks ill do that if I have a problem, for now phone is up and running and ready for use
That's great news. I guess all you needed was a different USB cable. I find the s4 to be very picky about USB cables when using Odin.

Categories

Resources