Best way to update rooted firmware? - Sony Xperia 1 II Questions & Answers

Best way to update rooted firmware? - Sony Xperia 1 II Questions & Answers

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.

Related

Possible Brick? Need Help Urgently!

Hi there guys,
I have a locked bootloader on my Sony Z1, I have the dual recovery (at least, I did), I flashed something, just a different boot animation and afterwards the boot animation didn't work properly.
So I went back to recovery to restore the backup that I had made just before flashing the boot animation and it came up with an error half way through restoring the /System, and aborted.
After it aborted and exited recovery, on the way out it said "No Root Access Detected" and asked if I wanted to "Reroot" it, so I said yes.
Now when it boots, it just sits on the "Sony" screen, with no colour on the LED, or anything. Can't hold the buttons to go to recovery either.
Can't use the Sony Flashtool, because that requires an unlocked bootloader, and I can't use the Sony Software Companion, because that requires the phone to fully boot.
Is there anything that you guys can suggest?
Thanks in advance.

corydor13 said:
Hi there guys,
I have a locked bootloader on my Sony Z1, I have the dual recovery (at least, I did), I flashed something, just a different boot animation and afterwards the boot animation didn't work properly.
So I went back to recovery to restore the backup that I had made just before flashing the boot animation and it came up with an error half way through restoring the /System, and aborted.
After it aborted and exited recovery, on the way out it said "No Root Access Detected" and asked if I wanted to "Reroot" it, so I said yes.
Now when it boots, it just sits on the "Sony" screen, with no colour on the LED, or anything. Can't hold the buttons to go to recovery either.
Can't use the Sony Flashtool, because that requires an unlocked bootloader, and I can't use the Sony Software Companion, because that requires the phone to fully boot.
Is there anything that you guys can suggest?
Thanks in advance.
Click to expand...
Click to collapse
There are some issues with restoring backups on dual recovery, i think this is fixed with the latest version of dual-recovery(check that thread for updates). Do not use Sony flashtool, use the this flashtool http://forum.xda-developers.com/showthread.php?t=2439328 - read from Part 4 and you can download firmwares from here http://forum.xda-developers.com/showthread.php?t=2469191.

