Related
So, I tried to upgrade my phone that was rooted and was stuck in a CWM bootloop, I was able to get out of the bootloop by installing the DFUSE rom that us for the d959, the problem is now I have my phone booted up but I need to return back to stock AT&T d950 preferably kitkat, but I cant figure out to do so, thanks for your help to get to where I am so far, just need a push one step further.
joecash said:
So, I tried to upgrade my phone that was rooted and was stuck in a CWM bootloop, I was able to get out of the bootloop by installing the DFUSE rom that us for the d959, the problem is now I have my phone booted up but I need to return back to stock AT&T d950 preferably kitkat, but I cant figure out to do so, thanks for your help to get to where I am so far, just need a push one step further.
Click to expand...
Click to collapse
NEVER update anything if you are rooted especially not when you have a custom recovery. At least not until you thoroughly read through the forum. I find it insane that people will just start flashing things when you could possibly have a $700 paper weight. The att model and the tmous model have different modems. Go here for a really good guide. http://forum.xda-developers.com/showthread.php?t=2753013
joecash said:
So, I tried to upgrade my phone that was rooted and was stuck in a CWM bootloop, I was able to get out of the bootloop by installing the DFUSE rom that us for the d959, the problem is now I have my phone booted up but I need to return back to stock AT&T d950 preferably kitkat, but I cant figure out to do so, thanks for your help to get to where I am so far, just need a push one step further.
Click to expand...
Click to collapse
You can't just go back to kitkat since there's no one put out a return to stock kitkat procedure. Your best option is to use the return to jelly bean stock flashtool procedure for at&t and just take the kitkat update again that's the only way.
Sent from my LG-LS995 using Tapatalk
yellowman82 said:
You can't just go back to kitkat since there's no one put out a return to stock kitkat procedure. Your best option is to use the return to jelly bean stock flashtool procedure for at&t and just take the kitkat update again that's the only way.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
i don't think he can because the flash tool will more than likely think its the tmobile variant now.
PattyNYC said:
i don't think he can because the flash tool will more than likely think its the tmobile variant now.
Click to expand...
Click to collapse
Well that sucks not sure what he could do then.
Sent from my LG-LS995 using Tapatalk
yellowman82 said:
Well that sucks not sure what he could do then.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
i think the link in the second post should help him. he should stil have adb
PattyNYC said:
NEVER update anything if you are rooted especially not when you have a custom recovery. At least not until you thoroughly read through the forum. I find it insane that people will just start flashing things when you could possibly have a $700 paper weight. The att model and the tmous model have different modems. Go here for a really good guide. http://forum.xda-developers.com/showthread.php?t=2753013
Click to expand...
Click to collapse
I am basically in the same situation as this OP was before his worked, but it isnt working for me I get the error that the model doesnt match if I use the D950 dll and tot, and i get an error that says cross upgrade if i use the D959 dll and the 950 tot
joecash said:
I am basically in the same situation as this OP was before his worked, but it isnt working for me I get the error that the model doesnt match if I use the D950 dll and tot, and i get an error that says cross upgrade if i use the D959 dll and the 950 tot
Click to expand...
Click to collapse
Post questions in that thread it would be beneficial for you as I don't know a lot about basebands
I'm about to move to Australia and wanted to unlock my Samsung S3 LTE, which is currently locked to EE. I've looked at doing it via the network, who charge about £20 and also on Ebay, who don't seem to support my phone. Is there a way of unlocking it?
The phone is running Android 4.3 and hasn't been rooted or customised in any way.
Pianoman91 said:
I'm about to move to Australia and wanted to unlock my Samsung S3 LTE, which is currently locked to EE. I've looked at doing it via the network, who charge about £20 and also on Ebay, who don't seem to support my phone. Is there a way of unlocking it?
The phone is running Android 4.3 and hasn't been rooted or customised in any way.
Click to expand...
Click to collapse
you might want to check this out --> http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866
MaHo_66 said:
you might want to check this out --> http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866
Click to expand...
Click to collapse
I'll give that a try- many thanks!
that guide is useless... you can't downgrade to 4.1.1 once you got 4.3
spiderman07 said:
that guide is useless... you can't downgrade to 4.1.1 once you got 4.3
Click to expand...
Click to collapse
It worked for me.
spiderman07 said:
that guide is useless... you can't downgrade to 4.1.1 once you got 4.3
Click to expand...
Click to collapse
nothing is useless till you have tried it mate and im glad it worked out for you pianoman :good:
spiderman07 said:
that guide is useless... you can't downgrade to 4.1.1 once you got 4.3
Click to expand...
Click to collapse
Stop saying crap. You can downgrade if you didn't install a stock 4.3.
Pianoman91 said:
I'm about to move to Australia and wanted to unlock my Samsung S3 LTE, which is currently locked to EE. I've looked at doing it via the network, who charge about £20 and also on Ebay, who don't seem to support my phone. Is there a way of unlocking it?
The phone is running Android 4.3 and hasn't been rooted or customised in any way.
Click to expand...
Click to collapse
Hi,Pianoman91,you can unlock your device method downgrade- flashing firmware 4.1.1 from this forum:http://www.htcmania.com/showthread.php?t=738977
You need previously root your device,install a custom recovery and then flash firmware 4.1.1. Then use the hidden menu.This must to work!Before you must to make all backups.
Once done,you can flash again 4.3 frmware.You have to be aware that this proces will change Knox status from 0X0 to 0X1. This method is tested and works.Make on your own risk.
Thanks a develloper fzeta !
Best regards!
Pianoman91 said:
It worked for me.
Click to expand...
Click to collapse
Have you been able to downgrade to 4.1.1 while having stock 4.3?
LucasBass said:
Have you been able to downgrade to 4.1.1 while having stock 4.3?
Click to expand...
Click to collapse
Need to explain that is not downgrade to Bootloader 4.3/KNOX/-this is impossible for the moment.This way we make downgrade to firmware 4.3-4.1.1.:good:
LucasBass said:
Have you been able to downgrade to 4.1.1 while having stock 4.3?
Click to expand...
Click to collapse
The method suggested here worked perfectly for me
MaHo_66 said:
you might want to check this out --> http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866
Click to expand...
Click to collapse
As mentioned, using this does trigger the Knox counter- but if that doesn't bother you then it's worth doing this method to unlock your phone. After I'd used Odin to go back to 4.1 and unlocked the networks I just reconnected the phone to Kies and it then updated the firmware back to 4.3. Tried a Vodafone Sim card in my phone today to make sure it was unlocked and it worked perfectly.
Pianoman91 said:
The method suggested here worked perfectly for me
As mentioned, using this does trigger the Knox counter- but if that doesn't bother you then it's worth doing this method to unlock your phone. After I'd used Odin to go back to 4.1 and unlocked the networks I just reconnected the phone to Kies and it then updated the firmware back to 4.3. Tried a Vodafone Sim card in my phone today to make sure it was unlocked and it worked perfectly.
Click to expand...
Click to collapse
We are talking about two different methods,Pianoman91.I think if you try flash oficial firmware from 4.3/official/ to 4.1.1 trough Odin you will not be able to do it.Downgrade to bootloader 4.3 it is impossible in this time. But if we apply the method I mentioned should work .You should flashing trough Custom recovery a firmware modified.
Best regards!
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
spydc said:
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
Click to expand...
Click to collapse
Did you ever get an answer to this?
NO, but....
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
gello924 said:
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
Click to expand...
Click to collapse
Wait, it has an unlocked bootloader on the rebranded G900A?
Vesnyx said:
Wait, it has an unlocked bootloader on the rebranded G900A?
Click to expand...
Click to collapse
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Sent from my Amazon KFGIWI using XDA Labs
AptLogic said:
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Click to expand...
Click to collapse
You could always try it. I don't know exactly how well it will work.
You would have to be rooted FIRST on the G900A in order for FlashFire to work. If i remember correctly anything already on LP can't be rooted or downgraded back to KK.
---------- Post added at 11:30 PM ---------- Previous post was at 11:12 PM ----------
Y'know what would be really nice???: Seeing that android updates are only good for 2yrs on a particular model after its initial released, and the given the fact that most carries plans are only 2yrs; wouldn't it be nice if (for sake of argument in THIS thread) AT&T would release a firmware for their phones, that would unlock the bootloader and possibly SIM unlock the phone as well. I mean after 2yrs the device is paid for and quite frankly no longer belongs to them. I hate the idea of being forced to either get a new device once my plan has expired or use MY phone with the carrier its branded under. Of course it probably has everything to with them making their money from those of us who can't do without having a new device every year.
So I can pull a copy of the G900AZ engineering firmware I found, but I doubt we'll be able to flash it. What is was thinking is that we use beaups CID changer to make our device into one similar to the cricket wireless one. Since it is essentially a dev edition of our phone.
You cant just flash a unlocked bootloader to a locked bootloader phone. A specific explout must be developed to defeat the bootloader. Simply shashing over it will never work.
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Vesnyx said:
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Click to expand...
Click to collapse
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
AptLogic said:
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
Click to expand...
Click to collapse
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
NavSad said:
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
Click to expand...
Click to collapse
Mine are S1, T1, R1, A2, P1. I'm on Lollipop 5.0 with with ability to downgrade to NCE.
Also @AptLogic, maybe try through stock recovery, just as a precautionary measure.
P l e a s e do not try this
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
AptLogic said:
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
Click to expand...
Click to collapse
Try using a debrick image.
NavSad said:
Try using a debrick image.
Click to expand...
Click to collapse
I can't get the phone to boot, not even into Download Mode
AptLogic said:
I can't get the phone to boot, not even into Download Mode
Click to expand...
Click to collapse
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
NavSad said:
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
Click to expand...
Click to collapse
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
AptLogic said:
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
Click to expand...
Click to collapse
I would try this method:
Grab a sdcard
Grab a debrick image here:https://www.androidfilehost.com/?fid=457095661767140194
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
NavSad said:
I would try this method:
Grab a sdcard
Grab a debrick image here:UPLOADING
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
Click to expand...
Click to collapse
Is the debrick image just the first 200MB of the phone's data?
The other day I bought a nexus 6 used and didn't know what carrier it was from.. Well I dug around in the settings and found out that it was Verizon. The phone worked fine with my T-Mobile sim just like it should but when I tried flashing 5.1.1 Verizon build lmy48i it just would not flash right... It would just bootloop and nexus root toolkit said everything failed to flash but the bootloader. But I tried again after taking the sim out and it worked first try. Everything is okay, but why does a sim make so much of a difference? Should I be flashing T-Mobile img's?
dude_itsdevon1 said:
The other day I bought a nexus 6 used and didn't know what carrier it was from.. Well I dug around in the settings and found out that it was Verizon. The phone worked fine with my T-Mobile sim just like it should but when I tried flashing 5.1.1 Verizon build lmy48i it just would not flash right... It would just bootloop and nexus root toolkit said everything failed to flash but the bootloader. But I tried again after taking the sim out and it worked first try. Everything is okay, but why does a sim make so much of a difference? Should I be flashing T-Mobile img's?
Click to expand...
Click to collapse
First, you shouldn't use toolkits unless you already know how to use fastboot.
Second, use fastboot and flash the latest T-Mobile factory image if you're using your device on T-Mobile.
Follow method #2 from here:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Evolution_Tech said:
First, you shouldn't use toolkits unless you already know how to use fastboot.
Second, use fastboot and flash the latest T-Mobile factory image if you're using your device on T-Mobile.
Follow method #2 from here:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks for the super quick reply, I am familiar with fasboot and doing it manually but I'm lazy that's all. It just makes it so simple. thanks for letting me know which image to use. I just had to set up the apn settings to get my data to work right. Will I get otas if I flash the T-Mobile factory image and use their service?
dude_itsdevon1 said:
Thanks for the super quick reply, I am familiar with fasboot and doing it manually but I'm lazy that's all. It just makes it so simple. thanks for letting me know which image to use. I just had to set up the apn settings to get my data to work right. Will I get otas if I flash the T-Mobile factory image and use their service?
Click to expand...
Click to collapse
As long as you're 100% stock and using a T-Mobile sim, you'll be able to get and install T-Mobile OTA's.
LMY48I is not a T-Mobile version. You want LYZ28E or LYZ28J.
Searching via cell isn't great for me at the moment. I've found a few threads with lollipop files to use in Odin. But I haven't read anything that says it's simple to flash them and downgrade properly from Marshmallow to Lollipop. Is there a tutorial/file thread already on here that I am missing via search? Is this something I can do without rooting?
Da hell is that chipmunk woman
Sammobile doesn't have the stock 5.1 firmware.. is that an omen against downgrading?
Most of the posts ive read are indicating Marshmallow is not able to be downgraded, bootloader locked.. looks like a dead end
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
johnkirchner said:
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
Click to expand...
Click to collapse
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
At the time of my post months ago, this was not possible. It is very possible now, I have also done it.
gooch1006 said:
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
Click to expand...
Click to collapse
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
johnkirchner said:
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
Click to expand...
Click to collapse
Thanks for the link, i had searched without luck on my own.
https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
following this guide for rolling back to LP, work for me downgrade from MM and getting root on LP.
Mine didn't... version DPH4, october 1, 2016 security patch, odin gave me an error something like level 4 > 3 and didn't start the reflash process. I was able to reflash the same 6.0.1 and its not the same as what was on there, so maybe the ota updates had a problem? I'm still locked out of downgrading.
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
kecel said:
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
Click to expand...
Click to collapse
i had that issue at one point, i just flashed the CSC and CP again and it worked.. Idk if it's that simple for you guys tho..
g900a downgrade from 6.0.1 to 5.1.1
djs2571 said:
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Click to expand...
Click to collapse
i also have the at&t model, but used some info in this post: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
i used odin to flash full OI5 firmware, minus the bootloader file. Only use the AP, CP, and CSC files. the bootloader is the same. and really, i had already flashed the PA2 build earlier that day i remember now. would probably do that first. flashing the PA2, i used all four files, BL, AP, CP, and CSC . they both flashed the first time, if they dont then try a different cable first. usually that is my issue.
so , i flashed from 6.0.1 down to 5.1.1 pa2, then down to oi5. still have no problems other than getting root..... im focusing on bootloader now, i have unlocked them on htc's before, but havent tried any other phone yet. the work continues tonight.