Database Users

Bootloader/Flash Problem

I have an ATT i337 S4 (mdl baseband) running on T-mobile. Current setup was wicked 7.0 ROM with ATT kernel.
I was trying to change to cyanogenmod ROM and tried using my TWRP 2.5.0.2 to load the rom but it would flash it and gave me an md5 error. Supposedly this is a known issue with TWRP so most people recommend using clockworkmod recovery and I tried to load that using recovery tools. Recovery tools couldn't find the CWM image file but did find the 2.6.3.0 updated TWRP image file so I tried to update TWRP and when I did, I can't boot to recovery anymore and instead get the yellow triangle saying unauthorized software.
At the same time (ugh) I flashed wicked 8 ROM update and think I loki'd it (I am running wicked 8.0 now) but I forgot to run the att kernel afterward. The current kernel is 3.4.5 ... dirty ptmr3 ... N5110 #1. I think this is the standard t-mobile kernel which will obviously not work on my ATT phone.
The problem is, now I can't reboot into recovery mode. When I try, I get the yellow triangle "system software not authorized by ATT...". I don't know if the problem is with the bad kernel or with the updated 2.6.3 TWRP. The only way I can get around the bootloader problem is the hold down the down vol and home button, then the power button and that gets me into a "Warning a custom OS can cause critical problems ..." page. From there if I continue, I get the yellow triangle. If I hit the volume down button to cancel, it boots normally but not into the bootloader and I have partial functionality of my phone.
Where do I go from here? Odin to stock? Replace the bootloader somehow? Anything else?
I did do a nandroid of my system before all of this but for some reason I can't access my SD card. I can hit mount but nothing shows up on file manager. Will that backup replace the bootloader with the known good one? I could copy the backup to the phone memory and do it from there using titanium backup I think.
Thanks,

odin back to stock and then wipe/clear then retry should fix this problem

lilg754367 said:
odin back to stock and then wipe/clear then retry should fix this problem
Click to expand...
Click to collapse
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.

colorchange said:
Do you think it's worth a shot to try and find a kernel flasher that will allow me to flash the correct kernel? I really hate to start from scratch unless it's my only choice.
Click to expand...
Click to collapse
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.

colorchange said:
Can I use fastboot to try and load the original twrp 2.5.0 version bootloader that worked? Then I can factory reset, reflash the ROM, loki, then flash the ATT kernel.
Click to expand...
Click to collapse
I'm guessing I might be able to modify the open boot script and change to the old version but I don't know how to do this.

i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain

lilg754367 said:
i mean its really up to you and your personal preference but i was just saying that is what i would do and then look around for different kernels and so on i do but its alot to explain
Click to expand...
Click to collapse
Thanks lil, i know the kernel I want and have it downloaded. Right now I am downloading the tar file to get me back to stock. I was hoping to do something easier but crud...

yea no problem just hit the thanks button for me good luck

I can't get Odin to talk to my device. When it is not in download mode, Odin sees it but hangs and can't communicate. When I connect it in debug mode (very hard to get into download mode), Odin can't see it.
Help!

SOLVED recovery is not seandroid enforcing set warrenty bit : recovery --> loop

after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?

Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap

fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.

hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man

TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred

thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!

nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD

Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast

Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....

Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.

Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of

Thanks!
Thank you very much,you save me a lot of trouble.

hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot

billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?

hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6

billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat

hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery

billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.

hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin

billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.

Cant access CWM anymore.

Tried to install CWM from rom manager 6.0.4.6 but i had 6.0.4.7.
This cus i have problem installing CM updates directly by pressing restart and install.
Efter this i was in a boot loop an could not access CWM only the DL mode. So i installed CWM from the original source i did the first time and then the boot was ok all the way but then tried PWR VOL+ HOME but then i gut in to the boot loop again untli i reinstalled the CWM tried once more but same result.
So now i have CWM installed and i can boot up but i cant access CWM to make backup or restore the previus one.
Any ideas of what could be wrong?

Wrong section
Sent from my SM-N900T using Tapatalk

6.0.4.7 is for KK bootloader. If you haven't that's why
go back to 4.6

I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?

spyvingen said:
I have kitkat cm11
maybe thats why it does not work now?
With one should i have? Link to dl pls.
Sorry if posting wrong could someone move it please?
Click to expand...
Click to collapse
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm

ratcom said:
its your bootloader thats still 4.3, cm kitkat works on the old bootloader .... just go and download a older version of cwm
Click to expand...
Click to collapse
I upgraded to samsung stock kikat before and its non reversible as i got it does that matter?

to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.

antique_sonic said:
to be frank, I never try to flash anything from ROM manager.
This tools I've left it very very long time ago.
Have you tried to reflash the KK stock firmware, since you said you are on KK already (to get your stock recovery first), make sure everything is ok. Then reflash the CWM through ODIN. Don't use ROM manager.
Click to expand...
Click to collapse
Could try that. The problem is i cant make a backup now when i dont have access to CWM
But if it is the only way sure i will try it.

[Q] SM-T537R4 Galaxy Tab 4 10.1 will not load! Only has download and stock recovery

