Database Users

Help my gt-i9505 stocked on samsung logo..

i will tell all the information here..i have my samsung gt-i9505 carrier locked to globe telecom here in the philippines..
i tried to factory unlock here http://forum.xda-developers.com/showthread.php?t=2282683 but i have no luck on it..i have change my baseband several time via odin but still i pin request always shows after i reboot..i have android version 4.2.2, stock firmware DXUBMF8.
so i stopped from there..i moved on to try to root my s4,before having this phone i had owned a s4 factory unlock and i have had rooted it but i already forgot how to do it again..so started anew by looking again at forum threads,i have tried omega custom rom but if i goes to recovery mode my screen only shows the following options: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update cache..my question here was,is this the default recovery mode of s4 now?because i can still recall that my last s4's default recovery menu shows with advance option with wipe dalvik cache etc..and my recovery menu now shows no apply update from internal storage..when i tried flashing the custom rom save on my sd card: apply update>omega*something*.zip..it all well done but after rebooting my phone didn't any stuff from that custom rom nor rooted at all..can you help me solving this?
and lastly this is my main problem now,i searched again the thread and went down to this thread http://forum.xda-developers.com/showthread.php?t=2250824 i downloaded the pre-rooted rom XXUBMF8..flashed it with odin PDA..passed and from then my phone was stocked every time i reboot to samsung logo..
i have tried to flash again on a stocked rom. odin>PHONE>(the stock rom)>start>passed then reboot it still stocked to samsung logo..
sorry this was too long to read but i have to tell what all i have been done resulting to this..can someone help me..i will be very thanful for your help..

can anyone help me with this?i have been searching the forum for hours..i have done flashing through odin with stock rom and pit file but it ended up failed..done factory reset with default recovery mode but nothing happens still stucked on boot logo..

still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.

voidjov said:
still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.
Click to expand...
Click to collapse
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info

did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom

TingTingin said:
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info
Click to expand...
Click to collapse
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
daibaron said:
did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom
Click to expand...
Click to collapse
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<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> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..

voidjov said:
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<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> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..
Click to expand...
Click to collapse
In the Thread you point out... read AGAIN about PIT
http://forum.xda-developers.com/showthread.php?t=2265477
Download the PIT and follow the exact procedure... it's not like flashing a new firmware so read which boxes you check
Try the PIT file with / without the firmware
check also this thread... in case you have a pit related error.
http://forum.xda-developers.com/showthread.php?t=2283919
I'm sure you have all you need to recover your phone.
When you will have recovered your phone, update this thread saying you solved your problem.
check also this thread... in case you have a pit related error.
OH, don't forget to update my thanks counter

Hello,
I saw an answer to this problem in another thread. You have to swipe the phone by starting it with VOLUME UP + HOME + POWER, and then whatever options you have to swipe everything.

