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!
Related
So I am not to NOOB but I sure acted like it last night when I was way tired and tried to flash a ROM. Here is what I did...
I didn't catch that I didn't have the CWM but that I had booted into the stock recovery tool... Well I didn't before it was to late that is...
I clicked WIPE DATA
I clicked WIPE CACHE
Then noticed there was no "install from SD"
So it seems like whatever I find to install from ODIN I can't get the CWM to install so I can then flash a ROM!
I need my phone up for work, I am in HOT SH!T!
How can I either flash a rom via stock recovery "update format" OR install CMW via ODIN?
PLEASE HELP ASAP!!
Thank you
why don't you just flash again via odin and then root your phone via odin as well?
Don't quite understand whats your problem. So what if you wiped data and cache the rom is still there. Reboot normally and flash cfroot according to your firmware and then you should have cwm up and running. After that flash desired rom and the end.
Sent from my GT-I9100 using xda premium
Flash one of the CF-Root kernels through Odin, whichever one matches the firmware you're running. They have CWM baked in, along with root so you can flash a ROM afterwards.
If you can't get into download mode, turn your phone off, plug it in and hold down + power + home and it should boot into download mode. Then you can flash with Odin.
I thought the same thing, that so what that I wiped them... but when I rebooted the phone it just sits at the "Rethink possible screen"
I can get into download mode and I did find the "cf" post but I dunno what kernel I am running as I can't boot to go into settings to seek.
if you in recovery mod choose reboot, and it will be ok, than read: http://forum.xda-developers.com/showthread.php?t=1103399,
or put in download mod: turn your phone off, hold down + power + home. Then flash with Odin.
I know you probably don't want to, but you can try doing a factory reset, that should allow you to get your phone up and running. If you have gmail installed it should put all your contacts back, as long as you backed up to gmail.
If you have an old copy of titanium backup you won't loose ALL your apps, this is why I tend to back up every weekend, I'm only a week behind with everything if problems arise....
Cheers...
Flash stock rom... Download cwm and flash with odin.... Then instal rom u want with cwm...
Sent from my GT-I9100 using xda premium
like I said, I am not a noob, just made a mistake...
I found the cf-kernel page, but I dunno what kernel I am running and so I dunno what kernel to flash (It seems vital)
"just rebooting" don't work lol I wish... it hangs at the "rethink possible" boot screen...
I was rooted but running the stock rom, if I can get CWM installed I think I will be golden, but whatever I seem to flash from ODIN don't work :-( no matter what nothing will flash as "PDA" but when I flash using "phone" it seems to install "zimage" which is the embedded file and succeeds and phone reboots... but still only to the rethink possible point.
flash any stock firmware then flash supercore 2.0 and do whatever you want from there
Think i know what the problem is,i have same issue sometimes,try flashing anogher rooted Kernel through odin,make sure its like if the rom is a kj3 that it has a kj3 kernel.see if that works
ultramag69 said:
you can try doing a factory reset... Cheers...
Click to expand...
Click to collapse
Be glad to but it isn't an option in the recovery?
My options are as follows...
Reboot system now
Apply update from SD
Wipe/reset
Wipe/cache
been in similar, if not same situation, things were missing from cwm recovery, like you wrote...if memory serves me fine,
flash stock fw with pit, repartition and everything...
then some rootec kernel with recovery...
Oh sh!t... just flashed the pit file here... http://www.darkyrom.com/community/i...-with-odin/#download-a-pit-file-for-the-i9100
and odin said success... and screen went black.
Not responding at all now :-(
let's go in a safe way...as long as you have download mode, you're OK.
Go to samfirmware or somewhere on XDA and find FULL STOCK FIRMWARE with proper .pit file and flash it with odin. Not kernel, not anything that is not full rom.
since you state that you are not noob, you know what from there.
abovenbeyond said:
Oh sh!t... just flashed the pit file here... http://www.darkyrom.com/community/i...-with-odin/#download-a-pit-file-for-the-i9100
and odin said success... and screen went black.
Not responding at all now :-(
Click to expand...
Click to collapse
What on earth are you doing?
It clearly states:
I9000 & I897 owners (not I91000!!!) may also need a PIT file (also included in RE ROM ZIP files). I will explain further what it's for.
Why didn't you follow a tutorial on xda? Can you boot in download mode?
borstri said:
let's go in a safe way...as long as you have download mode, you're OK.
Go to samfirmware or somewhere on XDA and fin FULL STOCK FIRMWARE with proper .pit file and flash it with odin. Not kernel, not anything that is not full rom.
since you state that you are not noob, you know what from there.
Click to expand...
Click to collapse
Sounds amazing but after my post above I not can't get the phone to power on although I hear the laptop detect it as I attempt to power down or up, but no screen or led display...
Really worried now... ****!
Lennyz1988 said:
What on earth are you doing?
It clearly states:
I9000 & I897 owners (not I91000!!!) may also need a PIT file (also included in RE ROM ZIP files). I will explain further what it's for.
Why didn't you follow a tutorial on xda? Can you boot in download mode?
Click to expand...
Click to collapse
I flashed this...
Download a PIT file for the I9100
Download EXT4.pit file (2KB)
(for the S2 only)
battery pullout, then three button combo for download
My GS4 ATT keeps getting stuck on the Samsung Custom screen after rebooting my rom.
The initial reboot after doing a clean install works fine, but after restarting, it gets stuck.
I have tried 3 different roms so far and all have the same problem, any suggestions?
other information:
model#: sgh-1337
version 4.3
baseband:1337UCUAMDL
kernal:3.4.0-g4fe9989-dirty
what recovery
what roms did you try
by clean, i assume you wiped system also
i don't pay attn to kernel names. is that part of the rom you last flashed or did you get it elsewhere and if so exactly how did you flash it
rugmankc said:
what recovery
what roms did you try
by clean, i assume you wiped system also
i don't pay attn to kernel names. is that part of the rom you last flashed or did you get it elsewhere and if so exactly how did you flash it
Click to expand...
Click to collapse
I tried hyperdrive rls14 3 times and lquidsmooth, shostock, all have the same problem.
I flashed it through TWRP like normal, wipe, install, wipe chache ...
i might have to go back to stock via odin, but im currently running a mac.
is that kernel stock for one of the roms, if not flash rom with it's stock kernel
which twrp, 2.5.0.2 is best
rugmankc said:
is that kernel stock for one of the roms, if not flash rom with it's stock kernel
which twrp, 2.5.0.2 is best
Click to expand...
Click to collapse
its the stock kernals with the roms, im not sure which version of twrp I have because then I wont be able to boot into into rom.
ok, so you can't boot into recovery?
have you ever flashed and ran a rom successfully, which one?
if so, what has changed if anything to be a possible cause
rugmankc said:
ok, so you can't boot into recovery?
have you ever flashed and ran a rom successfully, which one?
if so, what has changed if anything to be a possible cause
Click to expand...
Click to collapse
No i can boot into recover, i cant boot into the rom after restarting (after installing the rom it will boot, but after restarting it gets stuck on boot)
I have ran many roms in the past, i flashed over stock root. I am not sure what to, and dont want to restore it completely unless its a must.
baseband is your radio, what's your Build number, if you know
i think on a mac you will need to use heimdal, this guy Ashton may be able to help if you go that route
http://forum.xda-developers.com/showthread.php?t=1917237
i just was confused. if you can't get to recovery, how did you flash 3 roms and have same issue?
rugmankc said:
baseband is your radio, what's your Build number, if you know
i think on a mac you will need to use heimdal, this guy Ashton may be able to help if you go that route
http://forum.xda-developers.com/showthread.php?t=1917237
i just was confused. if you can't get to recovery, how did you flash 3 roms and have same issue?
Click to expand...
Click to collapse
I dont think you completely understand my situation. So everything works fine, except when I restart my phone after flashing a new rom, it will get stuck on the samsung boot logo. this happens to every rom I have tried.
Bump.
gsr101 said:
Bump.
Click to expand...
Click to collapse
You do know that the first boot after flashing a rom is going to take longer than normal. I think that's what you're experiencing
jd1639 said:
You do know that the first boot after flashing a rom is going to take longer than normal. I think that's what you're experiencing
Click to expand...
Click to collapse
it boots perfectly after flashing the rom, but after i get into the rom and install stuff and then I reboot causes the phone to get stuck on the logo.
I noticed that there is something wrong with the root permissions.
gsr101 said:
it boots perfectly after flashing the rom, but after i get into the rom and install stuff and then I reboot causes the phone to get stuck on the logo.
I noticed that there is something wrong with the root permissions.
Click to expand...
Click to collapse
Try flashing super su in recovery again
jd1639 said:
Try flashing super su in recovery again
Click to expand...
Click to collapse
I have, it works but wont boot into the os unless i wipe and install the rom again
gsr101 said:
I have, it works but wont boot into the os unless i wipe and install the rom again
Click to expand...
Click to collapse
What recovery are you using?
also, i don't remember you saying what your build is, just the baseband.
these things uaually happen if you are flashing a rom not meant for your phone or an incompatible kernel
rugmankc said:
also, i don't remember you saying what your build is, just the baseband.
these things uaually happen if you are flashing a rom not meant for your phone or an incompatible kernel
Click to expand...
Click to collapse
oh, thanks for the help. I really want to run Hyperdrive RLS14 on it, so should I goto stock then update and root?
well, would like to know your build not baseband
ie, mdl, mf3, mk2
otherwise back to stock thru heimdall, since you are on mac, may be path, never used it but there is info on it thru google searches
also, if possible backing up important info on internal card and reformatting may be another option
rugmankc said:
well, would like to know your build not baseband
ie, mdl, mf3, mk2
otherwise back to stock thru heimdall, since you are on mac, may be path, never used it but there is info on it thru google searches
also, if possible backing up important info on internal card and reformatting may be another option
Click to expand...
Click to collapse
My BASEBAND says MDL, My BUILD says RLS13.
gsr101 said:
My BASEBAND says MDL, My BUILD says RLS13.
Click to expand...
Click to collapse
Still think it's an issue with your recovery. Google twrp 2.5.0.2 zip xda and flash that in your current recovery. Then flash your rom and see if you still have the problem
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.
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.
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