Related
In case some of you who have flashed to the euro firmware want to go back, the below is an early firmware for at&t and can be flashed via Odin.
This is not the most recent stock firmware, but it is something:
http://www.multiupload.com/J9Q8A95EF7
Pass: samfirmware.com
do not select repartition when flashing this.
clubtech said:
In case some of you who have flashed to the euro firmware want to go back, the below is an early firmware for at&t and can be flashed via Odin.
This is not the most recent stock firmware, but it is something:
http://www.multiupload.com/J9Q8A95EF7
Pass: samfirmware.com
do not select repartition when flashing this.
Click to expand...
Click to collapse
can you get sprint firmware
clubtech said:
In case some of you who have flashed to the euro firmware want to go back, the below is an early firmware for at&t and can be flashed via Odin.
This is not the most recent stock firmware, but it is something:
http://www.multiupload.com/J9Q8A95EF7
Pass: samfirmware.com
do not select repartition when flashing this.
Click to expand...
Click to collapse
No need of .pit file?
Is it just like putting it into "PDA" and flash?
clubtech said:
In case some of you who have flashed to the euro firmware want to go back, the below is an early firmware for at&t and can be flashed via Odin.
This is not the most recent stock firmware, but it is something:
http://www.multiupload.com/J9Q8A95EF7
Pass: samfirmware.com
do not select repartition when flashing this.
Click to expand...
Click to collapse
so if we flash this could we upgrade to the latest att firmware
wrong thread:
I took a rotobackup of my AT&T SGT prior to flashing it with the Russian+Euro roms. If anyone would like them I can post the files up somewhere.
agentdr8 said:
I took a rotobackup of my AT&T SGT prior to flashing it with the Russian+Euro roms. If anyone would like them I can post the files up somewhere.
Click to expand...
Click to collapse
I would like that as long as it was factory reset before the backup so it doesn't have any of your personal information.
caveman999 said:
I would like that as long as it was factory reset before the backup so it doesn't have any of your personal information.
Click to expand...
Click to collapse
It should be clean of any personal data; I had just rooted it via SuperOneClick and installed Busybox and then pulled the backup. I'll upload it to multiupload tomorrow and post the link.
EDIT: Looks like it does contain some stuff. If I ever have to restore it, I'll do a factory reset and pull a clean dump and post it. So for now, if anyone wants pieces of the original firmware, minus the data partition, let me know and I'll upload those pieces.
agentdr8 said:
It should be clean of any personal data; I had just rooted it via SuperOneClick and installed Busybox and then pulled the backup. I'll upload it to multiupload tomorrow and post the link.
EDIT: Looks like it does contain some stuff. If I ever have to restore it, I'll do a factory reset and pull a clean dump and post it. So for now, if anyone wants pieces of the original firmware, minus the data partition, let me know and I'll upload those pieces.
Click to expand...
Click to collapse
Did you ever get the rom? I would like to go back to ATT rom if I can. The one clubtech posted unfortunately did not work for me. I think it does need a pit file, but which one? I have no idea.
I repeat the rom posted here DID NOT work for me. Blank screen with the tab vibrating every 10 secs or so. I was fortunate enough to get it back into download mode to go back to jjk5.
Looking for a stock ATT rom thanks.
can we just ask AT&T to reflash our devices or do we need t send them to Samsung if we want original version again?
jtorral said:
can we just ask AT&T to reflash our devices or do we need t send them to Samsung if we want original version again?
Click to expand...
Click to collapse
I believe if you tell AT&T you've flashed it with anything other than an officially released firmware, they'll tell you to pound sand, and that your warranty is void.
heythorp said:
Did you ever get the rom? I would like to go back to ATT rom if I can. The one clubtech posted unfortunately did not work for me. I think it does need a pit file, but which one? I have no idea.
I repeat the rom posted here DID NOT work for me. Blank screen with the tab vibrating every 10 secs or so. I was fortunate enough to get it back into download mode to go back to jjk5.
Looking for a stock ATT rom thanks.
Click to expand...
Click to collapse
I do have the rotobackup that I pulled from my SGT prior to flashing to JJ4/JK5, but I didn't do a factory wipe before I pulled the files, and thus there is personal data in some of the files. I'd rather not distribute my Gmail login info, which I'm positive is stored in there since I accessed the Market.
You might be able to flash all of the files I have, minus the dbdata partition (maybe substitute the one from clubtech?) and maybe that would work? I'd defer to someone more knowledgeable though, like Roto. I'm not even sure the efs partition should be shared, as there's IMEI info in there.
Heres the stock AT&T firmware I put together from my Tabs original firmware. I'm going to flash this now to test it once more, In Odin, no pit file.
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/ATT_Stock.zip
rotohammer said:
Heres the stock AT&T firmware I put together from my Tabs original firmware. I'm going to flash this now to test it once more, In Odin, no pit file.
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/ATT_Stock.zip
Click to expand...
Click to collapse
The reason i.was.going to flash back was.to.get the media hub app.and upgrade it. Then i was going to put.it.on jma so i.could use the $50 credit. But i would like it anyways in case i need warranty help.
Thanks for checking.
rotohammer said:
Heres the stock AT&T firmware I put together from my Tabs original firmware. I'm going to flash this now to test it once more, In Odin, no pit file.
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/ATT_Stock.zip
Click to expand...
Click to collapse
As expected, it worked, BUT:
It boots up blank, no splash screen.
Recovery is also blank, making it hard to navigate lol
Other than that, it works fine. Its good enough for return purposes or to grab files off and then flash back to JME.
Hmm, my guess than is the other one worked too then.
Any idea on why this boots up blank? Hopefully someone will grab this rom before flashing.
Not sure how you navigate a blank screen. Will give it a shot.
Thanks again.
rotohammer said:
As expected, it worked, BUT:
It boots up blank, no splash screen.
Recovery is also blank, making it hard to navigate lol
Other than that, it works fine. Its good enough for return purposes or to grab files off and then flash back to JME.
Click to expand...
Click to collapse
Funny, I actually got a samsung splash screen, but nothing else! Nothing! Blank after that. Same as the one clubtech provided.
I can get back to d/l screen but thats it. Can't see or do anything else
I've had issues trying to go back to stock AT&T after a full JMA flash, I ended up using all the files from my rotobackup minus the zImage because of the signed bootloaders...
So you got it to work? Could you post the files you used. Thanks
I believe the one from rotohammer are actually from my stock backup. (He hosted them for me) You can double check by checking topics I've posted, one of them is a stock AT&T dump I did.
Basically my configuration right now is JMA pbl sbl and kernel and the rest is AT&T stock. Flashing back the zImage from my backup didn't work if I'm remembering correctly.
Sent from my SGH-I987 using XDA App
Hello all. I have posted this problem/question before but received no help. So im posting it again. I recently rooted my S3 and installed cyanogenmod and decided I like touchwiz so I decided to unroot it. So I installed triangle away to delete any traces of root and the process was completed nicely. Then I flashed a stock rom that I downloaded online. Then I did a stock factory reset. But it doesnt feel right. There are slight graphics glitches with opening some apps. Like opening facebook messanger will display white and black lines untill it loads up. I tried the whole reinstall thing and no help. There are other similar glitches. Can anyone help me? I want my s3 fully stock like it was straight from att.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dima470 said:
Then I flashed a stock rom that I downloaded online.
Click to expand...
Click to collapse
I would try another file download location (which you did not specify where you downloaded from). You might also try and redownload and ensure to do an MD5 check. Of course this means factory resetting again and ODIN.
If nothing else, download rooted ROM from Mr.Robinson's post and unroot it. This will keep your flash counter as is.
aybarrap1 said:
I would try another file download location (which you did not specify where you downloaded from). You might also try and redownload and ensure to do an MD5 check. Of course this means factory resetting again and ODIN.
If nothing else, download rooted ROM from Mr.Robinson's post and unroot it. This will keep your flash counter as is.
Click to expand...
Click to collapse
Thank You for your quick responce. I downloaded the rom from a video i found on YouTube.(doesn't seem reliable huh...) How do i do an MD5 check?
dima470 said:
Thank You for your quick responce. I downloaded the rom from a video i found on YouTube.(doesn't seem reliable huh...) How do i do an MD5 check?
Click to expand...
Click to collapse
Follow this thread for downloading stock roms: http://forum.xda-developers.com/showthread.php?t=1968625. After unzipping most should end with the file name .md5. ODIN will do the md5 check automatically for you. Just pay attention to the prompts.
If you find that this does not work, go here and download rooted rom to be flashed via ODIN. You can then remove root.
If the file is not ODIN flashable with an md5 at the end, look for a long string of digits and letters that should be right by the download. A good example to know what I am talking about is to take a look at the site for rooted stock roms. Notice the md5 under the Old image AT&T file download link. Download and extract this file and follow the directions.
aybarrap1 said:
Follow this thread for downloading stock roms: http://forum.xda-developers.com/showthread.php?t=1968625. After unzipping most should end with the file name .md5. ODIN will do the md5 check automatically for you. Just pay attention to the prompts.
If you find that this does not work, go here and download rooted rom to be flashed via ODIN. You can then remove root.
If the file is not ODIN flashable with an md5 at the end, look for a long string of digits and letters that should be right by the download. A good example to know what I am talking about is to take a look at the site for rooted stock roms. Notice the md5 under the Old image AT&T file download link. Download and extract this file and follow the directions.
Click to expand...
Click to collapse
I tried Mr. Robinson's rooted stock rom, and it has the exact same issue.... Is it all just in my head? Please do help. My S3 isn't perfect anymore and i'm really OCD about it. I regret ever rooting.
I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk
I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.
Samobile.com
info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A
0 Results found
You searched for "sm-t807a"
It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.
OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.
Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.
It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.
I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.
i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
also odin was used.
ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing
I'm new to making modifications on my phone and I need some help deodexing the ROM.
I've got a Note 4 from Sprint running Android 5.01. I've installed TWRP and made a backup. I've also downloaded the version of Xposed that I want to get installed. But when I tried to flash Xposed to the phone, I got a message that a deodexed ROM was required.
I know that Titanium Backup can be used to deodex apps but it doesn't work with the framework. Is there a tool or app that anyone can recommend to me for this? Or is there a deodexed version of Samsung's stock ROM that I can easily swap out with the existing ROM?
Any help would be much appreciated.
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Thank you and some additional questions
samep said:
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
jmalmberg said:
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
Click to expand...
Click to collapse
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
samep said:
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
jmalmberg said:
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
Click to expand...
Click to collapse
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
samep said:
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
jmalmberg said:
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
Click to expand...
Click to collapse
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
samep said:
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
jmalmberg said:
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
Click to expand...
Click to collapse
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
samep said:
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
jmalmberg said:
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
Click to expand...
Click to collapse
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
samep said:
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you! It worked.
jmalmberg said:
Thank you! It worked.
Click to expand...
Click to collapse
Now, hopefully you have ROM picked out and on extSdCard ready to flash.
I'd backup stock ROM to extSdCard in TWRP just in case.
Follow the OP on your ROM install. Enjoy!
Sent from my SM-N920P using Tapatalk