Anyone with a Tmobile SM-t357t that has gotten Marsh Mellow to load on their tablet? I have downloaded the 6 for the SM-t355 but cant seem to get it to flash. They are both basically the same tablet.
Anyone know why the sm-t355 will not flash on the sm-t357t? they are both LTE . I get a Failed (auth) if i flash the sm-t357t home tar the exact same way it does flash. Anyone got any ideas how to mod the odin file to make it work? or why it wont work?
Ok since no one else is trying to make this work. I have so far got the SM-355 odin on the SM-357t. At this point the tablet boots up just fine. The screen does not respond. So im not sure if its because i did not flash any of the bootloaders or modems or that I need another kernel. I did try to flash some of the Custom 355 350 MM kernels but could not get tablet boot after that. As far as i can see the data is working i see the 4g lte icon is on and it seems to be transferring data.
Related
So, before I begin, I'd like to point out that I'm an idiot. I don't know how or why, but I'm an idiot.
I've been running danv's ROM for the longest time without issues (galaxy s4 on Rogers) and then decided to update the ROM today. After making my titanium backups and everything like that, (haven't made a ROM backup in a while though - again, idiot) I decided it was time to flash the ROM.
Well, I went and did a full wipe, and then all of a sudden when my phone rebooted, it rebooted into download mode with the whole "could not do normal boot" in the top left corner.
I was able to get into my phone by doing volume up/home/power and then canceling when it said to install new OS or not. So I do have access to my phone, but anytime it restarts it goes into download mode, I can't even get into recovery mode to flash the ROM.
Any ideas what to do to be able to flash this ROM? I have a rom backup from March of this year, would that fix the issue and then just try to flash the new ROM again once I was able to get into recovery mode?
Any help anyone can provide me would be much appreciated. I'm currently downloading the stock firmware from sammobile to see if that would fix the issue since I can install that over odin.
Thanks in advance.
*Edit* So recovering from a ROM backup didn't work either. I've done some researching and I think trying to flash through odin is my only option unless I've missed something. I'm running firmware NE3, so does that mean I should get the stockfirm ware for my device (S4 Rogers NI2) or get the firmware for the same NE3 that I have on my phone (In this case it would be Puerto Rico firmware)?
If someone could let me know if this would work, I would very much appreciate it.
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
vexx32 said:
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
Click to expand...
Click to collapse
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
dirtydodge said:
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
Click to expand...
Click to collapse
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
vexx32 said:
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
Click to expand...
Click to collapse
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
dirtydodge said:
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
Click to expand...
Click to collapse
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
vexx32 said:
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
Click to expand...
Click to collapse
Yea it works. I know that one does. You'll get a message that says "unauthorized SIM card: or something like that. Just ignore it and use WiFi to setup the phone. Once you have it setup use package disabler or titanium to freeze "setup wizard" and that'll get rid of that notification. You'll have to manually setup your AT&T APN. After that your golden.
so heres the situation, a couple weeks ago my sammy a5 meet a horrible end and ive been without a phone. My buddy gave me his old s7 edge, its got cracked screen and has been sitting inn a drawer(hes rocking a pixel xl instead). so got it home charged it up turn it on and it got this blue sceen says there was a problem updating.
so longer story short got the stock 6.0.1 for bell 935w8 but i only run ubuntu, now while im able to flash smaller tars or img files flashing all stock at once wont work with either heimdall or Jodin3.
thought i could maybe flash twrp and go straight into custom roms i cant flash anything onto the device because of FAP lock in download mode.
Can anyone help me out? i know this would be easier with a windows comp but i dont have one.
can anyone help me
Hello I'm currently using a sprint note 4 and been having this message shown in download mode after trying to flash anything on odin. I've tried different versions of odin but they all fail. This started to happen after flashing QI5 bl/modem while on lineage OS. I may have done something wrong because after the phone finished booting, signal was always weak or would drop. This also happens on older builds of lineage and other aosp ROMs I tried so I know its a problem with my phone and not the rom. Nobody else is experiencing the same either. I've tried going back to the previous bl/modem and stock mm but they'll all fail. Flashing the same QI5 is the only one that passes on odin but signal will still be weak after it boots up. Calls and SMS work most of the time or once in a while but data never does or loads very slow unless connected to wifi. I think I really messed it up this time for the first time I hope there is a fix if anyone knows. Might not want to have to get a new phone yet. Ty
edit - found out about this https://forum.xda-developers.com/note-4-sprint/general/firmware-qi5-released-10-11-2017-t3686982
and the weak signal might be with my service i will check with that because it still happens after the stock flash. maybe it isnt modem related. thx to those who uploaded the flashable tar it doesnt fail in odin
Im using a Galaxy s7 edge exynos and I have been trying ALL day to return to stock firmware. (was aiming for 6.0, but when that didnt work I started trying 7.0 with slightly more success...) I was previously rooted via magisk using TWRP. I am not able to flash all 4 files at once via odin, (BL, AP, CP, CSC) I quickly get an error on both the device and odin (decive says binary 2 device something... Odin stops at either Param.bin or cm.bin depending on which CSC I use) the BL file seems to be the one that refuses to flash (from any of the 4 versions of odin i have and using different firmware versions that previously worked on the phone)
I am able to flash just the AP, CP, and CSC but when android loads up my mobile data doesnt work and many other things dont work correctly as well ...
I am so confused as to what I can even possibly do now. Im sitting here with a phone that wont correctly software update that I cant correctly root and has no mobile data. No full 4 files will correctly flash without odin error. TWRP gives me crap now too. I have wiped and formatted all the data many times hoping id missed something.
Send help
also
I try to manually update and it says "registering device" for a sec and then "Process failed" Like android 7.0 is running but not how it was before. I did update to newest update via the phone before i decided to try to revert to android 6.0 again because I was having issues connecting my pokemon go+
Hmmmm I still have problems with 5ghz and mobile data but i got magisk to install... luckily im not using this for phone purposes. this is the best i can do without help
What is yohr phone model ?
G935f
G935f
Currently running g935fd
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
riseofsand said:
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
Click to expand...
Click to collapse
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
I'd still like to try to get my 5ghz and cell signal (just in case something happens to my main phone) but I'm scared to soft brick my phone for the 1000th time in 2 days when I managed to get it semi working.
CactuarKing said:
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
Click to expand...
Click to collapse
Last time something like that happend to me, is because i was flashing the wrong stock rom (same model but wrong original carrier) sometimes it does matter, sometimes not
I was worried I might have messed it up for good as well luckily I'm not completely stuck but I still dont understand why I couldnt just 100% flash my OS via odin like I always do. Although I got cocky and started without following instructions up on the computer this time. Just my luck
double check mod #it can change with different roms my s5 tmobile g900t originally now its grown into g935f S7 edge