SM-A310F and my stupid mistake. - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Hi, I'd like to start off by saying that I'm not new with the whole rooting and recovery ordeal. I just happen to be an "OG" (or at least I'd like to call myself that) modder (android 4 and before) and stuff like this never existed.
So, I've had this phone for a while and thought I'd go ahead and slap a custom rom on it to see how it'd go. Pretty generic stuff, enabled OEM-Unlock, installed TWRP, got a custom rom I'd liked, and would you know it: after logging into my google account, I disabled OEM-unlock. Basically I soft-bricked my phone ("Custom binary blocked by FRP lock" or something). Do you guys know any way to kind of fix this? I'd tried to flash it with a 5.1.1 rom, but didn't notice that you couldn't downgrade cause android 5 security policies. I'm kind of panicking and I'd appreciate any kind of help. (Even if you can send me links to stock roms I'd appreciate it)
EDIT: Oh yeah forgot to say this: I was running android 7 Nougat before the custom rom. I think it was a custom bootloader so I might be screwed...
EDIT 2: I live in Hungary so maybe another stuff to look out for.
Cheers,
Gabe.

gabe56f said:
Hi, I'd like to start off by saying that I'm not new with the whole rooting and recovery ordeal. I just happen to be an "OG" (or at least I'd like to call myself that) modder (android 4 and before) and stuff like this never existed.
So, I've had this phone for a while and thought I'd go ahead and slap a custom rom on it to see how it'd go. Pretty generic stuff, enabled OEM-Unlock, installed TWRP, got a custom rom I'd liked, and would you know it: after logging into my google account, I disabled OEM-unlock. Basically I soft-bricked my phone ("Custom binary blocked by FRP lock" or something). Do you guys know any way to kind of fix this? I'd tried to flash it with a 5.1.1 rom, but didn't notice that you couldn't downgrade cause android 5 security policies. I'm kind of panicking and I'd appreciate any kind of help. (Even if you can send me links to stock roms I'd appreciate it)
EDIT: Oh yeah forgot to say this: I was running android 7 Nougat before the custom rom. I think it was a custom bootloader so I might be screwed...
EDIT 2: I live in Hungary so maybe another stuff to look out for.
Cheers,
Gabe.
Click to expand...
Click to collapse
I think flashing the stock rom would work, if you backed your stock rom it would be better but if not search for it on sammobile (search for model and country). Remember to use odin patched

Related

[Q] Cannot update firmware via official channels despite reinstalling stock firmware

