I bought a second hand galaxy note 5, on the back cover of the phone the model is written SM-N920C but in download mode is written SM-N920D ! Nevertheless when I check the model at "setting/about the device" the model was SM-N920I
The problem started when my I discovered that my note 5 was flashed with venom rom before my purchase, then I accidentally formated all system files so the phone stuck in Android logo, I tried to flash the phone using Odin and SM-N920c but Odin said FAILED just just when I click start and I attached a photo shows this error in Odin.
Please help me to find the SM-N920D stock firmware.
Why are you checking all those boxes? Just download single Odin file from Sammobile.com and flash with AP checked only. Directions are found on their firmware download page.
If the device has previously been rooted, then you'll need to re-root, otherwise you'll have no deep sleep (high idle battery drain). There is no known alternative to this.
Best of luck
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
UpInTheAir said:
Why are you checking all those boxes? Just download single Odin file from Sammobile.com and flash with AP checked only. Directions are found on their firmware download page.
If the device has previously been rooted, then you'll need to re-root, otherwise you'll have no deep sleep (high idle battery drain). There is no known alternative to this.
Best of luck
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
Click to expand...
Click to collapse
The issue is multiple models. It's mentioned differently on the back, download mode and the device settings so getting the right firmware was the main concern.
On previous thread, 920D was found to be the probable model due to same being mentioned in download mode, but that means it could be a Docomo variant and the firmware isn't easy to find.
RazorMC said:
The issue is multiple models. It's mentioned differently on the back, download mode and the device settings so getting the right firmware was the main concern.
On previous thread, 920D was found to be the probable model due to same being mentioned in download mode, but that means it could be a Docomo variant and the firmware isn't easy to find.
Click to expand...
Click to collapse
So you couldn't be bothered answering my question that was to ultimately help you. It's quite obvious you have no idea what you were doing, so question asked, advice given,..... and subsequently ignored. Never mind. Please don't respond, because I don't want to waste any more of my own very precious and limited time.
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
UpInTheAir said:
So you couldn't be bothered answering my question that was to ultimately help you. It's quite obvious you have no idea what you were doing, so question asked, advice given,..... and subsequently ignored. Never mind. Please don't respond, because I don't want to waste any more of my own very precious and limited time.
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
Click to expand...
Click to collapse
Wow.
If your highness could have read the post you'd know I'm not the OP. I indicated the main issue which remains: the correct device model and the correct firmware.
Learn to read next time you jump in.
RazorMC said:
Wow.
If your highness could have read the post you'd know I'm not the OP. I indicated the main issue which remains: the correct device model and the correct firmware.
Learn to read next time you jump in.
Click to expand...
Click to collapse
Yes. WOW
OP was using Odin incorrectly which gave him ZERO chance to flash anything successfully !!!
That and the additional info I provided stands as 100% correct, so both you and OP did not realise that and dismissal shows the low level of competency to use the basic tools. That's the point. No more, no less.
UN-recognized Developer of my SkyHigh Kernel v5.8.x powered SM-N920C
Related
I had battery issues with my Note GT-N7000. I purchased the original battery from samsung service center. Phone did restarted several times due to low battery. After one such incident it was not accepting my correct pattern. After some time it just stopped getting start up.
Then i tried to enter into recovery mode. It got stucked at android green logo, wheel spinning every single time.
But download mode is still working. I tried to re-flash it with stock firmware as i was running it before this problem occurred (stock with root).
I followed flashing instructions extremely carefully and as they instruct. When i put my phone into download mode, it got successfully recognized by my computer, But while flashing it got stucks at flashing factoryfs.img, ""NAND write start"" and followed by ""complete write operation failed"".
I did changed my original usb cable to another original cable. My antivirus and firewall are turned off permanently. I did tried it on another computer but same result. Downloaded my firmware from sammobile twice. Did tried different Odin versions from 1.83 to 3.07. But no luck at all. I am attaching my screenshots so that you can have a look.
Please help me out in any way you can. Any links or help will be highly appreciated from the bottom of my heart. Thanks in advance for your reply.
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your quick response. I do not have a ROM that require me to change PIT information. I was on pure stock with root before this issue came up. I did unchecked reset time but same error came up.
Different partition scheme...? As far as i know, i didnt do anything to my partitions.
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
ThaiDai said:
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
Click to expand...
Click to collapse
So is there any possibility of restoring the data?
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
I do have the backup but its more than 2 months old...but i cannot go into stock recovery....i should have installed cutom recovery. Any links to follow or any proper guides to come out from it?
http://forum.xda-developers.com/showthread.php?t=1667886
ThaiDai said:
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
As per the article and since i cannot enter into recovery mode, i tried all the PIT files provided with stock rom. But nothing has worked. Every time Odin is failing. I am attaching the screenshot of the same. I did tried to flash speedmod kernel but didnt got success message from Odin. Kindly help me.
i have used custom PIT files due to which my binary counter has increased(i dont care as its out of warranty). My phone shows a yellow warning sign on bootup and now it just dont even start the recovery mode and shows that yellow warning sign when i try to enter recovery.
Download mode is still working but i am unable to perform any write operation. NAND operation is failing everytime. When i used PIT files, it says re-partition operation failed. I can only try things mentioned in the above posts only when i can enter recovery.
Will someone be kind enough to help me out on this one as i really need urgent help? Please help me out guys.
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
ThaiDai said:
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
Click to expand...
Click to collapse
Thanks for replying. I did read that article carefully but all steps and troubleshooting is valid only and only when your phone's recovery mode is working. In my phone, only download mode is working. So all those steps are not applicable to me.
However i went for case B where he has described solution if we are unable to access recovery mode and suggested to use blind method to use custom pit files. I followed him but it didn't worked out for me. None of the pit files worked for me and i just ended up raising my binary counter to 2 now.
I am not receiving any replies from people(Only 2 or 3 kind people like you have replied, i appreciate it). I am not getting support. Its reallly sad just because my phone is little old now.
Even if i didn't find any solution and my phone becomes a brick( i guess it has become by now) it is still fine for me But the most sad thing is no one cares to reply on a community which was built to help each others. I am continuosly searching for solutions now. Lets see how far i can go. Thanks for your time. Do let me know if you come across any thing or i am ready to try any solution/troubleshooting steps.
nokiamodeln91 said:
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
Click to expand...
Click to collapse
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
vinay28761 said:
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
Click to expand...
Click to collapse
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
vinay28761 said:
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
Click to expand...
Click to collapse
Have you tried another pc, and genuine USB cable by Samsung?
nokiamodeln91 said:
Have you tried another pc, and genuine USB cable by Samsung?
Click to expand...
Click to collapse
Yes i tried on different pc, different cables(all are genuine)
Hello Everyone,
Today we'll be unlocking the Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung, which both required you to root your Galaxy S6 SM-G920T. I will guide throughout the steps to root your phone without tripping the knox counter, which will allow us to use one of the programs above. We will use the (sboot.bin) which allows their service centers to do flashing and repairs to the device without tripping the Knox counter. The modified bootloader also disables write protection on the device. Once you are done rooting and unlocking the Galaxy S6 SM-G920T, we will restore the official firmware 5.1.1. Don't worry, your phone is unlock permanently regardless of the times you restore the phone.
The steps to root your Samsung Galaxy SM-G920T 5.1.1
1. Install Samsung USB Drivers
2. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
3. Plug phone in and wait for drivers to install if necessary.
4. Download Odin
5. Download sboot.bin for Galaxy S6
6. Open odin and then you should now see phone’s modem port highlighted in blue.
7. Click on BL tab and select the correct sboot.bin that you downloaded above. Then click start.
8. When phone comes back on, power it off again and put into download mode.
9. Download UniBase_BOG8_v2
10. Open odin again and this time select AP tab and select UniBase_BOG_V2 file and click start.
11. You're Done!!!
When the phone turn on, it will be rooted. To verify that knox has not been tripped go back to download mode and it should still say KNOX WARRANTY: 0 (0X0000). Now you can go ahead and unlock your Samsung Galaxy SM-G920T 5.1.1 using the Z3X Samsung Tool or Octopus Box Samsung. The sboot.bin isn’t playing very well, causing issues with Calls and Fingerprint sensor, but it is only for the meantime until you restore your phone back to the stock firmware.
Restoring your Samsung Galaxy SM-G920T to the stock firmware 5.1.1
1. Download the SM-G920T stock firmware
2. Open and extract the firmware file, then you should get the a file in .tar.md5 format.
3. Put the phone in download mode by: Power phone off then press and hold Volume down, home and power keys at same time until you see warning screen then let go and hit volume up one time.
4. Open odin and then you should now see phone’s modem port highlighted in blue.
5. Click the AP button tab and select G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
6. Make sure Re-partition checkbox is NOT selected, under the Options tab. Click start and wait for it to finish completely.
7. Enjoy!!! The G920TUVU2COF6 Android 5.1.1 firmware on your Galaxy SM-G920T.
I hope this guide helps everyone who wants to unlock their Samsung Galaxy SM-G920T, but needs their phone rooted first temporarily.
Will this work if I'm on the G920TUVU2COF8 build?
It may work!
yoderz said:
Will this work if I'm on the G920TUVU2COF8 build?
Click to expand...
Click to collapse
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Any chance we could get links to the files you reference? Thank you in advance.
ron.cabanillas said:
I'm sure it works on the G920TUVU2COF8 build, but I'm not 100% sure. If anything, you can always go restore your phone through odin.
Click to expand...
Click to collapse
Can confirm it works. Went my own route on some things but Knox is 0 and SuperSU and TWRP are installed and working
Use the Search Engines!
LPoirierIV said:
Any chance we could get links to the files you reference? Thank you in advance.
Click to expand...
Click to collapse
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Anyone with some credibility willing to try this? Or have tried it... No offense but the two people that posted have a combined 7 posts...
Sent from my SM-G920T using Tapatalk
So at the end of the step I'll end with stock of6 with root?
Will this deleted my saved data and apps?
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
ron.cabanillas said:
I can't post the file links here, I would recommend you to use the search engine such as: Google, Bing, Yahoo and others to find the files you need. The files will be in the first two pages of the search engines.
Click to expand...
Click to collapse
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
It should work without problems
noodlev1 said:
I found this site if with links if anyone wants to try it out.
I haven't tried it myself so as always at your own risk.
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
Click to expand...
Click to collapse
These link should work fine with your galaxy s6 SM-G920t
You have to Root, unlock and restore
LPoirierIV said:
Yeah, I'm familiar with Google and the like. I just thought it may make things easier on people if there were links to the files since this was put together as a guide of sorts.
I ended up using the guide that noodlev1 posted since it came up frequently in the search for the needed files. I tried to post it earlier but I'm not cool enough to post links yet. I can confirm that I was able to root a bone stock sm-g920t without tripping knox.
As far as the sim unlock goes, still not able to successfully keep the sim unlock after a factory reset.
Click to expand...
Click to collapse
The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock.
It should work fine
noodlev1 said:
Were you on COF8? I want to try when I have a little time but I've been reading some people are having issues with ODIN on COF8.
Click to expand...
Click to collapse
Regardless of the firmware COF8 or COF6, you must have the full stock firmware to restore your phone after it rooted and unlocked.
I can't post the link Yet!
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: this seems to be a much better guide
http://androiding.how/root-t-mobile-s6-and-s6-edge-on-5-1-1-without-tripping-knox-counter/
edit: and here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
I more than glad to post the link, I don't have any problems. The forum rules don't allow me yet to post the links. The guide you found have the link everyone needs too.
It should work Too!
LPoirierIV said:
I honestly forget which baseband I was on. I spent all day flashing different builds to try to get the sim unlock to stick. I'm currently on COF9 on a metro pcs rom for the sm-g920t1 in hopes that I can receive a working unlock code. (Metro PCS rom is the only way to enter an unlock code apparently.)
Click to expand...
Click to collapse
The latest Tmobile is COF8, regardless COF8 or COF6 build you can unlock it. The Steps are easy, You must root the phone, unlock using Z3X Samsung Tool or Octopus Box Samsung and then restore the phone back to the stock firmware. Regardless of how many times you restore or update, your phone will always be unlock. Now you can also flash to metro pcs, but you have to stay with the metro pcs after you unlock it with the code.
mrvirginia said:
you could always PM one of these guys with the links...
very hard to follow a guide without links. granted there is google but who knows if what anyone finds is exactly what you used.
edit: here's the original thread http://forum.xda-developers.com/tmo...root-g925t-g920t-5-1-1-tripping-knox-t3149653
Click to expand...
Click to collapse
True i posted there a compilation to root without triping knox and on cof8. Must be on page 24 i think. And the md5 of sboot number to compare from ones in google
rooted but issues
both methods worked for my phone. got my phone rooter and unlocked. but i keep getting security threat warning if i stay rooted
when i press the power button i can see the "Samsung galaxy note 4" thing and then after a couple seconds it does it all over again.
https: //gyazo.com/ 7253cff1fd13dba02df89eae9df6d1a1 (sorry cant post links yet delete spaces)
i downloaded the stock firmware from Sammobile and it still will not work.
i went to tmobile and told them this is happening they said Samsung will send you a new phone but i didn't tell them my phone is rooted
does anyone think that they will not give a new phone if i say anything?
i tried putting TWRP and starting but the most it goes to is download mode. a least it turns on... :crying: :crying:
please someone help me this is the only phone i have
EDIT: is there a way to make the knox counter 0x0 from 0x1? if can do that i would send the phone to samsung
when i go into download mode it says "SYSTEM STATUS: CUSTOM" even though i restored everything to the official firmware
re: boot screen blinks
proman505 said:
when i press the power button i can see the "Samsung galaxy note 4" thing and then after a couple seconds it does it all over again.
https: //gyazo.com/ 7253cff1fd13dba02df89eae9df6d1a1 (sorry cant post links yet delete spaces)
i downloaded the stock firmware from Sammobile and it still will not work.
i went to tmobile and told them this is happening they said Samsung will send you a new phone but i didn't tell them my phone is rooted
does anyone think that they will not give a new phone if i say anything?
i tried putting TWRP and starting but the most it goes to is download mode. a least it turns on... :crying: :crying:
please someone help me this is the only phone i have
EDIT: is there a way to make the knox counter 0x0 from 0x1? if can do that i would send the phone to samsung
Click to expand...
Click to collapse
Don't worry, they will not ask you anything about knox or root.
Tmobile won't even look for root or knox in the first place unless you tell
them all those details.
Also you do not need to exchange your phone because it's a simple fix.
You must have installed or flashed something which is not compatible
with your N910T Tmobile phone which caused the issue you are having.
The only reason you have not had any luck in fixing it yourself is the fact
that you do not have enough experience yet to figure it out and you have
not read enough posts here in xda about your particular issue.
The problem you are having with your phone is not a new one, many people here
have had the exact same problem with their phones and have solved the problem.
The first thing you need to remember is to always follow the instructions to a "T" before
flashing firmwares, roms, kernels, recoveries, themes and any mods or addons.
If you do not fully understand the posted instructions here in xda then post a question
regarding your specific issue before you do anything.
Good luck,
Have a great day!
Sorry, but currently your warranty is void forever.
Are you following Odin instructions correctly? <-Most important step
Are you flashing the correct firmware for your phone? <-Also important
Have you tried different versions of Odin?
Are you getting a PASS when using Odin?
Misterjunky said:
Don't worry, they will not ask you anything about knox or root.
Tmobile won't even look for root or knox in the first place unless you tell
them all those details.
Also you did not need to exchange your phone because it's a simple fix.
The only reason you have not had any luck in fixing it yourself is the fact
that you do not have enough experience yet to figure it out and you have
not read enough posts here in xda about your particular issue.
The problem you are having with your phone is not a new one, many people here
have had the exact same problem with their phones and have solved the problem.
The first thing you need to remember is to always follow the instructions to a "T" before
flashing firmwares, roms, kernels, recoveries, themes and any mods or addons.
If you do not fully understand the posted instructions here in xda then post a question
regarding your specific issue before you do anything.
Good luck,
Have a great day!
Click to expand...
Click to collapse
i am 100% sure that i flashed the right stuff. the phone worked perfectly but then it just turned off and then got stuck in a bootloop for some reason. im gonna try to send it to samsung and not say anything about rooting it hopefully they will fix it
if you dont mind linking me what firmware i should use to restore it. i dont care about my data its already gone anyway.
Edit: how do i make the system status official because it says custom right now
xanmato said:
Sorry, but currently your warranty is void forever.
Are you following Odin instructions correctly? <-Most important step
Are you flashing the correct firmware for your phone? <-Also important
Have you tried different versions of Odin?
Are you getting a PASS when using Odin?
Click to expand...
Click to collapse
yes if you look at the link in the post odin seems to have no errors.
i followed the instruction right from sammobile and many youtube videos
www .sammobile .com /firmwares/download/46452/N910TUVU1COD6_N910TTMB1COD6_TMB/
thats what i used
I was using safestrap to try and install a custom rom, I wiped my stock rom but my phone ended up dying (I didn't see that the charger wasn't plugged in) now I can't do anything at all. IT just gets stuck on the samsung galaxy s5 logo. I cannot flash any AP I just get an auth failed error. I tried using the G900AUCU3BOC4_OneClick but I get an error on that as well. Please help me. I figured that I don't have an OS to boot into now. And I cant downgrade from 5.0 am I screwed?
So you can't put your phone into download mode and ODIN your old firmware back on to the phone?
Please post everything ODIN shows when you attempt so we can try and help you further. Might want to try flashing with the BL and PIT file as well.
P.S. I don't know what G900AUCU3BOC4_OneClick is, but google took me to
http://www.theandroidsoul.com/att-galaxy-s5-lollipop-update-odin-firmware-80652/
And that doesn't look legit. Make sure you get all of your firmwares from here or sammobile.com. The "Odin" on that page doesn't even look like odin.
at&t s5 active sm-g870a
I was trying to root my phone following instructions on this site.
I installed the NE4 that was about 10+mb.
then I got stuck on the screen with red font that says "android system recovery <3E>"
I can still flash in download mode.
I attempted to install the full NE4 available from this site which is about 2.3 gig and it says FAIL! (Auth)
So then i attempted to load NG3 available from this site and it was sucessful but I'm still stuck on the "android system recovery boot.
Would anyone happen to know where I might get the "G870AUCU280F3 ROM"?
Also does anyone know what NAND erase all does when the box is checked in Odin 3.09?
Im thinking about checking that box and trying again.
for now I'm thrilled that I can still get to download mode and I don't want to mess that up.
In general section.
Sent from my SAMSUNG-SM-G870A using Tapatalk
XRange said:
In general section.
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
thank you so much sir, but i do not understand your post.
I do very little with computers and internets and forums.
I've been scouring this site for the info i need and I'm either not smart enough to know what i'm looking for or this site is so vast that it may take more than a few days to learn how to navigate it.
I will say that I find it unsettling that the forum doesn't seem to recognize that our phones (sm-g870a) even exist, as evidenced by typing s5 active in the equipment box.
but meanwhile i will search for a general section.
Sean89us said:
So you can't put your phone into download mode and ODIN your old firmware back on to the phone?
Please post everything ODIN shows when you attempt so we can try and help you further. Might want to try flashing with the BL and PIT file as well.
P.S. I don't know what G900AUCU3BOC4_OneClick is, but google took me to
http://www.theandroidsoul.com/att-galaxy-s5-lollipop-update-odin-firmware-80652/
And that doesn't look legit. Make sure you get all of your firmwares from here or sammobile.com. The "Odin" on that page doesn't even look like odin.
Click to expand...
Click to collapse
I can get into download mode just fine. However, when I try to flash it. I get the fused binary error. Regardless of the firmware.
squirt r6 said:
thank you so much sir, but i do not understand your post.
I do very little with computers and internets and forums.
I've been scouring this site for the info i need and I'm either not smart enough to know what i'm looking for or this site is so vast that it may take more than a few days to learn how to navigate it.
I will say that I find it unsettling that the forum doesn't seem to recognize that our phones (sm-g870a) even exist, as evidenced by typing s5 active in the equipment box.
but meanwhile i will search for a general section.
Click to expand...
Click to collapse
Squirt,
if you have a question, please submit your own question in this thread instead of hijacking somebody else's question with an off-topic one. I suggest you take XRange's advice and check the "General" section of the "AT&T Samsung Galaxy S 5" thread.
http://forum.xda-developers.com/att-galaxy-s5/general
Had you checked the general section, you would see that the 4th post down is exactly what you are looking for.
http://forum.xda-developers.com/att-galaxy-s5/general/how-to-update-to-g870aof2-5-0-keeproot-t3161733
Also, S5 actives do not need a separate thread, they are identical hardware-wise to the S5.
---------- Post added at 08:33 AM ---------- Previous post was at 08:25 AM ----------
rbxrootx said:
I can get into download mode just fine. However, when I try to flash it. I get the fused binary error. Regardless of the firmware.
Click to expand...
Click to collapse
At this point I recommend you try and use Samsung's Kies software to restore your phone to factory, then you can start over with rooting or flashing roms.
Guide here:
http://forum.xda-developers.com/showthread.php?t=1984717
Please note that the link on that page to download kies is broken, so you can find kies here (you will want to download kies3):
http://www.samsung.com/in/support/usefulsoftware/KIES/
Good luck, and let us know how it goes.
Sean89us said:
Squirt,
if you have a question, please submit your own question in this thread instead of hijacking somebody else's question with an off-topic one. I suggest you take XRange's advice and check the "General" section of the "AT&T Samsung Galaxy S 5" thread.
http://forum.xda-developers.com/att-galaxy-s5/general
Had you checked the general section, you would see that the 4th post down is exactly what you are looking for.
http://forum.xda-developers.com/att-galaxy-s5/general/how-to-update-to-g870aof2-5-0-keeproot-t3161733
Also, S5 actives do not need a separate thread, they are identical hardware-wise to the S5.
---------- Post added at 08:33 AM ---------- Previous post was at 08:25 AM ----------
At this point I recommend you try and use Samsung's Kies software to restore your phone to factory, then you can start over with rooting or flashing roms.
Guide here:
http://forum.xda-developers.com/showthread.php?t=1984717
Please note that the link on that page to download kies is broken, so you can find kies here (you will want to download kies3):
http://www.samsung.com/in/support/usefulsoftware/KIES/
Good luck, and let us know how it goes.
Click to expand...
Click to collapse
Thank You sean89us, and sorry I didn't mean to hijack your thread RobotX, i just figured that if were in the same predicament whatever fixes yours may fix mine.
My bad
kies says it is not compatible with the phone so I had to install a new program which acted like it was going to do the trick. After 3 hours, It quit and told me that it was unable to complete the task.
Hi Everyone, If this is the wrong place to post this plz MODERATORS move it to correct place..
Ok so we all know what safestrap is, and that it's not TWRP really...
We also know that the bootloader on the SM-N900A isn't unlockable...
So I usually develop stuff for LG devices, but I got hands on an old Note 3 from At&t and want to
find a way to get past the limitations of Safestrap and the roms are all mostly lollipop K.K or J.B based.
without the bootloader unlocked we can't change the kernel away from stock...
Well I've been reading some things in reddit about S8 and S8+ etc.
and supposedly they have patched Odin not to check model numbers etc.
same with S9 see here:
https://forum.xda-developers.com/galaxy-s9/how-to/how-to-flash-u1-firmware-to-device-t3765200
and so what I'm thinking is...
The modded/patched Odin has the model-ID and SHA hash check disabled, therefore allowing you to flash an unbranded "U1" firmware onto a branded "U" phone and vice versa.
As of now this works on most US Qualcom (QC) models, but an increasing number of international Exynos (EX) models now include a new RMM security which prevents this kind of cross-flashing unless you first disable the RMM, by flashing an RMM-Disabler package through TWRP.
Click to expand...
Click to collapse
if we use this method to flash the tmobile branded firmware for the note 3 will we then be able to simply boot to TWRP This device has no fastboot...
If this seems like a really bad stupid Idea please say so and explain exactly why.
If this seems like it might work please explain how and why.
If you have tried this please let me know what the outcome was.
Thanks for reading
just looking for more input before I FRY a thousand dollar phone
old as it is it's still nice.
Would you not be better in the AT&T forum >>or TMobile forum
JJEgan said:
Would you not be better in the AT&T forum >>or TMobile forum
Click to expand...
Click to collapse
you may be correct, but I just wanted experienced dev's to talk to about this and If I post on at&t specific threads, I'll likely have to tell a bunch of noobs that NO i haven't tried it yet { about to } and that no this isn't yet a bootloader unlock.
I wanted to discuss this with seasoned Devs such as @jcase
Any thoughts?
anyone?
Have a look almost nil Dev action on this section since day one .
JJEgan said:
Have a look almost nil Dev action on this section since day one .
Click to expand...
Click to collapse
Well It's turned to a dead end, and I no longer believe it possible.
I can confirm flashing the modem.bin to modem partition resulted in soft-brick
so i'm scared to try flashing the boot aboot sbl etc.
I'm now looking for a way to possibly boot a modified second
boot.img through a boot hijack, to enable me to use something like EFIdroid to boot custom roms...