Related
Okay, here is the stock SBF file for all those that have been waiting and digging around for it.
Please be careful using this and I am in no way responsible if you break or cripple your phone.
Enjoy.
http://www.mediafire.com/?ecadm7dxhrchb7z
thanks~
here it comes!
tcaudill01 said:
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
A pity, but I understand. Thanks for posting it when you did though.
(I never had the chance to download it, but I'll thank you anyway.)
tcaudill01 said:
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
I've downloaded it...
Now I give you my "thank you". But.... Can You understand my "But"?
tcaudill01 said:
Okay, here is the stock SBF file for all those that have been waiting and digging around for it.
Please be careful using this and I am in no way responsible if you break or cripple your phone.
Enjoy.
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
aww :-(. 30 minutes of google and i find this thread two days too late? My phone is bricked and useless :-(. Please reconsider?
dcostalis said:
aww :-(. 30 minutes of google and i find this thread two days too late? My phone is bricked and useless :-(. Please reconsider?
Click to expand...
Click to collapse
I have to agree. My old man needs this desperately. If you won't post it, at least send the link to some via PM.
Again, thank you for uncovering this.
thanks to original uploader, I personally don't understand calling people names and pulling the file after 2 days...
For those still looking...
cdn.anonfiles.com/1333515773933.rar
Thanks for the sbf!
This is great news, thanks a ton to whom managed to share this with the community.
working or not working
do u try it? information is not clearly.
works, but not recommend
cutdaubac said:
do u try it? information is not clearly.
Click to expand...
Click to collapse
it works, but not recommend.
motorola has released the update.zip for 4.1.15, and after the update, the final sha1sum of every file doesn't equal to the sha1sum in the sbf.
take care of it...
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
i mean, after update to 4.1.110 from 4.1.15, the sha1sum of the system dont equal to the sha1sum of the files in the sbf. however, i didn't check it, and i flashed the sbf.
now, i dont think there are any chance for this sbf to upgrade to the coming gingerbread. as the version are 4.1.100, but the sha1sum are totally different.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
for example,
the sha1sum of /system/app/AccountAndSyncSettings.apk:
4.1.15: d8c4844aaea053262817f7e3e48a2c70cab9c1b9
4.1.110: b8be65cc4224f5fd1bcb27404a94c463f57f8041
4.1.110sbf: b4957ae44524df9c8bd61d1f6842d47175092055
so i dont think there is anyone can upgrade from 4.1.110sbf to the coming gingerbread.
of course, the apk content is same.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
i think, i consider too much...
i wish the coming gingerbread use a total update, not patch..
if there are patch, then it will check the sha1sum of the origin system.
and if it just replace the whole system, then everything should be ok.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
thank so much for the file...!! im sure this would have saved quite a lot of people!
The Cell Phone Biz is corrupt to the core thats why we have to,,, customize..
...
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.[/QUOTE]
I like the phones you mention...
Galaxy Prevail, Marquis XRPT... I know I am well on my way to becoming a fanatic about this...
And I am just saving up to buy the Galaxy Note from Korea for like $250 (unlocked)...
But can you clue me in on how to save this "original file onto my mac"..
I already downloaded this MDM installer for my mac...
I am dreading all this and have no clue if I can take the ..
Original Sprint Motorolla ,,, that someone in China put a cardboard boost mobile sleeve around and now... Not really knowing who's OS is on this phone... and now try to unlock it (from ..?? sprint or boost) to.... Virgin Mobile (and a special low end Virgin Mobile called Assurance Wireless which everyone says is JUST FOR PAYLO (read lousy phones without features).... so teach me how to ave whatever OS is there in case this does not work at least I can activate it for Boost... and i will share my files... if you need em..
Thanks
A still somewhat sane Newbie who has been tormented too many times but the "in humane" and uncaring cell phone business!
I want to restore my Sprint XPRT to stock Froyo using this SBF and then update to Gingerbread.
liudongmiao mentioned some checksums not matching up for files between this SBF and stock files originally on the phone. Now that GB has been out for a while, anybody run into any problems updating as a result of that or have your updates went smoothly?
My phone isn't bricked, but rongsang made the excellent suggestion in the main XPRT thread on here that I should use the SBF and then apply the Gingerbread update as the easiest way to get to GB. My XPRT currently is running Froyo, rooted, and works okay (other than missing a few Sprint bloatware apks that the GB update seems to want there).
Update: After finding positive reports on another forum I went ahead and applied the SBF followed by the OTA Gingerbread update and all appears to have succeeded.
will this work with thr boost version of XPRT ?
I clicked the download link, and the file was accessible and downloadable. I don't know if this means that the OP was having second thoughts, but thank you very much to the OP for the file!
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
@beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This tool is based off the research of @ryanbg . This makes the process all the simpler for developers to understand/port functionality!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of, though, it still could work, I need a tester, PM me, or Telegram me @npjohnson), and many, many other devices form a variety of manufacturers..
How does this apply to you?
The Note 4 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can you help this progress?
You can't.
Currently, the CID writes 'successfully', and persists across reboots, but one of the registers isn't fully flushed. I am working on a module that will flush the register and allow for the Developer Edition Aboot to be flashed via ODIN.
Now, you may ask "How could we load modules, I thought that was impossible?", the short answer is, it is. At least, without what we found (or, rather, stumbled across).
We have the device kicking into Developer Edition using the CID write, and a hardware modification, which we stumbled across (demo: here, credits to @PaulPizz for spending late nights testing the various things I would throw at him, and having the balls to do some dangerous stuff that I personally believed would permanently brick his device). This method is volatile, dangerous, and quite honestly, shouldn't work. When I am confidently able to prove how it works, I will release details on my blog: here. Until then (shouldn't be more than a month, but as always, this is a free time project, and could be put on hold for real life, as I am busy with Cyber Security competitions).
What will most likely be the course of action once I release:
- Change CID to a provided Developer Edition CID
- Use hardware mod to flash/boot the custom kernel I have build to enable module loading (or maybe I'll build the function into the kernel itself, haven't decided yet)
- Either load the module, or call the function (if the latter, I'll write a binary to do so)
- Revert the hardware mod
- Flash Developer Edition Aboot via ODIN
This should be bootloader version agnostic, but, as always, beware updates, and, I'd stay away from any incoming MM updates on all locked carrier variants if you want to retain the ability to use this. If Samsung can update the eMMC firmware using those vendor commands, they can sure as heck change them the same way. Then the ability to do this goes away entirely.
You may be asking, "Can I donate to progress?"
Well. Sort of. Beaups asked that all donations go to the Make a Wish Foundation, or @ryanbg (as he is getting hitched , may you forever 'make cooking' Ryan! Haha.).
If you'd like to donate to me, know that it is not for the CID write, but instead, the work and research put into getting this all worked out for this device. I will also be dividing any donations sent to me with my tester, as he has spent a fair bit of time on this, as have I.
@npjohnson I have two devices s4 and note 4 both from Verizon, I'm in Brazil right now so I don't know if it makes a difference but I'm able to use temporary root in my note 4 so if you want any help give me a shot, I'm not a developer but engineer so any you need from me to get this rooted count me
OMG Could it be?
npjohnson said:
All,
Due to the recent accidental leak of Samsung eMMC vendor commands allowing write to protected eMMC areas, we are now able to write CID values on production devices.
Beaups has written an awesome tool called 'SamsungCID' (found here: https://github.com/beaups/SamsungCID). This makes the process all teh simpler!
I have built this tool from his source, and used it on a multitude of devices that use a Samsung eMMC. It works without flaw on the Moto G (Second Generation), Galaxy S5 (VZW/ATT, though, ATT doesn't have a Developer Edition that I am aware of), and many, many others.
How does this apply to you?
The Note 4 uses a Samsung eMMC, and has a Developer Edition. This means that it is vulnerable to this exploit.
How can I help this progress?
I need a few thing to make this work:
- A few testers with Production devices, and root (temp-root should work fine) -- I will contact these people individually, do not ask here to test.
- One person with a Developer Edition that has root (need an aboot dump, and them to run one command).
If any of you know of someone with a Developer Edition, please get them in contact with me. I can be reached on Hangouts, or on Telegram (@npjohnson).
PLEASE do not post your CID publicly.
Click to expand...
Click to collapse
So you are saying this might be a path to perm root?
kerfex said:
So you are saying this might be a path to perm root?
Click to expand...
Click to collapse
Not only root but unlock bootloader please encourage anyone to help
The android gods have sent us a miracle
---------- Post added at 12:30 PM ---------- Previous post was at 12:29 PM ----------
I have a locked Verizon note 4 I'm willing to help
@npjohnson Im willing to help. I have been around the block a few times testing for other developers. I am on 5.1.1 and can hold temp root with Kingroot for about 15 minutes.
Edit: I can role back to 5.0 if needed.
@npjohnson
I believe these are some note 4 developer files. Hope this helps
https://www.androidfilehost.com/?w=files&flid=28873
@Venom0642 - Awhile back I think you said you had a developer addition note 4. Do you still have one? Can you help?
howellcp said:
@Venom0642 - Awhile back I think you said you had a developer addition note 4. Do you still have one? Can you help?
Click to expand...
Click to collapse
Sorry mate look at my Sig i been on Note 5 since it came out, so i don't have any Note 4.
Running On Samsung Galaxy Note 5 N920A Wicked Deadly Venom Theme
also willing,
have a retail Verizon,
on LP but can roll back to kk
I have a dev ed Note Edge BUT I bought it used and the previous owner blew retail firmware into it, so aboot is destroyed. Strange thing, though, I'm able to get perm root with the latest kingroot on 5.1.1.
If that's useful to you, I'm down if you're down!
h00rj said:
I have a dev ed Note Edge BUT I bought it used and the previous owner blew retail firmware into it, so aboot is destroyed. Strange thing, though, I'm able to get perm root with the latest kingroot on 5.1.1.
If that's useful to you, I'm down if you're down!
Click to expand...
Click to collapse
If you have a backup of that old aboot, then yes. Feel free to jump in on the thread I added in the Note Edge XDA forum.
kerfex said:
So you are saying this might be a path to perm root?
Click to expand...
Click to collapse
Bootloader Unlock, so yeah, permanent root, though, I don't know if write protection will still be active, but we can hope.
PaulPizz said:
@npjohnson
I believe these are some note 4 developer files. Hope this helps
https://www.androidfilehost.com/?w=files&flid=28873
Click to expand...
Click to collapse
It would... if you knew whose aboot that was, and they were around to dump their CID. Track them down, then we'll talk.
@morgej, please see original post.
Just out of curiosity, correct me if this is lame thinking or not worth trying but would it be possible to change the cid to turn the device into lets say another variant in order to utilize something like CROM.apk or to odin another variants tar files to oem unlock a device?
elliwigy said:
Just out of curiosity, correct me if this is lame thinking or not worth trying but would it be possible to change the cid to turn the device into lets say another variant in order to utilize something like CROM.apk or to odin another variants tar files to oem unlock a device?
Click to expand...
Click to collapse
You could, but the device 99% wouldn't boot.
Plus, you do realize developer editions are unlocked? Why would you want to flash to another variant to oem unlock? Literally the same thing.
Rom-Addict said:
also willing,
have a retail Verizon,
on LP but can roll back to kk
Click to expand...
Click to collapse
Please Hangouts message me if you have adb set up, and can use it.
Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.
Zues532 said:
Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.
Click to expand...
Click to collapse
1. I believe this will work. I tired to help but suck at adb now apparently.
2. No need to post if you don't believe. Just ignore
Zues532 said:
Alright guys, a new exploit is great, but let's not get our hopes up just yet. How many times have we had our collective hearts broken over situations almost exactly like this one?
I really really hope this turns into something useful, but for now, I'm assuming it's just a flash in the pan.
Click to expand...
Click to collapse
Well. Why don't you read the paper?
All devices that:
1. Use a Samsung eMMC (allows CID write)
&
2. A Developer Edition (allows you to supply a developer CID, and use their aboot)
Are vulnerable.
Question it if you will, but I am packaging things up as I write.
have adb setup but it's been awhile
I ripped these files directly from Kies3. I supply these for anyone that needs or wants the virgin files for development or whatever. You assume all risk by using these files I offer no guarantee.
Firmware split into separate files.
AP Main ROM Platform
BL Bootloader
CP Modem
CSC Region / Carrier Data
https://mega.nz/#!wURj0QgD!KeX6dOzL1I8A18XwYvB2VuFONJlEoLbLb8iRYRV3Alk
The password to the archive is XDA601
and the MD5 Checksum is : 1f86e82f97cfa209744cb4e164ee043b
Nirrik said:
I ripped these files directly from Kies3. I supply these for anyone that needs or wants the virgin files for development or whatever. You assume all risk by using these files I offer no guarantee.
https://mega.nz/#!wURj0QgD!KeX6dOzL1I8A18XwYvB2VuFONJlEoLbLb8iRYRV3Alk
The password to the archive is XDA601
and the MD5 Checksum is : 1f86e82f97cfa209744cb4e164ee043b
Click to expand...
Click to collapse
lol this has been posted like 3 times now
Thats weird because I looked for official TMO SM-N910T files and couldnt find them. They were all modified or developer preview versions not release versions. Also mine includes the AP, BL, CP, and CSC flashes.
So it's the sm-910t not the t3 version.
and you're right. The other post is for the sprint version. I'm getting a fail! (Auth) when I try to flash it
Nirrik said:
Thats weird because I looked for official TMO SM-N910T files and couldnt find them. They were all modified or developer preview versions not release versions. Also mine includes the AP, BL, CP, and CSC flashes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
is that what it is you were afraid of? I was stealing your thunder? Either way I was just trying to help out, there are multiple versions out all slightly different and theres nothing wrong with mirrors if in fact you have the same 4 flashes in your zip.
Nirrik said:
is that what it is you were afraid of? I was stealing your thunder? Either way I was just trying to help out, there are multiple versions out all slightly different and theres nothing wrong with mirrors if in fact you have the same 4 flashes in your zip.
Click to expand...
Click to collapse
Thunder? Hardly, I could care less. This is not a popularity contest. Hence why my donate link doesn't even go to me.
I too was simply trying to also help out. There is no need for multiple posts of the exact same thing. (you were not the only one)
Some of the other posts were actually the wrong file and were bricking devices. I simply wanted to make sure people had the 100% for sure one.
Also AFH mirrors the file 6 times and is much faster then MEGA.
In addition typically/historically speaking stock firmware are usually posted in the Development section. (not a rule, I dont think)
4 flashes? What do you mean? There is one tar file in my zip.
---------- Post added at 01:36 AM ---------- Previous post was at 01:17 AM ----------
Actually to add; Your post is very useful I would just re-word the title. (and if possible request that it is moved to dev)
Your title "Tmobile 6.0.1 ODIN files" is not very detailed and a poor choice of words for what you posted.
Including the model of the phone and the build version of the firmware you posted would be more helpful. (there are two different models of the Note 4 for T-Mobile)
Because you got the files from Kies it contains the firmware split into separate files.
AP - Main ROM Platform
BL - Bootloader
CP - Modem
CSC - Region / Carrier Data
These things are very useful for some "power users".
However to many users this can be very confusing to flash with Odin and would need further explanation.
The Firmware I posted is what every one is accustomed to. (a tar you flash via Odin in PDA/AP)
---------- Post added at 02:13 AM ---------- Previous post was at 01:36 AM ----------
Then again it looks like this guy posted all of those files well before any of us. Dunno what to say at this point.
http://forum.xda-developers.com/note-4-tmobile/development/epe3-stock-t-mobile-marshmallow-t3406826
Sammobile posted the firmware yesterday.
Sent from my SM-N910T using XDA-Developers mobile app
Ok does that help out. I changed the title hope that helps, Im still new to posting files like this but Ill get the hang of it eventually. As for requesting the move I dont know how to do that.
As for sammobile, yes they almost always have it immediately but unless you have a paid subscription you'll be downloading for half the day, which is why I uploaded to a different place.
I rather run from a jaguar then go to that site.
@rbiter said:
Sammobile posted the firmware yesterday.
Sent from my SM-N910T using XDA-Developers mobile app
Click to expand...
Click to collapse
The site makes you jump through so many hoops and like I said if you dont pay for a subscription the downloads are a few hours.
Nirrik said:
The site makes you jump through so many hoops and like I said if you dont pay for a subscription the downloads are a few hours.
Click to expand...
Click to collapse
smokeingit said:
I rather run from a jaguar then go to that site.
Click to expand...
Click to collapse
Nirrik said:
Ok does that help out. I changed the title hope that helps, Im still new to posting files like this but Ill get the hang of it eventually. As for requesting the move I dont know how to do that.
As for sammobile, yes they almost always have it immediately but unless you have a paid subscription you'll be downloading for half the day, which is why I uploaded to a different place.
Click to expand...
Click to collapse
interesting. sammobile is slow but downloads usually take two hours top on good or regular days. yes, some days have had to start over a couple times so took all day because so slow and congested. was just putting it out there. sammobile isn't my first choice but it reliable and occasionally the firmware makes it there faster than here.
Thanks for the link. This is my first time seeing this link and I have google searched a bunch of them. So I googled specific to this model and I came to this link. Usually when I see xda I automatically check here first because I have had a lot of success in doing so thanks to users like yourself and many others. Keep up the good work ladies and gents.
N910t "virgin"
please, does it work with all operators ?
THANK YOU SOOOO MUCH!!!! I wanted to try out RR N on my Note 4 SM-N910T. I really love RR however during some phone calls, the caller couldn't hear me. A few other glitches. I tried all day today to switch back to stock and all the fireware I tried from SDA links failed in Odin. What a waste of a day!
Your link, even though it was mentioned was double posted, was the only one that came up in Google, and saved my phone! Thanks so much!!!!!!!!!!
Now I am just going to keep it rooted, Keep stock Rom, and use my paid version of Nova. I did like RR though. But I would rather a working phone best.
Nirrik said:
I ripped these files directly from Kies3. I supply these for anyone that needs or wants the virgin files for development or whatever. You assume all risk by using these files I offer no guarantee.
Firmware split into separate files.
AP Main ROM Platform
BL Bootloader
CP Modem
CSC Region / Carrier Data
https://mega.nz/#!wURj0QgD!KeX6dOzL1I8A18XwYvB2VuFONJlEoLbLb8iRYRV3Alk
The password to the archive is XDA601
and the MD5 Checksum is : 1f86e82f97cfa209744cb4e164ee043b
Click to expand...
Click to collapse
Thanks for this! Great to have! Appreciate it!
Me, Honestly Annoying, and 4 others are working getting root, and fastboot working on our device. As far as where we are at (as of this post), fastboot pulls up on the phone and the computer recognizes it, most fastboot commands work, but the ones involving unlocking the bootloader don't work. On every file we have tried up to this point, except for the userdebug I posted a bit ago we get file "signature verification failed", but that is due to a locked bootloader. we have been working nonstop to get the fastboot to function in our device so we can unlock our bootloader. If, and I mean if, this works right, it will easily be applied to quite a few devices. so, in short, we are working on it. We will release the files we have once we are SURE that they work like they are supposed to.
Just don't ask how long it's gonna take to be completed, cuz we honestly don't know. But we are working almost night and day to get this done
For real... Been day and night on this one
If anyone has any ACTUAL questions (ie. not an ETA), please ask them. If you would like to offer ACTUAL help (ie. not "I will test your root method" because there is none to test) please tell us here! Also, @autoprime you have been strangely quiet about all of this, can you offer some insight about where we are? It would be much appreciated
Let me know if there's any help I can render!
solitarywarrior1 said:
Let me know if there's any help I can render!
Click to expand...
Click to collapse
what's the exact model number of your device (I.E. LGLS992)?
schizoidd said:
what's the exact model number of your device (I.E. LGLS992)?
Click to expand...
Click to collapse
LGLS992
solitarywarrior1 said:
LGLS992
Click to expand...
Click to collapse
check your inbox for a skype join link.
UPDATE: modified the aboot and it booted... stay tuned for more
Can I buy yall a pizza or beer or something while you work?
INCREDIBLE WORK YOU GUYS
Sent from my LGLS992 using XDA-Developers mobile app
Honestly Annoying said:
UPDATE: modified the aboot and it booted... stay tuned for more
Click to expand...
Click to collapse
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
fiddy619 said:
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
Click to expand...
Click to collapse
We don't think so, though we will have to do some testing on that...
And schizoid cross edited the T-Mobile aboot with our aboot to see if the fastboot commands will work, we're still testing that
---------- Post added at 05:10 PM ---------- Previous post was at 04:42 PM ----------
Calling @thecubed @IllegalArgument @autoprime... we could really use your guys help on this. We're actually making some progress with this device and would love for you to be involved
Here to help
Also willing to help the cause via pizza ? or anything for that matter
fiddy619 said:
Nice!!! Are you sure it actually didn't just rewrite aboot during boot to the stock aboot? And what was modified on your aboot?
Click to expand...
Click to collapse
We checked, it definitely isn't writing the aboot back when it boots. Still won't recognize unlock commands though...
you haven't explained what's being done so there's not much to comment on.
good luck to you guys tho. :good:
autoprime said:
you haven't explained what's being done so there's not much to comment on.
good luck to you guys tho. :good:
Click to expand...
Click to collapse
Can I add you to our Skype chat? I think it would be easier to explain that way
Honestly Annoying said:
Can I add you to our Skype chat? I think it would be easier to explain that way
Click to expand...
Click to collapse
sorry, never have and never will use Skype.
I'll chat on any public XDA thread or #LG-IRC on Freenode IRC.
How are you getting fasboot, wiping recovery or laf? flashed another devices aboot?
you mention changing aboot... you have directly edited the stock Sprint LS992 aboot.img? Or flashed another devices aboot?
autoprime said:
sorry, never have and never will use Skype.
I'll chat on any public XDA thread or #LG-IRC on Freenode IRC.
How are you getting fasboot, wiping recovery or laf? flashed another devices aboot?
you mention changing aboot... you have directly edited the stock Sprint LS992 aboot.img? Or flashed another devices aboot?
Click to expand...
Click to collapse
No worries... this is OK
A while back Tungkick made me a TOT that booted into fastboot. Don't know what she did to edit it, but it works. However it did not recognize ANY fastboot commands, but once I enabled userdebug by editing the build.prop it started to recognize some of them. As far as aboot goes, that's all @schizoidd and I'll let him explain
ok so what has been edited and done. i looked at our aboot and compared it to tmobile's and noticed a few things were missing like the "welcome to fastboot" and a few other things. and on ours, there was some random characters that were in ours but not in t-mobile's nor on the verizon one, so on the stock edited, i just deleted that code. and like Honestly Annoying said, it booted without an issue. i also created another file with tmobile and sprint's aboot merged together and it also booted.
the things done on the merged aboot, sprint encryption, keysand a few other things, tmobile everything else. i have the files but will not upload to here until i know what's all going on
@autoprime ^^^ last post explains what we're doing
So, I'm at a total and complete loss as to what to do. I have spent hours upon hours googling, and searching xda and trying step after step after guide after guide and I canNOT fix my S5! I've tried recovery, I've tried Odin and there has got to be something I'm missing. When I plug up the phone into my laptop, it sort of recognizes it, in the sense that it makes the notification noise of it being recognized, as with any external device. Odin picks it up as well. The issue is when trying to boot up the phone, it's stuck on the Samsung Galaxy S5 custom, android etc screen. it will not go past this. i'm almost in tears right now, and just want to get the phone working again. Is there anyone out there that can help???
Tiny update.
So I tried another method, and still having issues. Only difference is, I get past the powered by android screen, but then when getting to the Samsung with the color and oval it freezes and shuts down. One step forward, 2 steps back.
which G900 model do you have? like is it a G900F? Mine is a G900P
youdoofus said:
which G900 model do you have? like is it a G900F? Mine is a G900P
Click to expand...
Click to collapse
it is the 900a (at&t). after spending hours upon hours. i finally managed to do something and get it back to working again. the band and the firm ware match, and i managed to get rid of the unauthorized actions detected message.
good to hear!! (or see, rather LoL) usually a flash in Odin with the correct tarball fixes most issues with S5's
youdoofus said:
good to hear!! (or see, rather LoL) usually a flash in Odin with the correct tarball fixes most issues with S5's
Click to expand...
Click to collapse
I'm just sad that I don't know which one or who it was that posted it so I could give my thanks, but I just tried so so so many I don't even know lol.
ahervey85 said:
I'm just sad that I don't know which one or who it was that posted it so I could give my thanks, but I just tried so so so many I don't even know lol.
Click to expand...
Click to collapse
what do you mean? the posts should still be wherever you found it. And giving thanks to the folks who helped out is one of the things that makes this forum so great. this place is so selfless in the time, energy and knowledge shared by its users!
youdoofus said:
what do you mean? the posts should still be wherever you found it. And giving thanks to the folks who helped out is one of the things that makes this forum so great. this place is so selfless in the time, energy and knowledge shared by its users!
Click to expand...
Click to collapse
well, let's just say i have a folder of 26 links, majority from here on trying to find a solution on how to root and consequently unbrick my phone when I messed it up. that's probably not even all of them. I only posted on one asking a question, but it was about upgrading the firmware (still waiting on a reply on that, lol). so I have no clue which post it was that was finally successful in restoring my phone.
ahervey85 said:
well, let's just say i have a folder of 26 links, majority from here on trying to find a solution on how to root and consequently unbrick my phone when I messed it up. that's probably not even all of them. I only posted on one asking a question, but it was about upgrading the firmware (still waiting on a reply on that, lol). so I have no clue which post it was that was finally successful in restoring my phone.
Click to expand...
Click to collapse
ahhhh, the clusterf--k of saved links, gotcha. whats your question about upgrading firmware?
youdoofus said:
ahhhh, the clusterf--k of saved links, gotcha. whats your question about upgrading firmware?
Click to expand...
Click to collapse
This is my phone. Just wondering if I can upgrade it following this https://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016
Or not.
ahervey85 said:
This is my phone. Just wondering if I can upgrade it following this https://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016
Or not.
Click to expand...
Click to collapse
oh holy [email protected]!!! according to samsung, no :/
https://www.sammobile.com/firmwares/database/SM-G900A/
thats the only firmware release on their database... thats so weird tho, i have the G900P and it has a dozen or so firmware releases