I don't know what's going on here.
I've had a rooted phone for a while, but wanted to update to 4.3 since that came out recently.
So I've reinstalled the stock firmware on my I9505 (XXUAME2, Poland), the whole big package. Installing this went without a problem, and now I'm back with a stock ROM. I did this because I wanted to go the official update path (perhaps I don't really need this, but... well, I'm a flash-addict).
However, if I try to find a new update using the "Update" button in the "About device" menu, all I get is an information that I've already got the latest software.
KIES, on the other hand, tells me that my device's current firmware version is not supported.
What's going on here?
Shaamaan said:
I don't know what's going on here.
I've had a rooted phone for a while, but wanted to update to 4.3 since that came out recently.
So I've reinstalled the stock firmware on my I9505 (XXUAME2, Poland), the whole big package. Installing this went without a problem, and now I'm back with a stock ROM. I did this because I wanted to go the official update path (perhaps I don't really need this, but... well, I'm a flash-addict).
However, if I try to find a new update using the "Update" button in the "About device" menu, all I get is an information that I've already got the latest software.
KIES, on the other hand, tells me that my device's current firmware version is not supported.
What's going on here?
Click to expand...
Click to collapse
Hi,
Did you try Triangle Away,from the market?
It will show if you triggered the flash counter.
Having said that,you still have the old ,non-knox bootloader.
You might want to just keep that and flash custom ROMS.
They have all the goodness of official ones,but you are still free of any restrictions.
malybru said:
Hi,
Did you try Triangle Away,from the market?
It will show if you triggered the flash counter.
Having said that,you still have the old ,non-knox bootloader.
You might want to just keep that and flash custom ROMS.
They have all the goodness of official ones,but you are still free of any restrictions.
Click to expand...
Click to collapse
I've used Triangle Away before, to reset my counter. Of course, after flashing in the official firmware the phone's no longer rooted, so Triangle Away won't work.
That said, I THINK I know why the official update procedure(s) failed - I've mixed up the firmware for my product code. Apparently when I originally rooted the device I've changed the product code to BTU and have been using that ever since without really knowing about it. But now I've installed the Polish firmware XEO, and I think this is why the update process went crazy.
With regards to custom ROMs... I've already got the phone configured the exact way I like it, and I know some custom ROMs can be... quite different. Are there any specific custom ROMs you had in mind that have all the goodies of official ROMs without the restrictions you mentioned?
Shaamaan said:
I've used Triangle Away before, to reset my counter. Of course, after flashing in the official firmware the phone's no longer rooted, so Triangle Away won't work.
That said, I THINK I know why the official update procedure(s) failed - I've mixed up the firmware for my product code. Apparently when I originally rooted the device I've changed the product code to BTU and have been using that ever since without really knowing about it. But now I've installed the Polish firmware XEO, and I think this is why the update process went crazy.
With regards to custom ROMs... I've already got the phone configured the exact way I like it, and I know some custom ROMs can be... quite different. Are there any specific custom ROMs you had in mind that have all the goodies of official ROMs without the restrictions you mentioned?
Click to expand...
Click to collapse
Hi,
TA is used while you are still rooted to reset the counter.
Then, you install stock ROM/firmware.
Only you know how you like your phone,so only you can make that decision about the ROM you choose.
The main restrictions are that once you root the new firmware with the new knox bootloader, you will trigger the knox warranty,and you will never be able to flash an older firmware.
Not everyone is bothered by this,so, this is all a personal choice again.
malybru said:
Hi,
TA is used while you are still rooted to reset the counter.
Then, you install stock ROM/firmware.
Only you know how you like your phone,so only you can make that decision about the ROM you choose.
The main restrictions are that once you root the new firmware with the new knox bootloader, you will trigger the knox warranty,and you will never be able to flash an older firmware.
Not everyone is bothered by this,so, this is all a personal choice again.
Click to expand...
Click to collapse
Any chance there's a custom ROM created from the stock firmware but with the bootloader removed?
I've read about Knox and I'm kind of glad the firmware update failed, as I wouldn't feel comfortable with that "warranty void" flag...

[Q] Some Questions...

Let me start out by saying that I do try and search for my answer. I don't like to start anything before I am 100% confident. I have rooted for a while, but always followed detailed tutorials. I have model number SM-N900T, android version 4.3, Build number ends in MI7.
I keep seeing something about a reactivation lock that is supposed to be under the security part of settings. I do not see one? Am I missing something?
I do not care about KNOX tripping and warranty issues and am going to install TWRP so I can install a ROM. Do I need to root first, or just install the recovery, as the ROM I am looking at says it is pre-rooted?
If the ROM is 4.4.2 do I need to do some update before installing the ROM or will installing the ROM automatically upgrade my android version?
Most of the ROMS I see say 9005? Will these work on my phone?
Thanks for any replies everyone, I'm just paranoid about messing something up.
Hondrongo said:
Let me start out by saying that I do try and search for my answer. I don't like to start anything before I am 100% confident. I have rooted for a while, but always followed detailed tutorials. I have model number SM-N900T, android version 4.3, Build number ends in MI7.
I keep seeing something about a reactivation lock that is supposed to be under the security part of settings. I do not see one? Am I missing something?
I do not care about KNOX tripping and warranty issues and am going to install TWRP so I can install a ROM. Do I need to root first, or just install the recovery, as the ROM I am looking at says it is pre-rooted?
If the ROM is 4.4.2 do I need to do some update before installing the ROM or will installing the ROM automatically upgrade my android version?
Most of the ROMS I see say 9005? Will these work on my phone?
Thanks for any replies everyone, I'm just paranoid about messing something up.
Click to expand...
Click to collapse
You are in the wrong forum!
You probably want to look at:
http://forum.xda-developers.com/note-3-tmobile
(but MI7 might probably be a good thing since with a little care you can keep your knox warranty, however please read in that forum for specifics since there might be certain important differences).

[Q] need help with firmware 4.4.2

