Database Users

Strange Recovery Action

I booted into recovery using TWRP and my device went straight into download mode and I could not get out. I have a unlocked at&t SGH i337 originally with the old bootloader or MDL.
Tried installing the tar file with Odin and it failed. The only tar file I can get to work is NB1 4.4.2. I can't install a custom recovery now cause every time I boot to recovery the whole process starts over.
My device is rooted and shows custom in the bootloader so I'm sure I'm unlocked but even so I went through the unlock procedures just to be sure.
Does this mean I need to use SafeStrap now???
Thanks for your help

PapaMag said:
I booted into recovery using TWRP and my device went straight into download mode and I could not get out. I have a unlocked at&t SGH i337 originally with the old bootloader or MDL.
Tried installing the tar file with Odin and it failed. The only tar file I can get to work is NB1 4.4.2. I can't install a custom recovery now cause every time I boot to recovery the whole process starts over.
My device is rooted and shows custom in the bootloader so I'm sure I'm unlocked but even so I went through the unlock procedures just to be sure.
Does this mean I need to use SafeStrap now???
Thanks for your help
Click to expand...
Click to collapse
Yep. If you ODIN'd the NB1 tar, welcome to the club... your bootloader is now locked and safestrap is the only recovery you can use.
Just to verify, double check your bootloader...
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4

Got this thing unlocked once sure there's a way there's a will ?
Sent from my SAMSUNG-SGH-I337 using Tapatalk

PapaMag said:
Got this thing unlocked once sure there's a way there's a will ?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
The first stage is denial.

guut13 said:
The first stage is denial.
Click to expand...
Click to collapse
It was a short denial, looks as though my flashing days are over for the most part

Cant Install CUSTOM ROMS (twrp Freezes/reboots Mid Flash)