Problem SOLVED!!!
hey guys i have solved my greatest problem since i started rooting back on my N7100,my 1st s4 and now my new s4..
thank you for all who helped me,after more than 24hours of reading and waiting for you replies and doing some intervention on my s4,i have recover it..i will post here how i did it for reference for others who might encounter this problem same as mine:
first of all i have noticed this just after successfully revived my phone, you have to WIPE THE DATA/FACTORY REFORMAT via recovery mode before and after doing any firmware update,then i just removed my battery may be a minute and put it back again every time i do flashing..
i used odin version 1.85 not version 3.04..i first chose the pit file and flash it.(when i tried flashing the pit and stock rom together it always ended up to fail)..so i decided to chose to flash the pit file only using odin v1.85(it automatically ticked the "repartition option on this odin version" then it passed..after that as i have said remove battery,wipe data,then i removed again the battery,then put it back and do download/odin mode on my phone,then i flashed stock rom from www.sammoble.com, i searched for globe carrier since my phone was locked on that carrier, then after 2-3minutes(be patient and don't do anything while waiting) my phone backed to life!!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OLBBMF8_I9505DXUBMF8_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
for those guys who helped me, i have pressed the thanks button for you guys 100x(i hope i can do that)..but truly i am very much thankful for you guys..i do not have to go to service provider technician or any cellphone repair stall just to repair my phone and pay,i have revived it with your help..THANK YOU!!!
i must add i would like to ask what is the best way to root my phone, i have read chainfire autoroot, is the best way to root my phone?as i can remember it is the same way i have rooted my first s4 two months ago because i saw my old folder here on my pc with that application..and best custom rom?
and the best way to factory unlock my phone, the working firmware..
you can post the link so i can read and do it myself..

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app

fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!

titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

[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.

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*

[CANADIAN] Odin 5.1.1 Bootloader & TWRP Flashable Modem - SM-G920W8 BOI6 *UPDATED*
Rogers is the only carrier who pushed this update, it was pulled shortly after, due to corruption. I had to spend literally ALL day downloading this. I downloaded it 7 times before i got a OTA zip that passes a CRC check and extracted properly. What a pain in the butt it is i had to convert my Telus device to Rogers fully down to modding the EFS to get this done.
Prerequisit: You must be on a 5.1.1 compatible TWRP as well as a 5.1.1 rom when flashing these packages or your going to get stuck in a binary miss match. While there is a fix for this with out the W8 5.1.1 odin packages, it takes a lot of musical flashing. So be sure to be on a compatible 5.1.1 rom, Kernel and TWRP first.
As always, you flash at YOUR OWN RISK. I will of course try to provide support if I am online, If you appreciate how much the pain in my butt was, and you didn't have to do this your self. Click Donate.
The Bootloader MUST be flashed via ODIN 3.10.X or higher. in the BL slot. Hence why its a tar. Sorry no flashables, Samsung locks the boot loader areas to everything but their own signed recovery, from their own signed update.zip
BO8H BL
BOI1 BL
BOI6 BL *LATEST*
The modem is TWRP flashable
BO8H Modem
BOI1 Modem
BOI6 Modem *LATEST*
You can get ODIN 3.10.6 HERE
Samsung USB Drivers HERE
Fingerprint confirmed working by my self. on custom 5.1.1 roms and stock.

You're my hero, lets have sex together

virulentt said:
You're my hero, lets have sex together
Click to expand...
Click to collapse
LOL the new "FIRST!"

-Mr. X- said:
LOL the new "FIRST!"
Click to expand...
Click to collapse
It works thanks a lot haha. No homo btw <3

Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?

anuben said:
Hi first of all thousands thanks to you for your work..
i have just quick question.
currently i am on xtrestolite v2.3 how do i flash this latest bootloader ? i tried flashing via odin v 3.10.7 and it failed. would you mind guide me here?
Click to expand...
Click to collapse
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.

-Mr. X- said:
You must reboot to download mode, and ensure you have the samsung drivers installed. IF you have already done this. paste your odin log.
failing that
please try attached odin instead. If it works i will edit the OP link. .7 worked for me. But either or.
Click to expand...
Click to collapse
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.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)
<ID:0/005> Removed!!

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.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)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
redownload the Bootloader, your .tar could be corrupted.

anuben said:
this is the log from odin. and just to make sure.. i have to select BL option in odin right?
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> cm.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)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Yes i flashed it via BL. Whats your actual device.

Worked perfectly for me. So glad to have a working fingerprint scanner on a 5.1.1 custom rom. Thanks
Sent from my SM-G920W8

Easiest way to do it is just make sure the Bootloader is loaded on Odin first on your PC then reboot to recovery and flash the modem package, select reboot and choose Download so it reboots to download mode, plug the phone to usb and flash in Odin and you're done!
Sent from my SM-G925F

I'm now getting some new "not enforcing" red text during boot. Is that expected?

BlackRabbits said:
I'm now getting some new "not enforcing" red text during boot. Is that expected?
Click to expand...
Click to collapse
Yep that's normal.
Sent from my SM-G925F

-Mr. X- said:
Yes i flashed it via BL. Whats your actual device.
Click to expand...
Click to collapse
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3