sofir786 said:
There are some issues with restoring backups on dual recovery, i think this is fixed with the latest version of dual-recovery(check that thread for updates). Do not use Sony flashtool, use the this flashtool http://forum.xda-developers.com/showthread.php?t=2439328 - read from Part 4 and you can download firmwares from here http://forum.xda-developers.com/showthread.php?t=2469191.
Click to expand...
Click to collapse
Thank you so much!
I am on 02 in the UK, and hate the fact it has the stupid 02 bubble up and down animations, so would it be fine if I used to Generic UK FTF?
and would there be any disadvantage to using this one over the 02 FTF?
also, on the first link you posted, it said to download the EXE for the application and I have done that, but it said to download the device files folder they have, and place that in the flashtool folder, but the device files link isn't there? So what do I have to do?
Place the FTF in the folder they specified, or?
(sorry if I seem a noob, come from using/flashing HTC's for years)

corydor13 said:
Thank you so much!
I am on 02 in the UK, and hate the fact it has the stupid 02 bubble up and down animations, so would it be fine if I used to Generic UK FTF?
and would there be any disadvantage to using this one over the 02 FTF?
also, on the first link you posted, it said to download the EXE for the application and I have done that, but it said to download the device files folder they have, and place that in the flashtool folder, but the device files link isn't there? So what do I have to do?
Place the FTF in the folder they specified, or?
(sorry if I seem a noob, come from using/flashing HTC's for years)
Click to expand...
Click to collapse
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares

sofir786 said:
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares
Click to expand...
Click to collapse
Ah ok then. Yeah, I have the HTC One too. Just chucked my SIM in that until I get the Z1 up again, lol.
Thanks a lot. I'll update when it's working again.

sofir786 said:
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares
Click to expand...
Click to collapse
Should I exclude any of the things that are options in the FlashTool?

corydor13 said:
Should I exclude any of the things that are options in the FlashTool?
Click to expand...
Click to collapse
Nah not really, you can untick data if you want so that doesnt get wiped but i would do a full wipe and leave everything as is when you flash.

sofir786 said:
Nah not really, you can untick data if you want so that doesnt get wiped but i would do a full wipe and leave everything as is when you flash.
Click to expand...
Click to collapse
Got it all back up and working. All the inbuilt apps updated and system updated to the newest version.
Just need to download all the apps I had, possibly think about rooting it and that tomorrow.
xD.

corydor13 said:
Got it all back up and working. All the inbuilt apps updated and system updated to the newest version.
Just need to download all the apps I had, possibly think about rooting it and that tomorrow.
xD.
Click to expand...
Click to collapse
ah great stuff. Just to let you know this firmware - 14.1.G.2.257 - is not currently rootable, thought id give you a heads up.

sofir786 said:
ah great stuff. Just to let you know this firmware - 14.1.G.2.257 - is not currently rootable, thought id give you a heads up.
Click to expand...
Click to collapse
The update that I just got on my phone says "14.1.G.1.534"

corydor13 said:
The update that I just got on my phone says "14.1.G.1.534"
Click to expand...
Click to collapse
your cool then, you dont have to worry, that version firmware is rootable

sofir786 said:
your cool then, you dont have to worry, that version firmware is rootable
Click to expand...
Click to collapse
Thank you.

Xperia Z will not update, what steps can I take to get the proper firmware on it?

Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.

tinodevoe said:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
Click to expand...
Click to collapse
can you take a screenshot of the 6616 screen? and can you go to the firmware by customization thread and follow the instructions? what is your cust.# ?

Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.

tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
I think you can flash c6606 Software without problems... Maybe even of C6603 via Flashtool.

tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
OK, that is really very strange. You could try to contact DoomLord or Apollo89, they have knowledge of such things.
Are you rooted? Can you do a CWM Backup? I suggest having a full backup before flashing another rom. So in case you need it, you can flash it back.
I am not sure if you have the same kernel as the rest of us. If you can not do a CWM backup, and are not rooted, you need to find a way to extract the file "boot.img" from the phone. This is the kernel, which you can easily flash back. But for this operation, a bootloader unlock will most probably be necessary.
If you can get no help from Doom or Apollo and can not extract boot.img, you might need to flash hoping for luck, or stay on the firmware you have.
Disclaimer: I might be much too paranoid, after all your phone seems to have the same hardware as the normal one, and a flash of a 10.4.B.0.569 ROM should be no problem. I just don't want to be the one that did not warn you and be responsable for a broken phone...
===============================================================
EDIT: Just had a look at the thread, C6616 is bell Canada, if you had found that, you could have reported back and told us that you solved the problem.
===============================================================

thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.

tinodevoe said:
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
Click to expand...
Click to collapse
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet

N1k0la89 said:
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
Click to expand...
Click to collapse
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.

tinodevoe said:
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
Click to expand...
Click to collapse
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).

akisg said:
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
Click to expand...
Click to collapse
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?

tinodevoe said:
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
Click to expand...
Click to collapse
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..

akisg said:
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
Click to expand...
Click to collapse
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?

tinodevoe said:
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
Click to expand...
Click to collapse
As soon you are installing a stock rom, you don't have to worry about root.
But if you wanna root, your only choice is to flash a 4.2 rom, root it with a method of your choice and then upgrade to a prerooted 4.3.

Can someone please point me in the right direction to a FW that works with my phone? the only one that I seem to be able to use with flashtool is this one here which is 4.1.2. http://forum.xda-developers.com/showthread.php?t=2390178
however it won't let me update the system!
I'm guessing that I need a C6616 firmware to make this work, but I also tried this one, http://forum.xda-developers.com/showthread.php?t=2612159 and I get an error in flashtools, in red writing 'ERROR - error flashing. Aborted'.
I've been searching on here and all the other firmwares are 6603 which I tried a couple and again errors in flashtools.
trying again with that 4.1.2 its flashing it but its not the firmware I need!

ok, finally got one of them to work! I'm not sure what it was but I downloaded a bunch of firmwares until one of them finally updated me to 4.3.
thanks for all the help!

New NEXUS6

So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks

nixie2121 said:
So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks
Click to expand...
Click to collapse
Once you root lollipop you can't accept OTAs, however you can flash the update via fastboot.

nixie2121 said:
So I will have my new phone from T mobile on Wednesday and want to unlock and root it right away. I have read how to do it and it looks easy enough.
If I keep stock Rom and don't flash a custom kernel, can i still get updates or once you root can you no longer update?
thanks
Click to expand...
Click to collapse
Hi! Welcome to the Nexus 6 community.
First, keep doing what you have been doing. Reading! That's the best way to learn the how to's.
As far as OTA's, lollipop requires that NO system modifications are present for OTA to flash. However, there are many ways around this "feature". Keep searching and reading here, as all of these topics have been addressed. Always remember, Google is your friend too.

Pilz said:
Once you root lollipop you can't accept OTAs, however you can flash the update via fastboot.
Click to expand...
Click to collapse
I have been reading around, mostly on tapatalk (hard to find things!)
Anyway, could you answer this question (I will learn about flashing updates via fastboot soon, maybe you can point me to a good thread to learn this?)
When I flash an update, is it like flashing a new rom meaning all apps, settings and such are wiped?
Thanks so much!!!

nixie2121 said:
I have been reading around, mostly on tapatalk (hard to find things!)
Anyway, could you answer this question (I will learn about flashing updates via fastboot soon, maybe you can point me to a good thread to learn this?)
When I flash an update, is it like flashing a new rom meaning all apps, settings and such are wiped?
Thanks so much!!!
Click to expand...
Click to collapse
This OP is a good start
http://forum.xda-developers.com/showthread.php?t=2948481
When you flash a update via fastboot don't use the flash-all.bat file because it will encrypt your phone ( if you decrypted) and wipe the user data. Flash each image manually (I always do this) and you will be fine. If you want a break down of the order I'll post it and or link a post for updating while rooted.

Pilz said:
This OP is a good start
http://forum.xda-developers.com/showthread.php?t=2948481
When you flash a update via fastboot don't use the flash-all.bat file because it will encrypt your phone ( if you decrypted) and wipe the user data. Flash each image manually (I always do this) and you will be fine. If you want a break down of the order I'll post it and or link a post for updating while rooted.
Click to expand...
Click to collapse
Did you decrypt? I see the thread on how to do that as well.

nixie2121 said:
Did you decrypt? I see the thread on how to do that as well.
Click to expand...
Click to collapse
Yes I did (Its one of the first things I did) if you wait then you will lose your user data. When you encrypt or decrypt and or unlock/re-lock the BL it will wipe your phone.

MM Update (QI2) - TWRP Won't Install!!!

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.

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

Got a XZ1c but I have a bit of a problem

I've recently purchased an XZ1c since my old z3c was basically falling apart at this point. (Would have kept it if the repair guy didn't royally screw things up.)
The phone is practically untouched physically and has been great for the past two weeks... It was when I tried taking pictures that I've noticed my first problem.
Green pictures had to reboot to see if the bootloader was unlocked and to my chagrin, the previous owner never told me they had unlocked the phone in the first place and didn't even know about DRM keys so those are lost.
I've rooted my old z3c before a long time ago and it was painless. Now with this phone, I'm having a bit of a problem and I'm hesitant to even try rooting it since I haven't rooted a phone since and I would prefer getting advices.
I am aware of the guide on rooting the phone and would have no problems following it if it wasn't for the fact that my phone's build was currently 47.1.A.12.270 and the guides use the .16.20 update but can't find the files to update to the September build. Model G8441
Since the phone is unlocked, I can't update through the normal means in order to get to that update or get 9.0 for that matter in order to do the root. Is there a guide on updating the phone to those before using the guide to root it? I haven't done this in a long time and don't remember anything. Thanks in advance!