Hi
Im having problems with putting a custom rom on my Note 3 N9005
First I want to mention I am new to all this (NEWBIE) but I have messed around with computers and flashing console for years
Second my phone came to me rooted noticed this when downloading root checker.
(Couldn't tell you anything about it)
So I decided to try put a custom rom on my device as the fact I have been stuck on 4.4.2 since I got the phone
I started by putting a custom recovery using Odin my first attempt was ClockworkMod recovery 6.0.4.8 though every time I tried to boot into recovery it would state "REVOVERY MODE" restart and boot normailly. so I Installed Twrp 3.0.0 and worked:good: boots into it fine made a back up of my rom then cleared system, archive and dalvik/art cache after this I go to install the custom zip file Lordwolf as it goes through the flash the loading bar freezes after saying
"starting armoa installer virsion 2.70rc2 "
"(C) 2013 by amarullz xda-developers"
then just restarts after freezing for about 4 seconds with nothing flashed on the phone.
I have tried a few rom to the same outcome there is no real error just freezes and reboots.
I have tried to look for answer spending a good hour and thats an under statment!!
what am I doing wrong? am I missing something important?

I am having same issue. Mine gets to the part "2013 xda dev.....", freezes in mid-flash and reboots. This has happened with some ROM's such as Touchwiz, darklord and temasek. However the Resurrection Remix worked fine, although I could not get the radio to start working. Any help????

Multiple posts same subject .
Use TWRP below 3.
Root permission and Custom recovery (PhilZ Touch 6.48.4 or twrp-2.8.7.0) is required
TWRP recovery recommended, 2.8.7.0. Newer versions are not supported

Okay. First of all,you need to update from 4.4.2 to 5.0 official. To do this,open up Odin,go into Download mode and flash this https://www.sammobile.com/firmwares/download/66272/N9005XXUGBPB1_N9005EVRGBPB1_EVR/ ... it's official Lollipop 5.0. This will update your bootloader and modem. After you are done flashing,flash TWRP 2.8.7.0 with Odin. After that feel free to flash anything
EDIT: Keep in mind,if you want to flash TW (TouchWiz) based ROMs you can't use TWRP higher than 2.8.7.0. TWRP 3.0 is not compatible with Samsung/TW ROMs. On the other hand,if you decide to flash CyanogenMod based ROM you can flash TWRP 3.0.2.1

You will find the most popular,stable SM-N9005 recovery is TWRP 2.8.7.0 - I would strongly suggest using this one. It is not only less bugs but also many others here use the same and is best for support/queries that arise.
Also, TWRP still offers online live support via freenode.

JJEgan said:
Multiple posts same subject .
Use TWRP below 3.
Root permission and Custom recovery (PhilZ Touch 6.48.4 or twrp-2.8.7.0) is required
TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Click to expand...
Click to collapse
Yes, thanks that did the trick. I downgraded to 2.8.7.4. and installed perfectly. Thanks a million!!!

OF1 Firmware Bootloader Locked
GamingDj said:
Okay. First of all,you need to update from 4.4.2 to 5.0 official. To do this,open up Odin,go into Download mode and flash this https://www.sammobile.com/firmwares/download/66272/N9005XXUGBPB1_N9005EVRGBPB1_EVR/ ... it's official Lollipop 5.0. This will update your bootloader and modem. After you are done flashing,flash TWRP 2.8.7.0 with Odin. After that feel free to flash anything
EDIT: Keep in mind,if you want to flash TW (TouchWiz) based ROMs you can't use TWRP higher than 2.8.7.0. TWRP 3.0 is not compatible with Samsung/TW ROMs. On the other hand,if you decide to flash CyanogenMod based ROM you can flash TWRP 3.0.2.1
Click to expand...
Click to collapse
I've been running on OF1 for a minute and it's Bootloader is locked so I have to unlock everytime using ADB fastboot. As for TWRP I have 2.8.7.0. installed. Flashed like a charm, although I can't get my sms to work now (Aryamod 6.0.1.)

If you have N9005 your bootloader can't be locked. AT&T & Verizon locks their phone's bootloader.

GamingDj said:
If you have N9005 your bootloader can't be locked. AT&T & Verizon locks their phone's bootloader.
Click to expand...
Click to collapse
I have a Verizon note 3, someone told me to upload my vzw note 3 with the n9005 firmware. Supposedly would fix my bootloader.

Also,SMS not working should be ROM problem. I personally never had it.

newbie201 said:
I have a Verizon note 3, someone told me to upload my vzw note 3 with the n9005 firmware. Supposedly would fix my bootloader.
Click to expand...
Click to collapse
what u mean by fixing your bootloader ?
---------- Post added at 12:09 PM ---------- Previous post was at 12:09 PM ----------
also its weird, i have been using the latest twrp and i havent encountered problems, even tho ive being using roms not compatible with my phone lol

newbie201 said:
I have a Verizon note 3, someone told me to upload my vzw note 3 with the n9005 firmware. Supposedly would fix my bootloader.
Click to expand...
Click to collapse
The Verizon note 3 has locked bootloader. Even if the bootloader was unlocked, you can't flash an n9005 bootloader to the Verizon note 3 as Odin won't allow that to happen.

HLTEVZW 5.0 Recovery Image

I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?

cyberoptics said:
I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?
Click to expand...
Click to collapse
Cyberoptics,
It's bad form to post the same request in multiple threads.
You'll probably have to odin back the official OF1 5.0 image and start fresh.
Cheers,
B.D.

cyberoptics said:
I rooted my hltevzw 5.0 which has a locked bootloader with CMF 4.4... I'm on 5.0. That resulted in my entered a boot loop after corrupting my recovery partition. I flashed another file that got me back in the phone... but I don't have the stock 5.0 recovery and every custom recovery for this phone is 4.4.
Can anyone who used the yemen or dr.android root for 5.0 make me an img.tar that I can flash to fix my seandroid not enforcing error when I try to use stock 5.0 recovery?
Click to expand...
Click to collapse
Image here : https://www.androidfilehost.com/?fid=24052804347806840
recovery here : https://www.androidfilehost.com/?fid=24052804347806842
That is what you need right ?

aaroon200 said:
Image here : https://www.androidfilehost.com/?fid=24052804347806840
recovery here : https://www.androidfilehost.com/?fid=24052804347806842
That is what you need right ?
Click to expand...
Click to collapse
YES! The recovery imaged flashed in Odin and I'm looking at my stock recovery.
Why folks told me to re-image my boot partion I have no idea... the recovery image is a whole different partition than the data... absolutely no reason to lose data.
Thanks again aaroon!

cyberoptics said:
YES! The recovery imaged flashed in Odin and I'm looking at my stock recovery.
Why folks told me to re-image my boot partion I have no idea... the recovery image is a whole different partition than the data... absolutely no reason to lose data.
Thanks again aaroon!
Click to expand...
Click to collapse
Ok no problem, but please don't flash any custom recovery (ClockworkMod/TWRP) on your note 3, it won't work , the only option is to download " flash fire" if you want to flash the JasmineROM v6.1 or something else.

i'm try but not working on 5.0.

aaroon200 said:
Ok no problem, but please don't flash any custom recovery (ClockworkMod/TWRP) on your note 3, it won't work , the only option is to download " flash fire" if you want to flash the JasmineROM v6.1 or something else.
Click to expand...
Click to collapse
I have SM-900V verizon note 3 and I am running the latest TWRP...
And Running JasmineROM v6.1 after using TWRP to flash it.

@CL3WL3SS
You are commenting on a thread from March 2016 - a time when boot loader unlocking was not available to retail Note3 phone owners.
There's probably not much point in reviving old threads and correcting folks over points that they could not possibly have been aware of.
But yeah, *now* you can run TWRP in the recovery of an unlocked bootloader phone. They didn't have that option in March.

bftb0 said:
@CL3WL3SS
You are commenting on a thread from March 2016 - a time when boot loader unlocking was not available to retail Note3 phone owners.
There's probably not much point in reviving old threads and correcting folks over points that they could not possibly have been aware of.
But yeah, *now* you can run TWRP in the recovery of an unlocked bootloader phone. They didn't have that option in March.
Click to expand...
Click to collapse
Sorry I didn't go back that far, I thought. I will definitely look at the dates from now on. Apologies.

how to use flasfire
CL3WL3SS said:
I have SM-900V verizon note 3 and I am running the latest TWRP...
And Running JasmineROM v6.1 after using TWRP to flash it.
Click to expand...
Click to collapse
How did u do that my friend? Is flashfirelike safestrap? Locked bootloader bypass?

Error when trying to install custom recovery (TWRP or CWM).

Yet another post... So, I have been trying to install TWRP and CWM but every time I boot into recovery with those installed I get: "System Software not Authorized" error. Is there anyway to bypass this? I think I Soft Bricked it, but I fixed it with Odin and a stock recovery file. I just want to get a custom recovery... Any help is appreciated.
Device: Samsung Galaxy S4 I337 (AT&T) (Rooted)

Can't install cwm or twrp on an s4 with a locked bootloader.

Hmm that is strange.

audit13 said:
Can't install cwm or twrp on an s4 with a locked bootloader.
Click to expand...
Click to collapse
How would I go about unlocking it? I remember before the s4 got the 5.0.1 update and I had cwm.

The att s4 bootloader can't be unlocked once it has been upgraded to a locked bootloader.

That sucks. Is there another phone that can unlock it's boot loader? I head something about asking the company to unlock it for you. Is that possible?

Quick little update:
I have found some options that might work. Option 1: Someone said that you could downgrade to 4.2.2 because that has an unlocked boot loader. Or option 2, which is go to Best Buy and tell the Samsung Support Center dude to unlock it for you. I really would rather go with option one, because what if the dude denies it. Unless, because I already got the locked one on my device, there is no way to downgrade it...

There is no way to downgrade the bootloader to 4.2.2 or to unlock the bootloader.

Right, well I installed Safestrap and updated to 5.0.1 with keep root method. Something I just realized is that we have a s2 laying around somewhere. I guess I can mess with that. And as for a new phone, I guess I will save up to buy a Nexus 6 from the Google site.

Odin stuck at "File analysis"

Attempting to flash TWRP using Odin, only Odin keeps getting stuck at "File analysis." Please help!

TWRP can't be flashed to an AT&T s4 with a locked bootloader.
What is the exact model # of the s4? The model # can be found in download mode.

audit13 said:
TWRP can't be flashed to an AT&T s4 with a locked bootloader. What is the exact model # of the s4? The model # can be found in download mode.
Click to expand...
Click to collapse
I had 3.0.2-0 TWRP on my i337 (jflteatt) for a good while now. Then yesterday I flashed the latest 3.1.0-0 and it broke my recovery (stupid me, I keep forgeting that I should not "fix it if it ain't broken"!). Whoever posted the 3.1.0-0 version "forgot" to mention that it was not lokied! Now I am trying to recover my recovery, as it were: Someone posted a .tar of a lokied 3.1.0-0 TWRP, but it looks to me that the file is bad. Can you provide a working (i.e. lokied) .tar of an earlier TWRP version please?

Does your i337 have a locked bootloader?

audit13 said:
Does your i337 have a locked bootloader?
Click to expand...
Click to collapse
All ATT i337 (jflteatt) have locked bootloaders. That is why "they" came up with the loki-doki exploit.

The i337 bootloader was locked with the 4.3 or newer ROM. With a locked bootloader, no exploit will allow the installation of twrp, philz, or cwm which is why safestrap must be used with a locked bootloader. Same applies to the att note 3.
https://forum.xda-developers.com/showthread.php?t=2785166
What is the bootloader version on the i337?

audit13 said:
The i337 bootloader was locked with the 4.3 or newer ROM. With a locked bootloader, no exploit will allow the installation of twrp, philz, or cwm which is why safestrap must be used with a locked bootloader. ... What is the bootloader version on the i337?
Click to expand...
Click to collapse
Thanks for the replies. As I said in my earlier post, I used to run TWRP 3.0.2-0 on my jflteatt, and that should tell you everything you need to know. (I am currently running LinOS 14.1 on the phone.) Only yesterday, after "upgrading" my recovery to 3.1.0-0 the trouble started. As for the bootloader version, how do you tell what that is?

Since the phone is running twrp, this tells me that the bootloader is older than 4.3 and the bootloader is not locked.
Are there any references to Knox in download mode? If not, the bootloader is not locked and the bootloader is 4.1 or 4.2.

audit13 said:
Since the phone is running twrp, this tells me that the bootloader is older than 4.3 and the bootloader is not locked. ... If not, the bootloader is not locked and the bootloader is 4.1 or 4.2.
Click to expand...
Click to collapse
Again, all i337 bootloaders are locked. The first generations of locked bootloaders were vulnerable to the loki exploit. Newer generations of bootloaders are not so vulnerable.
And just to answer my initial question, TWRP cannot be flashed w/Odin on i337 (jflteatt), regardless of the bootloader version, as the bootloader is locked. I had to flash TWRP from within the OS after rooting. Problem solved.