I've been using Arter97's back-to-n0t3 v3 with his 3.5 kernel, SO SMOOTH I lose around 5 to 7% overnight. You guys should give it a try!
http://forum.xda-developers.com/galaxy-s6/development/to-n0t3-bring-larger-fun-to-flagship-t3179857
http://forum.xda-developers.com/gal...development/arter97-kernel-galaxy-s6-t3171246
*** Download links are on his website (careful, the 3.6 version of his kernel isn't for our device, use the 3.5 g920tw8 one ***
http://arter97.com/browse/S6/
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
that's not for the edge... you could brick your device flashing a non-edge bootloader to an edge one.

anuben said:
My device is G925w8 but its showing G925F in about phone as i am using xtrestolite v2.3
Click to expand...
Click to collapse
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.

-Mr. X- said:
This is why, odin is protecting you from your mistake. This is a G920W8 boot loader. It would brick your device if you convinced it to flash some how.
I do not have a G925W8 so i was un able to play musical CSC and FLash to get that OTA before rogers pulled it.
Just as a note guys, the fact that rogers pulled this update. expect all of the Canadian carrier updates to be delayed for weeks now.
Click to expand...
Click to collapse
holy fuk i shouldn't be doing drinking and flashing :silly: thank you though. appreciate your help...:good:

Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.

caanda45 said:
Thanks Mr. X....Confirmation number: 14Y69764AE724154S a little appreciation of your time. Can I re root and then flash this on my Bell device over 5.0.2? Or should I wait till I get the Bell`s 5.1.1. It has been awhile since I had a Sammy phone. I had a whale of time to get back to stock using Smart Switch and Odin always failed for me. Just want to be able to flash 5.1.1 roms with most stuff working. Thanks again!! My device is the SM-G920W8 Bell S6.
Click to expand...
Click to collapse
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I would flash TWRP on your 5.0.2 device as it sits, then i would choose your 5.1.1 rom of your liking. Put it all on your storage on the phone except the bootloader tar. Flash the rom, modem and what ever else in TWRP. then in the TWRP reboot options reboot directly to download/bootloader. and odin the bootloader. boot the device normally and you're good!
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader

-Mr. X- said:
As this is a 5.1.1 boot loader it will require you to be on a 5.1.1 rom. good news is there are many roms to choose from that all work perfect due to my audio patches, and now this boot loader
I do have the rogers ota update zip but i hesitate to distribute it since they pulled it due to bugs, and is uspect corruption ans i had to re-download it several times before it wasn't corrupt from their ota server.
PS: Thanks for the donation!
I am personally running this http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968, with the new boot loader and modem. it runs beautifully.
Any international rom with a kernel for our device and my audio patch will work. the rom i link packs it all up in a bow for you no extra work. finger print will also work since this boot loader
Click to expand...
Click to collapse
Perfect, I was on that rom for awhile with 5.0.2 and some stuff missing..So the best plan is
1. Re Root and Flash TWRP
2. Back up
3. Flash 5.1.1 Rom
4. Flash Bootloader with Odin
5. Flash Modem with TWRP
And then I should be good to go? Where does the Audio patch come in?
Any other suggestions or order to my plan?
Thanks again for your time and hard work!!!

Tried to install TWRP, messed up bootloader - Not sure what to do next

I pulled out my old Verizon Galaxy S4 with the intention of getting a ROM on it that had XPosed. After some Googling, saw KingRoot supported it, so I used that app to root it. Then I tried to get TWRP installed. Their website said you could do it from their TWRP Manager app, so I tried that. It *said* it succeeded, but after that, my phone couldn't even boot at all.
So then I read up on using Odin to fix it. I tried to flash TWRP recovery from Odin (even finding a .tar version was a PITA), but I got this:
Code:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now, it boots normally, but I can't get into Recovery any more.
All I really want to do is get some custom recovery on there. Or even back to normal at this point. But I don't know how. I also tried flashing Clockwork Mod, but that didn't improve anything. What should I be doing now? Go back to stock and start over? Or am I installing the wrong recoveries from Odin (the TWRP one wasn't on their official download page, they only have .img files there, not tars). Or what?

Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.

Make sure your TWRP is for that phone model. Verizon phones have locked bootloaders which make modifications harder.

Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.

Strephon Alkhalikoi said:
Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.
Click to expand...
Click to collapse
That link doesn't have any tarballs. Only image files. I couldn't find the tars on their site at all, and the only one I could find was one someone had as an attachment in a thread. No clue if it's the right one, though.
Strephon Alkhalikoi said:
Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.
Click to expand...
Click to collapse
I tried to install Clockwork Mod, but it didn't work. I got the fail message above when trying to install the tar via Odin, and when I tried to use their app, it did the same thing the TWRP Management app did - it said it succeeded, but now I can't boot into recovery.

Do not install Clockworkmod. It's no longer maintained and has problems with more current ROMs. Install TWRP using that tarball you found on the forums. I believe TWRP on Verizon has no tarballs as it's expected to be installed using the TWRP Manager or a similar app in the Play Store.
If this does not work, you may have to start from scratch. Hopefully you kept a copy of the ROM with the exploitable bootloader so you can reinstall if necessary.