Kesymos said:
I've noticed my first problem.
Green pictures had to reboot to see if the bootloader was unlocked
Click to expand...
Click to collapse
Every time to you boot or reboot it should tell you it's been unlocked. I'd have sent it back as soon as I booted it up.
Kesymos said:
Since the phone is unlocked, I can't update through the normal means in order to get to that update or get 9.0 for that matter in order to do the root.
Click to expand...
Click to collapse
As you don't need to worry about your TA partition use the Flashtool or Newflasher to upgrade to Pie, flash TWRP, install Magisk, done.

SXUsr said:
As you don't need to worry about your TA partition use the Flashtool or Newflasher to upgrade to Pie, flash TWRP, install Magisk, done.
Click to expand...
Click to collapse
I don't need to worry about going to .16.20 before upgrading to pie, just go directly?
If so, it's a lot easier than I thought. With my z3c I had to upgrade to a specific build prior rooting.
Just to make sure, the phone comes from the US so I should get the Customized US version for 47.2.A.11.228?

Kesymos said:
I don't need to worry about going to .16.20 before upgrading to pie, just go directly?
Click to expand...
Click to collapse
Correct.
Kesymos said:
Just to make sure, the phone comes from the US so I should get the Customized US version for 47.2.A.11.228?
Click to expand...
Click to collapse
Sure. If you have issues with the fingerprint reader give some of these THREADS a read.

SXUsr said:
Sure. If you have issues with the fingerprint reader give some of these THREADS a read.
Click to expand...
Click to collapse
Thanks, I'm not really going to use the feature but if It causes problem, I'll look into it. My only problem now is finding and downloading the tft file for the update so I can flash but I'm having difficulty finding such thing.
I was able to download the DE version that is over 2 gigs. Does the version truly matter?

Kesymos said:
My only problem now is finding and downloading the tft file for the update so I can flash but I'm having difficulty finding such thing.
Click to expand...
Click to collapse
Open the flashtool, run Xperifirm and it's there.
Kesymos said:
I was able to download the DE version that is over 2 gigs. Does the version truly matter?
Click to expand...
Click to collapse
Not really, apart from bloatware.

SXUsr said:
Open the flashtool, run Xperifirm and it's there.
Click to expand...
Click to collapse
Oh wow, even more proof I haven't done this in a while, I completely forgot about xperifirm, still have it on my computer, just need to update it. Now I feel dumb.
Thanks again for the reminder!

Database Develop

welcome