Related
any one using the rogers and know when will the update for 4.4?
yghrv said:
any one using the rogers and know when will the update for 4.4?
Click to expand...
Click to collapse
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X
flashallthetime said:
I gave up weeks ago waiting for the rogers(robbers) update, flashed the tmobile sbf 4.4 firmware on my unlocked boot loader moto. The way I see it we're probably last to receive the update, US done , now South Americian carriers, so assume sometime in January
Sent on my Moto X
Click to expand...
Click to collapse
disappoint about that, the first Moto X was saled with Rogers and then turns out to be the last one to update....
Also running the dev edition/retail firmware - it is totally the way to go. Forget about Rogers. I suspect Motorola already compiled 4.4 for them and they are sitting on it like they did the camera update. The only feature the Rogers firmware will likely offer is LTE on/off in the menu. I can't think of anything else it has going for it.
Running the retail version also gets rid of the carrier name in the upper left which is just silly to have anyway.
Should I unlock my bootloader? What does the warranty cover anyways?
alu0506 said:
Should I unlock my bootloader? What does the warranty cover anyways?
Click to expand...
Click to collapse
Well if the hardware was to fail such as the headphone jack breaking, ram going bad, speaker crapping out etc it would be covered under warranty. Once you request the bootloader unlock key that is gone. I figured since my phone was solid for more then a month and being I bought it used anyway I didn't have much to lose by unlocking the bootloader. For me it was the right move, used phones are getting cheaper on craigslist everyday if it does break and has to be replaced.
Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk
alu0506 said:
Yeah, I just checked. It doesn't cover physical damages so I'm gonna unlock the boot loader and maybe flash the Dev version.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Sounds good - any problems or questions let me know!
Steve-x said:
Sounds good - any problems or questions let me know!
Click to expand...
Click to collapse
Got it unlocked! What should I flash.... hmmm....
alu0506 said:
Got it unlocked! What should I flash.... hmmm....
Click to expand...
Click to collapse
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2
Works well on my Rogers phone, if you decide to flash one of the kitkat customs roms, you need the kitkat modems
Sent on my Moto X Running Beanstalk 4.4.2
Steve-x said:
Try this first:
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
What is it exactly? Is it pre-rooted or should I flash supersu?
alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
It is the retail/dev edition 4.4 kitkat rom. It is 100% stock as released by Motorola, you can root it after installing.
alu0506 said:
What is it exactly? Is it pre-rooted or should I flash supersu?
Click to expand...
Click to collapse
Its not a ROM but the stock firmware, it flashes the boot loader, stock recovery, modems and system files after it boots you can then flash twrp recovery for kitkat and flash supersu
Sent on my Moto X Running Beanstalk 4.4.2
Oh no.... I made have made a little oops.
I flashed everything and then selected normal powerup.
Booted to the warning screen, vibrated and got stuck...
[EDIT 1] GOT IT TO BOOT TO BOOTLOADER WOOT FLASHING AGAIN
[EDIT 2] Reflashed again... is it supposed to be at the warning screen for a long time after first reboot?
If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.
Steve-x said:
If you're in the bootloader I'd flash it again, may have been a failure in the data transfer.
Click to expand...
Click to collapse
I redownloaded it and reflashed and IT BOOTED! YAY! THANK YOU!
process
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
gthompson75 said:
What's the exact process to flash this file. Do I need custom recovery first? If you could list the steps for me that would be awesome.
Click to expand...
Click to collapse
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358
Thanks,
alu0506 said:
Well this is what I did:
Step 1. Download the latest drivers and adb/fastboot
If you already have the android adk installed, go to https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and download and install the latest drivers. Otherwise try this http://forum.xda-developers.com/showthread.php?t=2588979. I have never used it before but it looks like it should install both adb/fastboot and their corresponding drivers.
Step 2. Download mfastboot.exe
Go to https://drive.google.com/file/d/0B-SutxHydqfNczVMVXNtRVI4ZW8/edit?usp=sharing and download the file. This is motorola fastboot. You use it in place of the fastboot that came with the android sdk. For some reason, the fastboot that comes with the android SDK seems to not work when flashing some things. Download the file and save it somewhere.
Step 3. Download the Retail/Dev 4.4 rom
Thanks Steve-x for showing me this!
http://sbf.droid-developers.org/download.php?device=0&file=2
Download this file and unzip it.
Step 4. Unlock the bootloader
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth and follow the instructions to have a unlock code mailed to you. Remember, this will void your warranty AND WILL WIPE YOUR DATA. REMEMBER TO DO A BACKUP! I DIDN'T AND IT WAS A REALLY BAD MISTAKE.
Step 5. Flash the Retail/Dev rom
Remember that mfastboot.exe file that you downloaded earlier? Well it’s time to put it to good use. Copy (or move) the file to the directory where the rest of the Retail/Dev 4.4 rom files are located. (The zip that you extracted earlier, the one with the “system.img” in it?)
Now that you've done that, open “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” with your favorite plain text editor. (Use notepad if you have no favorite) We have to make it so that instead of using the standard android fastboot.exe to flash the files, it uses the mfastboot.exe. So, just edit the first line, “SET fastboot=fastboot.exe”, to “SET fastboot=mfastboot.exe”. Save and close it up.
Now, put your Moto X into bootloader mode if it isn't already. Power it down and then press the power and volume down buttons simultaneously until it powers on. Connect the usb cable to the computer, and wait for the pc to recognize everything. Now double-click on the “TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.bat” and it will start flashing.
After it is complete, turn the phone on by selecting “Normal Powerup” on the device. To navigate around the bootloader, use the volume down arrow key to select the option and the volume up key to execute it. If everything went correctly, your Moto X show powerup and boot into Android 4.4!
I think thats everything. If you need help please do ask!
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Oh right, if you want a custom recovery and root, this thread explains the process nicely http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
Thank you for the detailed info. When updates come out will we get them rogers or tmob/retail
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.
Hey guys,
Even after reading tons of threads, I cant seem to manually sideload an update for 5.0.1.
I just got this Nexus 6, but have been a long time user since Nexus 4.
What is the easiest way to upgrade to 5.0.1 without loosing all my data? Thanks again!
So you're stock unrooted? What happens when you sideload? Please give more info
Ive already tried to download the patch but cant seem to apply, even following a few guides.....
Reply
rootSU said:
So you're stock unrooted? What happens when you sideload? Please give more info
Click to expand...
Click to collapse
I am stock, rooted, unlocked. I tried to manually sideload with no success. I also tried the nexus toolbox. I get all the way to the end, and it looses ADB connection
@RoysGTI
If you are rooted, you will not be able to side load the update. And "unroot" will still leave some files which will prevent it from installing.
You need to extract the system.img from 5.0.0 and fastboot flash it. This will leave your user data intact. Then after flashing the update, you will have to reroot.
I assume you are still encrypted?
cam30era said:
@RoysGTI
If you are rooted, you will not be able to side load the update. And "unroot" will still leave some files which will prevent it from installing.
You need to extract the system.img from 5.0.0 and fastboot flash it. This will leave your user data intact. Then after flashing the update, you will have to reroot.
I assume you are still encrypted?
Click to expand...
Click to collapse
Could you assist me in the flashing of the system.img? How will that get me to 5.0.1?
I am not sure if I am encrypted or not.....
RoysGTI said:
Could you assist me in the flashing of the system.img? How will that get me to 5.0.1?
I am not sure if I am encrypted or not.....
Click to expand...
Click to collapse
You need to take a step back and do some reading and studying before doing anything else with your phone. You don't want to risk doing something wrong and bricking your device. Read and study these tutorials before proceeding further. Make sure you thoroughly understand everything, before proceeding. And don't hesitate to ask questions in those respective threads.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
cam30era said:
You need to take a step back and do some reading and studying before doing anything else with your phone. You don't want to risk doing something wrong and bricking your device. Read and study these tutorials before proceeding further. Make sure you thoroughly understand everything, before proceeding. And don't hesitate to ask questions in those respective threads.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Ok, I followed the first steps again, and restored back to original stock factory image. Going to check my version and then reroot.
Once I root again, will I have to do this same process for every OTA update?
RoysGTI said:
Ok, I followed the first steps again, and restored back to original stock factory image. Going to check my version and then reroot.
Once I root again, will I have to do this same process for every OTA update?
Click to expand...
Click to collapse
OTA will not install if you are rooted.
cam30era said:
OTA will not install if you are rooted.
Click to expand...
Click to collapse
Got updated to 5.0.1 with root access now. Thanks again for your help! It def. helps starting from scratch.
RoysGTI said:
Got updated to 5.0.1 with root access now. Thanks again for your help! It def. helps starting from scratch.
Click to expand...
Click to collapse
There's a button for that.
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
mrkhigh said:
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Pkt_Lnt said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
mrkhigh said:
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
Click to expand...
Click to collapse
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Pkt_Lnt said:
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Click to expand...
Click to collapse
That's what I thought.
Thanks for the links,
But I'm still looking for TWRP flashable if anyone knows of one?
This should be a relatively easy thing so I'm surprised it doesn't exist
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
leo5111 said:
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
Click to expand...
Click to collapse
TWRP can flash a stock image if someone creates it. Unless there is something odd about the nexus, but I doubt that. The only thing that shouldn't be flashed stock would be recovery.
I don't think I need to use some toolkit... adb and fastboot commands are simple enough.
I was hoping to avoid needing a PC at another persons house, I mean that is kinda the point of twrp.
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
If I owned the device I would make it for you guys. It seems something that is lacking that is really handy.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Google has done that for you already. Just unpack the archive you choose and the four images are in there.
https://developers.google.com/android/images
I thought we've already decided I cannot flash these images with TWRP....
mrkhigh said:
I thought we've already decided I cannot flash these images with TWRP....
Click to expand...
Click to collapse
http://www.droidviews.com/now-flash-image-files-using-twrp-2-8-4-0/
Different Google search gave this. I can find nothing else on TWRP site or G+
Appears you can also use FlashFire.
Thanks for the help.
OP could flash one of the stock lite ROMs in the development forum and get the TWRP-flashable stock ROM he's looking for. Danvdh and tupac4u both offer one that is nothing more a debloated stock ROM.
TWRP is able to flash system images from 3.0.2 and on. Just unpack the archive and select install img. Remember to flash stock kernel and newest radio and bootloader too (bare in mind that flashable bootloader is harder to find. You might have to find older one and update the files inside on your own). Afterwards flash stock recovery and lock bootloader with a zip. Now you can just reboot it. It's not that hard.
Lawstorant said:
....bare in mind that flashable bootloader is harder to find....
Click to expand...
Click to collapse
For Nexus 6 https://forum.xda-developers.com/showthread.php?p=59728002/
Thank you.
I went ahead and simply flashed him 100% stock via flash and fastboot.
This is probably resolved now, just adding info though. I had flashed stock 7.1.1 zip downloaded from google via twrp 3.0.3.0. It removed twrp itself too and I was back on stock.
mrkhigh said:
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Click to expand...
Click to collapse
Try the app FlashFire.
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