Hi everyone, I need advice on restoring functionality to my i9505. I Odin flashed the NA1 stock leak because I thought it was required for echoe v16 rom which seemed to work but I had no wifi so I flashed the wifi fix from the i9505 stock rom thread for the 4.4.2 stock rom but it broke the sound and I still have no wifi now I gave a buggy stock rom with no wifi no phone no messaging amongst other issues and my Knox flag is 0x1. I have tried Odin flashing all sorts of bootloader modems etc but they either don't fix anything or they have an error while trying to flash saying FAIL! (Auth) in Odin and device says SW REV. CHECK FAIL : fused : 4 , binary 3. If anyone can please help me with a solution I would be very greatfull. I have Googled and looked through a lot of threads but still haven't found an answer. I know I've made a stupid mistake, just need help now.
1. Stop of flash things without read before. Flashing old bootloaders is horrible idea. This will create a paperweight soon.
2. The unique solution u can do is:
- Flash I9505XXUFNB9 (NEE) Nordic Countries-> HERE or HERE by Odin :fingers-crossed:
thanks Joku1981, im downloading now, it was a stupid mistake, I have been flashing and modding phones for about 10 years since flashing monster packs on a Motorola E398, I don't generally make these mistakes, I did a lot of reading before attempting this and it looked like others were having success but I just misunderstood the process. I am in Australia, not sure if that matters, is there any specific process to flashing this? will there be any steps to follow flashing with oden?
dicko101 said:
thanks Joku1981, im downloading now, it was a stupid mistake, I have been flashing and modding phones for about 10 years since flashing monster packs on a Motorola E398, I don't generally make these mistakes, I did a lot of reading before attempting this and it looked like others were having success but I just misunderstood the process.
Click to expand...
Click to collapse
Im flashing for about 10 years too. But the Samsung bootloaders are one new big **** for all the people that love modify their phones
I know, its really disappointing, they should understand the potential of letting developers have access to the devices software by now, there are developers out there making way better stuff than the OEMs are. its almost starting to go backwards, you never used to have so much access as you have with the open source Android OS but now companys are clamping down on more and more of the device specific code etc.
dicko101 said:
I know, its really disappointing, they should understand the potential of letting developers have access to the devices software by now, there are developers out there making way better stuff than the OEMs are. its almost starting to go backwards, you never used to have so much access as you have with the open source Android OS but now companys are clamping down on more and more of the device specific code etc.
Click to expand...
Click to collapse
Samsung devices now: If you was lucky and you received one Samsung with android 4.2.2, DONT UPDATE IT PLS
I flashed the file successfully, but I still have no sound and no wifi, things like phone and messaging are still buggy, any other sugestions?
yes my original bootloader was pre KNOX, I know, I have already ruined it now, no going back, almost enough to put me off modding all together, think im going to be up for a new phone by the look of it.
also my android version still says 4.4.2 and baseband still I9505XXUFNA1
dicko101 said:
I flashed the file successfully, but I still have no sound and no wifi, things like phone and messaging are still buggy, any other sugestions?
Click to expand...
Click to collapse
Try to flash the combined package from here make sure to turn off your phone manually then wait atleast 10 sec and hold and press power Voldown in order to boot into downloadmode and open odin select CP/Phone ( .TAR) and flash
dicko101 said:
also my android version still says 4.4.2 and baseband still I9505XXUFNA1
Click to expand...
Click to collapse
Well because you flashed a 4.4.2 kitkat..... and instead of you writing thanks to joku1981 there's a button right over there > feel free to click
thank you to both of you guys, you have restored my phone, I am so greatful for your help and generosity I have thanked you both and I will make a small contribution for your efforts, please advise Repulsa if there is some way I can make you a small donation for your help. one more thing, I am confused now as to which roms will now be compatible with my phone, will it be safe to flash Echoe v16 now? and what roms will I have to stay away from? thank you both again so much for your help.

Which first?

