Hello, I just got a new unlocked Galaxy s4 active from at&t. It is on android 4.2.2 stock rom (touchwiz). I rooted using towelroot and deleted bloatware using titanium backup. Everything was going fine until I decided to restart the phone. Now it gets stuck on the at&t logo. I have tried doing the factory reset and it completes, but it still gets stuck on the logo. I also tried wiping the cache but it says it failed. First time rooting a phone and I don't really know what I did wrong. Any ideas on how to fix this?
R0GER99 said:
Hello, I just got a new unlocked Galaxy s4 active from at&t. It is on android 4.2.2 stock rom (touchwiz). I rooted using towelroot and deleted bloatware using titanium backup. Everything was going fine until I decided to restart the phone. Now it gets stuck on the at&t logo. I have tried doing the factory reset and it completes, but it still gets stuck on the logo. I also tried wiping the cache but it says it failed. First time rooting a phone and I don't really know what I did wrong. Any ideas on how to fix this?
Click to expand...
Click to collapse
Reflash the stock firmware. Other people may have some ideas that don't involve wiping your phone, but reflashing will work if you don't mind losing your data. Check the sticky in the General section for instructions.
Ok, will do. Can I reflash to a higher stock firmware?
Devo7v said:
Reflash the stock firmware. Other people may have some ideas that don't involve wiping your phone, but reflashing will work if you don't mind losing your data. Check the sticky in the General section for instructions.
Click to expand...
Click to collapse
How do I know what firmware I was on without being able to boot the phone?
R0GER99 said:
How do I know what firmware I was on without being able to boot the phone?
Click to expand...
Click to collapse
You said you were on 4.2.2, so it's safe to assume it was MF3. In reality it doesn't matter as long as you're flashing 4.4.2 .
I went through and installed the ML2 firmware and everything went fine, until I went to boot it. It starts with the samsung logo, then says recovery booting, then gives an error and says the system software is not authorized by at&t. Anyone know how to bypass this?
R0GER99 said:
I went through and installed the ML2 firmware and everything went fine, until I went to boot it. It starts with the samsung logo, then says recovery booting, then gives an error and says the system software is not authorized by at&t. Anyone know how to bypass this?
Click to expand...
Click to collapse
I would flash the NE3 firmware.
Devo7v said:
I would flash the NE3 firmware.
Click to expand...
Click to collapse
I flashed the NE3 firmware and I'm still getting the at&t error. When I go into download mode again it says the binary is custom but the system status is official. Don't know if that was helpful or not. I'm reading around that I have to flash a stock kernal too? (which I don't know how to do). ANY help is much appreciated.
I also just noticed that when the at&t error message pops up in the top right in red it says "SECURE FAIL:KERNAL". So now i definitely believe it is the kernal that is the problem.
Holy crap! I got it to work! I decided to try and flash the bootloader ( which it says not to in the tutorial) and it worked! Only thing I had to do was re-wipe it and wipe the catch. It hung at the at&t logo for a while (which scared me) but it eventually went through! Thank you for the help and sorry for almost spamming.
Related
well I froze some apps and now my phone is stuck at the Samsung logo.
I can reboot into recovery and have tried to reset my phone with no luck.
is there a way to re-flash the factory rom ? or restore the image through Odin ?
search on Google and here but unsure of the correct version.
any help would be great !
thanks
wuelf
no one has any thoughts ?
Will need to know what firmware you were running? If its MJ5 then call att or sammy get warranty replacement because there is no odin file for it.
In case you are lucky and have MI9 the follow the link below.
http://www.androidrootz.com/2013/10/how-to-unrootunbrick-at-galaxy-note-3.html
wuelfman said:
well I froze some apps and now my phone is stuck at the Samsung logo.
I can reboot into recovery and have tried to reset my phone with no luck.
is there a way to re-flash the factory rom ? or restore the image through Odin ?
search on Google and here but unsure of the correct version.
any help would be great !
thanks
wuelf
Click to expand...
Click to collapse
not sure of the firmware. that's why i have done nothing yet.
I played it safe and called AT&T there sending a replacement out.
Anything i need to do to the phone ? i reset the phone in the recovery screen.
it is rooted
What method did you use to root it?
wuelfman said:
not sure of the firmware. that's why i have done nothing yet.
I played it safe and called AT&T there sending a replacement out.
Anything i need to do to the phone ? i reset the phone in the recovery screen.
it is rooted
Click to expand...
Click to collapse
Root de la Vega
[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S
Just re-install your back up
Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?
Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.
There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull
daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.
Update odin and change usb cable and port.
Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.
Cheers for the helpful as well as not-so-helpful responses, all back up and running now.
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Matthew98405 said:
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Click to expand...
Click to collapse
First off you need to give more info about your phone. What build are you on 5.0, 4.4.4 etc. How did you get on that build. Ota update or custom update. We can't really help you unless we know what your running.
dirtydodge said:
First off you need to give more info about your phone. What build are you on 5.0, 4.4.4 etc. How did you get on that build. Ota update or custom update. We can't really help you unless we know what your running.
Click to expand...
Click to collapse
I had 5.0 via OTA
Matthew98405 said:
I had 5.0 via OTA
Click to expand...
Click to collapse
I'll search and see what I can find. Try searching for the OC4 firmware. if I find something i'll post it here
Matthew98405 said:
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Click to expand...
Click to collapse
if you can go into download mode then don't worry you can download another official firmware & flash it.
The firmware you tried & failed may be corrupt file so download new one & try.
Make sure your battery is more than 50%.if not know the battery level do not flash go to repair centre.
Sent from my SM-G900H using xda Forum
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
You can try this. Make sure you are using Odin 3.09. You will need the OC4 stock partitions located at the bottom of the first post. That might work.
I just thought of this, does it matter what cable I use?
(Galaxy S5 USB 3.0 cable or standard micro USB)
Because I just used a regular cable and it worked!
Matthew98405 said:
I just thought of this, does it matter what cable I use?
(Galaxy S5 USB 3.0 cable or standard micro USB)
Click to expand...
Click to collapse
It don't matter. As long as Itty is a good working cable
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Matthew98405 said:
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Click to expand...
Click to collapse
So your back up and running now?
dirtydodge said:
So your back up and running now?
Click to expand...
Click to collapse
Yup, and I restored everything!
Any idea why odin kept failing to flash a custom recovery?
Matthew98405 said:
Yup, and I restored everything!
Any idea why odin kept failing to flash a custom recovery?
Click to expand...
Click to collapse
Because your running 5.0 ota. You can't root that version yet plus they only custom recovery that we have on the AT&T S5 is either safestrap or Flashfire which is still in testing faze. You'll need to wait til you can root the ota 5.0 since it has different bootloader.
Ok, thanks, so I can stop messing up my phone.
Matthew98405 said:
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Click to expand...
Click to collapse
How did you get it to restore? Im stuck at a soft brick on my s5 at&t with the 5.0 ota bootloader. Please help
---------- Post added at 07:48 AM ---------- Previous post was at 07:12 AM ----------
Matthew98405 said:
I had 5.0 via OTA
Click to expand...
Click to collapse
If u need help i found solution of the same problem. lemme know if u do
sir i have tried to downgrade my galaxy s5 at&t by odin
but odin fails and i,m still stuck on firmware error ..
what i can i do?
shreesam09 said:
sir i have tried to downgrade my galaxy s5 at&t by odin
but odin fails and i,m still stuck on firmware error ..
what i can i do?
Click to expand...
Click to collapse
What firmware were you on originally? Sounds like you we're on 5.0 or above . If so you will have to flash a pure stock rom of the same back to it . And no rooting for any thing above 4.4.4
Sent from my SM-G900F using XDA-Developers mobile app
G925AUCS5DPJ1 ODIN firmware for AT&T S6 edge which features wifi calling and October security patch.
http://downloadmirror.co/Urj/G925AUCS5DPJ1.zip
verify???
does this work???
my phone is fac unlock will i lose anything?
Working Fine
xghostyxjokerx said:
does this work???
my phone is fac unlock will i lose anything?
Click to expand...
Click to collapse
It is working fine on my device , it doesn't effect the unlock, i'm using it in India
When i flash via odin it deletes all data or only update???
Erases the device
RikiMKD said:
When i flash via odin it deletes all data or only update???
Click to expand...
Click to collapse
Odin updating method always erases the data on phone(factory reset)
santhi4110 said:
Odin updating method always erases the data on phone(factory reset)
Click to expand...
Click to collapse
F*CK
thanks
santhi4110 said:
It is working fine on my device , it doesn't effect the unlock, i'm using it in India
Click to expand...
Click to collapse
Please help! After flash this ROM from odin, It won't boot up and stuck at Android Recovery screen. It said dm-verification fail.... need to check DRK first......
Can some one give me the link to the file to fix this issue please? I just found the file G925F_6.0.1_fixdrk. I did not see the file to fix G925A.
Thanks in Advance!
Works very well installed it directly from 5.1.1 with BOJ9
Thanks!
Worked for me as well, but i noticed by battery is draining faster. When my screen is on you can just see the battery vanish no matter what application i use. I came from CPF1 to this and i am thinking of going back since i could get a day and some on my phone..
Running factory stock AT&T firmware.
worked fine for me from Vietnam
I had no trouble with this, and was actually the only firmware that fixed the issue I created during a hastily thought out root attempt.
Appreciate it
I'm in Georgia too so nobody should have any trouble if you set up Odin correctly.
You will have to re-flash another modem, but it gets the phone to boot correctly.
I woke up and my phone had a message saying it was ready to update to N910TUVS2EQE2. Has anybody updated and rooted this fw yet?
I also recieved the update, I won't update for that reason. But the notification is annoying.
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Unless T-Mobile has suddenly reversed a long-standing policy and locked the bootloader on a previously unlocked device (something I have not ever heard of for any device), you can still flash TWRP recovery from Odin and then flash SuperSU from recovery, which does not modify the system partition. This should just be a minor security update for Marshmallow and not an update to Nougat, which would have much bigger compatibility consequences but which should still be rootable by the above method.
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Would be great if we could get a nougat release.
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
It is annoying as F!!!!! Every 6 hrs or so it nags the F!!!! outa you!
m4f1050 said:
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
Click to expand...
Click to collapse
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
Ok thanks.
t-mobile SM-910T
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
where could I get the QE2 file?
Lsanc1170 said:
where could I get the QE2 file?
Click to expand...
Click to collapse
Not going to say what others say all the time, but I searched for it. (I Googled it.) If you want to easily root it and already have TWRP recovery, go to this post:
https://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
If you want the ODIN version, go to this link:
https://samsunggalaxyrom.com/2017/0...sm-n910t-n910tuvs2eqe2-marshmallow-6-0-1.html
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
what is Smores Rom? what MM base does it use and what are it's features?
slaapliedje said:
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Click to expand...
Click to collapse
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
anyone getting better or worse signal with the QE2? .... feedback?
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
jnyfive said:
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
Click to expand...
Click to collapse
It was the USB cable. Tried different cable and port. Tada.
f4phantomii said:
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
Click to expand...
Click to collapse
That did seem to help, and oddly enough one of the watch faces I'd bought that wouldn't install now installs and works fine.
jnyfive said:
It was the USB cable. Tried different cable and port. Tada.
Click to expand...
Click to collapse
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
jnyfive said:
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
XeoNoX said:
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
Click to expand...
Click to collapse
TMO Note 4, baseband version N910TUVS2EQE2, tried lineage-14.1-20170725-UNOFFICIAL-trltetmo.zip and RR-N-v5.8.2-20170303-trltexx-Official.zip
Sent from my SM-G955U using Tapatalk