trying to install new.er/updated rom - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

so im trying to update my phone lately i was using dynamickat for a long time but wanted to update right not i got aryamod port to work but somethings up at first it restarts itself while doing the setup then after updating google store or any other app it just restarts itself but if im not doing anything its fine till i try installing an app store or sd card. i did everything right. id post in the rom forum post but it got closed up. id install stock rooted roms but i kinda need xposed and safestrap never wants to work with that nc1 flasher. help me please!!

gave up on that rom i have a stock rooted lollipop rom but i tried to do the nc1 flasher and just goes to stock recovery i cant find a oc1 kernel odin file since stock cant flash. otherwise ill have to go through the stock kitkat rom and redo the whole thing

Related

[Q] Stock 4.2.2 rooted could not install latest update. Stock rovery isnt working.

I changed from custom rom back to 4.12 stock and updated to 4.2.2. Main reason was camera and beatsaudio. Last week there was small update but could to install since had cwm recovery and rooted phone. I have unrooted phone but cant get stock recovery work.
Getting fed up i installed cm10.2 i love this rom but camera is **** so i want to go back to stock again. running RUU does not help either since i get error msg wrong bootloader. Help plz

Help with Rogers (SM-N900W8) device :/

So I ****** up, I'm usually good with this stuff but I don't know...
Anyways here is what happened. I had a rooted stock rom on Jellybean. Working fine I wanted to upgrade so...
I installed safestrap 3.71 and flashed the Urdroid stock rooted kitkat rom. Then I went onto ODIN and installed the files in this tutorial
http://forum.xda-developers.com/showthread.php?t=2712039
I got an error and realized crap the ATT Note 3 is not the same as the Rogers version...
ATT = SM900A
Rogers = SMN900W8
soooooo I realized I've been in the wrong forum this whole time and I was wondering what can I do to get help? Safestrap/recovery still works and I'm pretty sure I can flash JB roms still. I'm not sure which rom to use and where to go now.
What can I do to get back to stock or even better get a working Jellybean Rom?
Thanks a lot!
Okay I'm downloading the stock firmware from that sammobile and going to flash it with ODIN, hopefully should put me back to factory condition

Note 4 downgrade L/KK

Hey,
Something weird is going on with my Note 4... I updated to Lollipop 2 days ago, rooted with CF Autoroot and flashed Philz recovery, every thing seems to be ok until i tried to flash xposed, got bootloop
so i had to flash stock again, root, recovery, etc...
yesterday at night i was deleting some bloatware....i found it is a little bit annoying that now all apps come in a folder lol not like before, in all cases i deleted what i don't need, but i think i delete something important
so when i woke up today every single app get crashed after i open it....means i have to re-flash stock etc....
but what i tried to do is to restore an old backup i had on my sd card ( xnote NK4 ) and yes it boots and working perfectly without any problem !!!!
so how that happened ????
at the end its seems that we still can downgrade from Lollipop to Kitkat...
**** those who downgrade to 4.4.4 ( from a backup ) do not try to flash any kernel, just stay on the kernel you were using in the restore, otherwise you will get bootloop ***
Correct, I did downgrade yesterday from 5.0.1 stock to 4.4.4 stock.
Working normale,..
did you even read xposed thread op..?
its still not working on samsung tw roms
yes i did read that but it doesnt say that all samsung are bootloop so i just tried it, anyway i just flashed stock rooted kernel NK4 and the phone doesnt boot up lol
mrlove6 said:
yes i did read that but it doesnt say that all samsung are bootloop so i just tried it, anyway i just flashed stock rooted kernel NK4 and the phone doesnt boot up lol
Click to expand...
Click to collapse
No it won't, you are still on lolipop boot loaders so you need a custom permissive kernel to run kk roms

Soft-Brick Safestrap.

Hi, having a problem, I was getting ready to flash a custom rom on my new Att Galaxy S4 NG3, everything was ready to go I was in safestrap, advanced > formatted everything and then the battery fell out. Now all I get is the splash screen that says Samsung with the custom lock on it....
justinmillman said:
Hi, having a problem, I was getting ready to flash a custom rom on my new Att Galaxy S4 NG3, everything was ready to go I was in safestrap, advanced > formatted everything and then the battery fell out. Now all I get is the splash screen that says Samsung with the custom lock on it....
Click to expand...
Click to collapse
First, is it an S4 or S5? Double check that BEFORE trying these next steps. Find the ODIN file for your phone and you'll have to start over. ODIN, root with towelroot, install busybox, install safestrap and be on your way.
It is the S5, At&t Version, and I can't seem to find the stock ROM anywhere, I have the NG3 firmware edition.
For anyone else curios I was able to solve my problem. Although I could not find the newest exact version that was on my phone, I used the previous version from this thread:
http://forum.xda-developers.com/showthread.php?t=2785185
and was able to use odin to reflash the ROM and am now starting over with the process to safestrap and custom ROM's.

[Q] Can't Get Custom ROM to Flash on AT&T OA1 S5

I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
mnemonicj said:
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
Click to expand...
Click to collapse
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
dirtydodge said:
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
Click to expand...
Click to collapse
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
mnemonicj said:
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
Click to expand...
Click to collapse
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
dirtydodge said:
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
Click to expand...
Click to collapse
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
mnemonicj said:
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
Click to expand...
Click to collapse
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
dirtydodge said:
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
Click to expand...
Click to collapse
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
mnemonicj said:
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
Click to expand...
Click to collapse
First off you can't flash cyanogenmod cause of the locked bootloader. We have to stick with TW base roms. I like the stability about TMS2.0 plus the fact that the dev is still working on it. Most all the other devs have went to other phones. TalkingMonkeys is a great dev and is constantly working on mods and features.

Categories

Resources