Its been a few years so i was needing a refreshing (& though simple question, i cant seem to find exact answer).
I have the sm-t337a tab 4. If i plan on rooting it but i also was looking at installing a ROM, which order do i need to (or which do you recommend) do them in???
Thank you for your assistance
gdownloads said:
Its been a few years so i was needing a refreshing (& though simple question, i cant seem to find exact answer).
I have the sm-t337a tab 4. If i plan on rooting it but i also was looking at installing a ROM, which order do i need to (or which do you recommend) do them in???
Thank you for your assistance
Click to expand...
Click to collapse
You always have to root first before you are able to install a custom rom. That said, to the best of my knowledge, there aren't any custom roms available for the SM-T337A. Unfortunately, AT&T and Verizon lock the bootloader on their devices now. This means that you can't have a custom kernel or a custom recovery. Since Cyanogenmod and similar roms based off of it require a custom kernel, you can't have any cyanogen-type roms. That said, a stock based rom (anything capable of running on the stock kernel) should work fine, but as I've said, to the best of my knowledge nobody has made any roms like that for this device yet. Sorry to be the bearer of bad news.
thisisapoorusernamechoice said:
You always have to root first before you are able to install a custom rom. That said, to the best of my knowledge, there aren't any custom roms available for the SM-T337A. Unfortunately, AT&T and Verizon lock the bootloader on their devices now. This means that you can't have a custom kernel or a custom recovery. Since Cyanogenmod and similar roms based off of it require a custom kernel, you can't have any cyanogen-type roms. That said, a stock based rom (anything capable of running on the stock kernel) should work fine, but as I've said, to the best of my knowledge nobody has made any roms like that for this device yet. Sorry to be the bearer of bad news.
Click to expand...
Click to collapse
That sucks. Guess I'll have to be satisfied with just rooting it and maybe a different stock rom, if any available.
I was just searching on here & I'm not sure what instructions are the ones I need for this tab. I saw where someone says they tried towelroot & 1 other but did not work, & other similar posts, then find several posts mentioning that they have rooted it, so I'm not sure what way DOES work to root it. (I also found on another site, which I don't know if Im allowed to post the external link, "Working Tutorial How To Update/Upgrade Samsung SM-T337A To Android 5.1 Lollipop!) Needless to say Im a little unsure of what method I need to root it. ANDROID VERSION: 4.4.2 BUILD: kot49h.t337aucu1ank2
Also Is there a alternative stock based rom (with tutorial) you might recommend ?
gdownloads said:
That sucks. Guess I'll have to be satisfied with just rooting it and maybe a different stock rom, if any available.
I was just searching on here & I'm not sure what instructions are the ones I need for this tab. I saw where someone says they tried towelroot & 1 other but did not work, & other similar posts, then find several posts mentioning that they have rooted it, so I'm not sure what way DOES work to root it. (I also found on another site, which I don't know if Im allowed to post the external link, "Working Tutorial How To Update/Upgrade Samsung SM-T337A To Android 5.1 Lollipop!) Needless to say Im a little unsure of what method I need to root it. ANDROID VERSION: 4.4.2 BUILD: kot49h.t337aucu1ank2
Also Is there a alternative stock based rom (with tutorial) you might recommend ?
Click to expand...
Click to collapse
All you can do is try towelroot. If it comes back as failed, then oh well, it doesn't mess anything up. Towelroot will only work for kernel dates before July 2014 I believe. There are NO custom ROMs, no recovery, no alternatives for this tablet. No developer interest, no carrier support, so no android version beyond 4.4.2. We have been abandoned by AT&T with no way of getting any updates ever again because they locked us out. So we are stuck with a worthless pile of crap tablet that gets more laggy by the day. No more carrier variants of any device for me ever again. International only.
rootng that works
pre4speed said:
All you can do is try towelroot. If it comes back as failed, then oh well, it doesn't mess anything up. Towelroot will only work for kernel dates before July 2014 I believe. There are NO custom ROMs, no recovery, no alternatives for this tablet. No developer interest, no carrier support, so no android version beyond 4.4.2. We have been abandoned by AT&T with no way of getting any updates ever again because they locked us out. So we are stuck with a worthless pile of crap tablet that gets more laggy by the day. No more carrier variants of any device for me ever again. International only.
Click to expand...
Click to collapse
kingroot works perfectly on the T337A tab4

How to return to original firmware from CM13

Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
gabrsmn said:
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
Click to expand...
Click to collapse
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
minimale_ldz said:
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
Click to expand...
Click to collapse
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
gabrsmn said:
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
Click to expand...
Click to collapse
Flashing newer firmware won't break anything, it's a normal update. Worse thing would be if you tried to flash Lollipop over Marshmallow.
Making backup is always a good idea, do mind however, that flashing full stock firmware means overwriting your TWRP with stock recovery. Also, be aware the files you linked are actually firmware and not TWRP flashable zips.
And yes, you should be able to relock bootloader with original firmware.

Categories

Resources