[GUIDE] Heimdall - BOOTLOOP RECOVERY, STOCK RESTORE! SM-N900T only!

[noobtoob]

Yes this is what I want to know, possibly the bootloader is locked from what has been circulating but Tmobile has never locked the bootloader before

Sent from my SM-N900T using Tapatalk

Not locked, but protected. They put something in there as to not be able to revert backwards. It is still unlocked and rootable.

I am not even close to bring a Dev, or bootliader guy, so looks like we have to wait. I guess Odin will become my friend in the meantime. **sigh**

Sent from my SM-N900T using Tapatalk

 

[bdorr1105]

Not locked, but protected. They put something in there as to not be able to revert backwards. It is still unlocked and rootable.

I am not even close to bring a Dev, or bootliader guy, so looks like we have to wait. I guess Odin will become my friend in the meantime. **sigh**

Sent from my SM-N900T using Tapatalk

Lol Yea I Hear ya

 

[cbucz24]

Not locked, but protected. They put something in there as to not be able to revert backwards. It is still unlocked and rootable.

I am not even close to bring a Dev, or bootliader guy, so looks like we have to wait. I guess Odin will become my friend in the meantime. **sigh**

Sent from my SM-N900T using Tapatalk

Lol I was talking to dragon about this last night. He's trying to make a pkg like you.

On a side note. I finally got my virtualbox installed. Took twice. Oh well.
Now I can't get it to see anything USB?
I've checked the options. Mint sees it an pops it open.

I'm going to grab my windows laptop today. Too frustrated to keep fighting with it for now. I've got theming to do

Sent from my SM-N900T using Tapatalk 2

 

[lainemac]

Anyone able to get the 4.4.2 pit file? My note 3 seems to be acting funny...

 

[noobtoob]

Anyone able to get the 4.4.2 pit file? My note 3 seems to be acting funny...

Post number 52.

Sent from my SM-G900T using Tapatalk

 

[vitosans]

Post number 52.

Sent from my SM-G900T using Tapatalk

Anyone have any luck with this?

I have a 1/2 pregnant 4.4.2 install. To me it looks like the stock recovery was loaded and thats it. hemidall looks useless on 4.4.2 and odin is not working for me. (write error) I think its a vmware-fusion issue will try on a real windows pc at work this morning. Has anyone used the pit file from post 52 w/ odin?

Running out of ideas here to bring this soft brick back to life. Kies ( useless ) hemidall not working with 4.4.2, and odin doesn't look like its likes vmware-fusion.

Regards,

 

[noobtoob]

Anyone have any luck with this?

I have a 1/2 pregnant 4.4.2 install. To me it looks like the stock recovery was loaded and thats it. hemidall looks useless on 4.4.2 and odin is not working for me. (write error) I think its a vmware-fusion issue will try on a real windows pc at work this morning. Has anyone used the pit file from post 52 w/ odin?

Running out of ideas here to bring this soft brick back to life. Kies ( useless ) hemidall not working with 4.4.2, and odin doesn't look like its likes vmware-fusion.

Regards,

VMware definitely doors not work with our phones, and as you mention 4.4.2 kills heimdall. you are able to flash any stock tar through Odin on a windows PC without the pit, but my phone specifically like version 3.07 of Odin.

Fusionized tweaking tapatalker here...

 

[vitosans]

VMware definitely doors not work with our phones, and as you mention 4.4.2 kills heimdall. you are able to flash any stock tar through Odin on a windows PC without the pit, but my phone specifically like version 3.07 of Odin.

Fusionized tweaking tapatalker here...

100% was my problem. I spent hours hacking trying to get this working. Then finally gave up. After posting this morning, at work I took over a windows laptop and it flashed first pop. :good:

If anyone is using vmware fusion and odin and you get write fail, its vmware not your phone.

Thx for the thread.

 

[noobtoob]

Deleted

custom DPI - check
custom theme - check
awesome phone - check
ROM = [Rock Solid] Vendetta <-- verified beast of a ROM.

 

[xxjahasotoxx]

Post number 52.

Sent from my SM-G900T using Tapatalk

I tried using this on the new NF9 update and it didn't work

I'm on win 8 using odin tried both odin 3.7 and 3.10

any help would be greatly appreciated

 

[noobtoob]

I tried using this on the new NF9 update and it didn't work

I'm on win 8 using odin tried both odin 3.7 and 3.10

any help would be greatly appreciated

They updated boot loader to not allow rolling back from kk to jb. This method no longer works. Only way it would was if you pulled it straight out of the box and tried it out. We are all stuck using Odin right now. Even with Odin you can't go back to stock job, but can restore the latest firmware.

Sent from the dirty flashed note 3!

 

[songykun]

Hey @noobtoob, thanks for the guide, i was stuck trying to flash with Odin and started trying to do your method.

I got the initial libusb -12 error fixed, I've tried using Zadig.exe and replacing the MSM8960 Drivers with the libsub-win32 drivers, which seemed to work but then it gets to the point where it won't download the pit anymore.

I've tried it on multiple USB ports, two different computers and a laptop. I've tried with the original Samsung Note 3 Cable, and also a Note 4 Cable.

Here's a history of what else i've done to try to fix it and the errors i've received.

I've soft bricked by wife's phone while trying to do a CF autoroot with Odin.
The error i'm receiving is:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.

I've tried hooking it up to Kies (Kies Lite) to run the Emeregency Firmware Recovery, but Kies won't recognise the device.
It just sit's there saying connecting.

I've tried using Odin to flash the stock firmware and I get a error after Nand Write.
Stock Firmware i'm trying to Flash: N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Heimdall Log:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...


I'm at a loss now as how to proceed, i'm no expert on rooting, but i've rooted my own Note 3 and now my Note 4 with no problem.

Any help would be appreciated in getting this running, as we don't have money to get a new phone for my wife since we just had our first baby and finances are tight.

 

[LgPWN'd]

Sure would like to get that pit file... alas ALL LINKS BROKEN

 

[tula97]

any hope for pit file ?