Rooted the device with Odin. But couldn't for the life of me find a recovery for it. Flash a ton through Odin then final got a TWRP recovery to work.. When I wiped everything I was instructed to I tried to flash the rom I found (Bliss) I got a could not mount preload error.. And another error I can't recall. Then it just kept looping. So I ran the root file through Odin again.. And it now just boots straight to the Samsun logo and sits there until you hold power vol down (or up) and home till it switches to download or recovery. The TWRP is gone somehow and its stock again.
Hope this isn't confusing... I'll answer any questions and try any suggestion... PLEASE HELP

eatfleshzombie said:
Rooted the device with Odin. But couldn't for the life of me find a recovery for it. Flash a ton through Odin then final got a TWRP recovery to work.. When I wiped everything I was instructed to I tried to flash the rom I found (Bliss) I got a could not mount preload error.. And another error I can't recall. Then it just kept looping. So I ran the root file through Odin again.. And it now just boots straight to the Samsun logo and sits there until you hold power vol down (or up) and home till it switches to download or recovery. The TWRP is gone somehow and its stock again.
Hope this isn't confusing... I'll answer any questions and try any suggestion... PLEASE HELP
Click to expand...
Click to collapse
As far as I know there aren't any custom recoveries or roms working for your model number, so that's why nothing is working properly. Your only solution would appear to be to download the stock firmware and flash back to stock with Odin.

thisisapoorusernamechoice said:
As far as I know there aren't any custom recoveries or roms working for your model number, so that's why nothing is working properly. Your only solution would appear to be to download the stock firmware and flash back to stock with Odin.
Click to expand...
Click to collapse
Thanks for the link! I'll do that as soon as I get home.
Do you know if there's any way to get a custom rom onto my tablet?

eatfleshzombie said:
Thanks for the link! I'll do that as soon as I get home.
Do you know if there's any way to get a custom rom onto my tablet?
Click to expand...
Click to collapse
Unfortunately I'm fairly certain there are no custom Roms available for your tablet

thisisapoorusernamechoice said:
Unfortunately I'm fairly certain there are no custom Roms available for your tablet
Click to expand...
Click to collapse
Thats ok
I started the flsh of the stock firmware...seems hung up...does it take very long time to load?... the status hasnt changed in like 5 minutes.

did you get twrp to work? Im trying to get that installed so I can use xposed on the same model I believe sm-t537r4 I have it currently rooted

Can`t root my N9005

Hi All,
I have read through quite a lot of your threads on how to root a Note 3 and am getting nowhere. I once had it rooted and had Phronesis V4.1 and was working fine till one day it wasn't recognizing my sim card, so i tried putting Phronesis V5 on and ever since have had trouble. First it didn't work so i went onto Sammobile and down loaded Baseband Version N9005XXUGBOJ1. And have got my note 3 working again but i cant root it for some reason, when i try to go into recovery it says not rooted. It puts me into some sort of recovery when i press volume up/power/and the bottom button but when i try to it comes up with an error message in Red : Failed to verify wholefile signature, signature verified failed. This of course happened when i did have root. Any help or pointing in the right direction would be appreciated .
Norman

Have you tried flashing the latest supersu through twrp?

audit13 said:
Have you tried flashing the latest supersu through twrp?
Click to expand...
Click to collapse
Hi Audit13, Thanks for your reply. I cant put TWRP or any other recovery`s on, i put TWRP onto Odin and flashed it but it keeps reverting to the stock android recovery i have got on my device. At this precise moment i cant even get into stock recovery, i press the volume up/ power and home button whilst the Note 3 is off. It shows recovering into boot in blue and then set warranty bit: Recovery, but it just resets to starting up my phone. Also if i flash supersu will it work if i dont have a rooted device? tia

Normski15 said:
Hi Audit13, Thanks for your reply. I cant put TWRP or any other recovery`s on, i put TWRP onto Odin and flashed it but it keeps reverting to the stock android recovery i have got on my device. At this precise moment i cant even get into stock recovery, i press the volume up/ power and home button whilst the Note 3 is off. It shows recovering into boot in blue and then set warranty bit: Recovery, but it just resets to starting up my phone. Also if i flash supersu will it work if i dont have a rooted device? tia
Click to expand...
Click to collapse
Wipe your phone and reflash your stock rom egain,then flash the recovery...
Let us know! !!

jemis1983 said:
Wipe your phone and reflash your stock rom egain,then flash the recovery...
Let us know! !!
Click to expand...
Click to collapse
Ok will try thanks.

maybe you flashed the wrong recovery file.

Normski15 said:
Ok will try thanks.
Click to expand...
Click to collapse
Hi tried that wiped phone and reinstalled original stock, rooted it then put TWRP on and now i`m on a contsant loop of Recovery booting: Recovery is not a seandroid Enforcing. Set warranty bit : recovery. any help please.

Try another recovery... That'll help you out

When flashing TWRP in Odin, do not check anything except f.reset time. Flash TWRP and, when you see the word "reset" in the status window, remove the USB cable, remove battery, wait 5 seconds, replace battery, use the button combination to boot into recovery.

Thanks to everyone involved got it sorted, i am assuming i was using the wrong/or corrupt TWRP. Did what you kind people said and am back on Pronesis V5.