Related
Here it is. Got my buddies c6606 us T-Mobile. Rooted fine, recovery went fine, but rom flash boot loops. And the best part is I cant get into recovery. So im stuck with fastboot, which gives me the same errors everytime, or flashmode with flashtool which I can put 100 fw's in the firmware folder and only a.1.253 shows up. Really need a.2.66 or 166 but I download them , place them in firmware folder with others and they're not there. My S3 is a dream compared to this. Takes me back to my HTC days! Anyway, I know its something small, its on .253 with some random rom asking for .66 or .67. Please, I'll pay. This is tying up my J-Tag repairs and other devices. Please, someone. I'll try whatever.
P.S. locked bootloader, apparently not unlockable.
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
jtford said:
jtford said:
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
Thanks. I was suprised with the errors using SUS. The device has a lot more potential to be exploited I think.
Click to expand...
Click to collapse
Sorry i got a message to you too late.
one thing: if you flashed over a different firmware, like for a 6603 or 6602 the sony software often says there is no update for your device because it sees it as a different phone.
The firmwares that you are placing in the /firmware folder are. Ftf files, and around 700mb? You can find firmware for download that comes in a different format, but flashtool wont see them.
Got this OTA after doing an ODIN of EPF1 to my phone. Baseband is updated to match, unsure about bootloader but I doubt it. If someone wants a ROM dump and is willing to tell me how....
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
elroy253 said:
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
Click to expand...
Click to collapse
I didn't. I haven't tried downgrading but I flashed recovery after it updated. The one thing I have noticed is that wanam xposed/firefds kit has some functions that don't work or change anything...
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
EncryptedCurse said:
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
Click to expand...
Click to collapse
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Maqical said:
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Click to expand...
Click to collapse
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
I guess until further notice using Smart Switch as a lazy way to recover from my own stupidity is out
EncryptedCurse said:
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...l/how-to-flash-marshmallow-update-sm-t3362983
This guide will help you with all of it, just change the "the rom" part to whatever 6.0 rom you decide you want to use instead.
I'm downloading the complete TAR image from Sammobile, but due to finances I don't have the means to pay for the full speed..
So I'm downloading at the slow method.. If someone else has not uploaded the image, I will upload it by late tonite..
I'm still having issues with the damn Upload it gives me last second errors when I step away to do another task..
I'm making my final attempt to upload it onto my Android File Host... It should be up by morning if it uploads correctly.. Just Look For Zaphodspeaks in Android File Host if I haven't posted it yet..
I have many tasks to do this week ends.. Mainly upkeep the the old house and updating some of the old wiring while its getting cooler..
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Got my phone rooted, custom rom, and kernel that I was using before, no problem.
Last night (9/27) I got a firmware update for my factory USA unlocked 920T. Sammobile shows it was released on 9/26. It was a 50MB file that updated the Android secruity patch date to Sept. 1. No other changes. I noticed the Samsung Smart Manager app/widget shows I'm using 5% less memory now. I don't know if it's better RAM management or Samsung modified the app/widget to show different figures LOL. I suspect the t-mobile 920T will get the update soon.
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
Thanks!!
RFrancis said:
Thanks!!
Click to expand...
Click to collapse
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
JustZaphod said:
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
Click to expand...
Click to collapse
Only a month? Record time there...
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
thanks
Hortisimo said:
thanks
Click to expand...
Click to collapse
Thank me by hitting the Thanks Thumbs up!
JustZaphod said:
Thank me by hitting the Thanks Thumbs up!
Click to expand...
Click to collapse
already did
Was wondering if a kind person could deodex this new update? for some reason i cannot install ubuntu on my pc to get it done right.Thanks
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave
Hi, I'm living in Costa Rica, I have a friend that was coming from Germany and he offered to bring something from there (phones are expensive here). My previous Z1 compact was almost dead (almost half screen without touch) so I bought a second hand XZ1 (I'm not a big fan of big screen phones) thru ebay kleinanzeigen. The phone got to my friend, he tried it and everything worked fine. When he brought it to me, I realized there was a demo mode activated on the phone. Tried deactivating it from system ('lock screen and security' tab is locked), *#*#sellmore#*#* ('Device is for store use only, Retail mode cannot be activated') and firmware reinstall thru sony companion but no luck. My friend it's going to be traveling back in over 6 months to Germany :crying: . Is there a way to remove this demo mode since returning it it's not an option? Thanks for your time!
craspo said:
Hi, I'm living in Costa Rica, I have a friend that was coming from Germany and he offered to bring something from there (phones are expensive here). My previous Z1 compact was almost dead (almost half screen without touch) so I bought a second hand XZ1 (I'm not a big fan of big screen phones) thru ebay kleinanzeigen. The phone got to my friend, he tried it and everything worked fine. When he brought it to me, I realized there was a demo mode activated on the phone. Tried deactivating it from system ('lock screen and security' tab is locked), *#*#sellmore#*#* ('Device is for store use only, Retail mode cannot be activated') and firmware reinstall thru sony companion but no luck. My friend it's going to be traveling back in over 6 months to Germany :crying: . Is there a way to remove this demo mode since returning it it's not an option? Thanks for your time!
Click to expand...
Click to collapse
Use the flashtool or newflasher to flash a different rom, if it's demo FW Sony companion will just keep reflashing it.
SXUsr said:
Use the flashtool or newflasher to flash a different rom, if it's demo FW Sony companion will just keep reflashing it.
Click to expand...
Click to collapse
Thank you very much for your reply! For using this tools, do I have to root or unlock bootloader or both?
craspo said:
Thank you very much for your reply! For using this tools, do I have to root or unlock bootloader or both?
Click to expand...
Click to collapse
Neither, just flash, but remove the persist file before flashing to keep the Android attest key in tact.
SXUsr said:
Neither, just flash, but remove the persist file before flashing to keep the Android attest key in tact.
Click to expand...
Click to collapse
Thanks again for your response! And sorry to break you ba**s again. I've dowloaded the last firmware from Xperfirm (47.2.A.11.228). I had Android 8 and this is 9. Is it worthy to upgrade? or I might encounter problems later on if I want for example to root or unlock boot loader? (I don't care much for customization I just use Titanium Backup for freezing or deleting bloatware)
And last question: I been reading about getting the persist file backed up and I just found this thread for motorola G5 would this still work? If not, would you mind guiding me in the right direction?
Thank you very much for your time again!
craspo said:
Thanks again for your response! And sorry to break you ba**s again. I've dowloaded the last firmware from Xperfirm (47.2.A.11.228). I had Android 8 and this is 9. Is it worthy to upgrade? or I might encounter problems later on if I want for example to root or unlock boot loader? (I don't care much for customization I just use Titanium Backup for freezing or deleting bloatware)
Click to expand...
Click to collapse
I'm sticking with Oreo because I don't like Pie, so that's down to your personal preference. You can find Oreo FW ending .20 in threads knocking about here. As for the persist.sin, you simply don't flash it, I think in the flashtool you can exclude it but if you use Newflasher you just delete it from the folder before flashing.
Give THIS thread a read.
SXUsr said:
I'm sticking with Oreo because I don't like Pie, so that's down to your personal preference. You can find Oreo FW ending .20 in threads knocking about here. As for the persist.sin, you simply don't flash it, I think in the flashtool you can exclude it but if you use Newflasher you just delete it from the folder before flashing.
Give THIS thread a read.
Click to expand...
Click to collapse
Ok I have the fw and deleted the persist file (persist_X-FLASH-ALL-C93B.sin, is this the right one?). Now just flash with newflasher? I do not have to backup TA partition (drm keys) or anything else?. Sorry for so many questions, I do not have a lot of experience on this and I do not want to mess it up.
Thanks again for your time!
craspo said:
Ok I have the fw and deleted the persist file (persist_X-FLASH-ALL-C93B.sin, is this the right one?). Now just flash with newflasher?
Click to expand...
Click to collapse
Yes, and yes.
craspo said:
I do not have to backup TA partition (drm keys) or anything else?. Sorry for so many questions, I do not have a lot of experience on this and I do not want to mess it up.
Thanks again for your time!
Click to expand...
Click to collapse
You only need to backup your TA if you're going to unlock the bootloader, if you're just flashing FW it doesn't matter.
SXUsr said:
Yes, and yes.
You only need to backup your TA if you're going to unlock the bootloader, if you're just flashing FW it doesn't matter.
Click to expand...
Click to collapse
Everything worked perfectly! Thank you, thank you very much for your time an patience!
craspo said:
Everything worked perfectly! Thank you, thank you very much for your time an patience!
Click to expand...
Click to collapse
You're welcome!
I'm currently on rooted:
XQ-AT51_Customized UK_1321-7192_58.0.A.0.1040_R8A
Looking to update to:
XQ-AT51_Customized UK_1321-7192_58.0.A.3.31_R8A
What's the best way to do this?
Research seems to suggest delete all .TA files aswell as the userdata file and if that works, to flash an extracted/pactched boot.img that I've already prepped. Though some users mention that they then get a decryption error resulting in the need to fully wipe.
I'd be grateful to hear from anyone who has successfully updated their Xperia 1 ii (with Flashtool or newflasher?).
Many thanks
Bump - anyone successfully updated their rooted firmware yet?
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Montane said:
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Click to expand...
Click to collapse
Hmm I thought that by being rooted/bootloader unlocked it's messed with the system updates. See attached, as Xperia Assist says there's an update available yet then clicking via Software Update it says I'm up to date.
I'm on 58.0.A.0.1040 customized UK and yet there's 58.0.A.3.39 available via Xperifirm
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Winrahr said:
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Click to expand...
Click to collapse
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Winrahr said:
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
Click to expand...
Click to collapse
Thanks yeah I may try that, or just stick to clean flashes
Montane said:
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Click to expand...
Click to collapse
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
cd993 said:
Thanks yeah I may try that, or just stick to clean flashes
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
Click to expand...
Click to collapse
Feels good to have an sd card to put all your backups on again doesn't it haha. I will not miss having to back up the internal storage slowly through USB2.0 just in case I have to wipe the entire storage.
I'm going to try a dirty flash on the next firmware update and hopefully I don't soft brick it again. Not having TWRP is new and scary to me.
Bump
With an updated firmware slowly rolling out (the one adding the RAW support and July security update) patch) etc, anyone managed to update when bootloader unlocked and rooted, avoiding losing data?
If I have to do a clean flash it wouldn't be the end of the world but I would love to avoid the hassle of (even with the usage of Swift Backup etc) and little things like not losing my autobrightness settings which have been learning my usage etc
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
YandereSan said:
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
Click to expand...
Click to collapse
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Newflasher guy gets mad when you talk about anything other than flashing every file so I'll post my update here.
Removed persist.sin and userdata.sin from the 3.88 update and ran through newflasher v33. Booted right back up and lost no data. YMMV.
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
By "rooting" for WiFi calling did you just flash another customization or did you unlock the bootloader? AFAIK there's no reason to root for getting WiFi calling as flashing another firmware is the easiest way.
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
Do you mean to say you received at OTA update notification via the system update option when rooted? Or you did a manual flash via newflasher?
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Montane said:
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Click to expand...
Click to collapse
If you unlocked your bootloader then you will not be able to take OTAs. You do not need to have bootloader unlocked to flash another stock firmware (ie through flashtool or newflasher). You do need to have bootloader unlocked to obtain root privileges.
cd993 said:
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Click to expand...
Click to collapse
I unlocked my Xperia 1 II, downloaded the latest raw update from XperiFirm, deleted the userdata file, put the phone into download mode (vol. down + power), flashed via NewFlasher v33.
Phone booted up perfectly fine. Running the latest update and have raw option for all 3 cameras.
The only time your device will wipe is when you first unlock the bootloader. Otherwise, you shouldn't have any issues updating it.