[Q] XT1097 unstoppable reboot - X 2014 Q&A, Help & Troubleshooting

[Q] XT1097 unstoppable reboot - X 2014 Q&A, Help & Troubleshooting

Hello mighty XDA developers,
Reason(?):
I have f**ked my XT1097 (Bootloader unlocked, Telus, Canada). I tried to root my Lollipop phone with bhp090808's multi-tool V4.1. Somehow the tool was unsuccessful on rooting my phone. It installed supersu and that was that.
With Supersu installed, apps were somehow unable to download from Google Play, therefore I disabled it and the problem was gone. I was then in vacation so I have no access of Windows so I left it at that for a week, phone ran normally.
After I got back form vacation, I reverted my phone back to stock recovery and 4.4.4 with the Multi-tool, in order to try re-rooting the phone. I might or might not have started the root process when I was in 4.4.4 (I honestly don't remember). Afterwards my phone's wifi stopped working (cannot be turned on or off, with the status of "Turning Wifi On"). The phone also reboots itself after around 1 minute.
I have a bad flash, now whenever I update to Lollipop, my wifi stops working and I get nonstop reboots. Phone is perfectly fine when I stay in KK
and I have lost my IMEI
Tried methods:
- I have tried erasing the phone by going into the backup and reset menu to reset the phone,the same problems remain.
- I have tried clearing the phone by erasing data and catch from stock recovery, the same problems remain.
- I have tried using the Muti-Tool to revert back to stock. but then the phone restarts every time before adb can do anything
- I have tried using RSD, flashing the Brazilian XT1097 .img into the phone. Despite a successfully flash, the same problems remain.
Problem:
- Phone's wifi is stuck
- Phone keeps rebooting (safe mode or not)
- When phone is powered off, it will restart itself and then go on the reboot loop again (even when i boot into safe mode and turn it off form there)
- Phone does not turn off without rebooting itself other than powering off from Recovery
- Phone Cannot be charged
Help needed!
I really messed my phone up and need help! Please can someone suggest a solution? I dont have TWRP so I cannot wipe system and reinstall
Motosurf

BlueEditionE6 said:
After I got back form vacation, I reverted my phone back to stock recovery and 4.4.4
Click to expand...
Click to collapse
It is dangerous to downgrade a Moto X. This is not a Nexus device.
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
BlueEditionE6 said:
I dont have TWRP so I cannot wipe system and reinstall
Click to expand...
Click to collapse
Press and hold the power button to shut it off and then immediately press and hold the vol down and then press and hold power. Hold both for about 4 seconds and release. This should put you into fastboot mode. Then plug the device into your computer and start Motorola Device Manager.
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
BlueEditionE6 said:
ps. the phone's battery is so low that it cant do anything. Wondering if the phone charges in Recovery mode. Battery status says charging, but I am not sure?
Click to expand...
Click to collapse
Do you have a turbo charger or know anyone who does?

JulesJam said:
It is dangerous to downgrade a Moto X. This is not a Nexus device.
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Press and hold the power button to shut it off and then immediately press and hold the vol down and then press and hold power. Hold both for about 4 seconds and release. This should put you into fastboot mode. Then plug the device into your computer and start Motorola Device Manager.
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
Do you have a turbo charger or know anyone who does?
Click to expand...
Click to collapse
yea i wasnt having trouble getting into fastbootmode. And turns out the phone does charge while in recovery

BlueEditionE6 said:
yea i wasnt having trouble getting into fastbootmode. And turns out the phone does charge while in recovery
Click to expand...
Click to collapse
OK so did you reflash system?

JulesJam said:
OK so did you reflash system?
Click to expand...
Click to collapse
reflashed KK, when i update to L, it does the same thing again.

BlueEditionE6 said:
reflashed KK, when i update to L, it does the same thing again.
Click to expand...
Click to collapse
Are you taking the OTA to get back to L? And if so, are you completely stock when you take the OTA?

JulesJam said:
Are you taking the OTA to get back to L? And if so, are you completely stock when you take the OTA?
Click to expand...
Click to collapse
Reverted to KK from the multi-tool and used the ota (XT1095), as well as reverted back to KK and used the xt1097 ota. same issue. I cannot find the XT1097 KK img

BlueEditionE6 said:
Reverted to KK from the multi-tool and used the ota (XT1095), as well as reverted back to KK and used the xt1097 ota. same issue. I cannot find the XT1097 KK img
Click to expand...
Click to collapse
If you are not completely stock 100%, it is best not to take the OTA b/c the OTA is a patch.
I would revert back to whatever version of KK system you did before, and also have a stock recovery. Then use Motorola Device Manager to get back to L. MDM should flash the correct version of system for your device.
Do you have MDM on your computer?

JulesJam said:
If you are not completely stock 100%, it is best not to take the OTA b/c the OTA is a patch.
I would revert back to whatever version of KK system you did before, and also have a stock recovery. Then use Motorola Device Manager to get back to L. MDM should flash the correct version of system for your device.
Do you have MDM on your computer?
Click to expand...
Click to collapse
Motorola Device Manager? Does it work like that ? No the problem is I dont have my original firmware, The web does not seem to have victara_retca.retca.en.ca.tkpca. kk nor L. Put up a seperate post asking if anyone has it on xda and on MotoFirmware

BlueEditionE6 said:
Motorola Device Manager? Does it work like that ? No the problem is I dont have my original firmware, The web does not seem to have victara_retca.retca.en.ca.tkpca. kk nor L. Put up a seperate post asking if anyone has it on xda and on MotoFirmware
Click to expand...
Click to collapse
Motorola Device Manager should download it and install it to your phone if you flash back to kit kat and then run MDM with your phone connected to your computer.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Also, you will end up with a copy of the firmware on your computer in :
c:\programdata\motorola\sue\firmwares

JulesJam said:
Motorola Device Manager should download it and install it to your phone if you flash back to kit kat and then run MDM with your phone connected to your computer.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Also, you will end up with a copy of the firmware on your computer in :
c:\programdata\motorola\sue\firmwares
Click to expand...
Click to collapse
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?

BlueEditionE6 said:
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?
Click to expand...
Click to collapse
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip

Steve-x said:
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip
Click to expand...
Click to collapse
OH WOW THANKS! i have been looking for this all along!

BlueEditionE6 said:
just to be sure, even if i flash into a 1095 kk, mdm would flash me back to 1097?
Click to expand...
Click to collapse
All you can do is try, you have flashed back to KK before so you know it doesn't brick your phone. I am only talking about flashing the SYSTEM (system.img) back to kit kat, not the bootloader or the partition table. If you have a custom recovery, I don't think it will work though. I think you need a stock recovery. The recovery can be lollipop.
When I flash my Verizon XT1096 back to kitkat system, with lollipop stock recovery, MDM will flash my system back to lollipop.
I understand about the issue with the different models, and I can't tell you whether MDM will have a problem with that or not, but if it does, it will just do nothing. You have flashed back to XT1095 KK before so I don't see why it would hurt to see what MDM does. It will be able to tell you have an XT1097 so it won't try to install a system for an XT1095.

Steve-x said:
You have to flash the stock Telus firmware.
Use rsdlite or mfastboot to return your phone to stock 5.0.1.
You can download it here: (yes it will take a few hours)
http://www.filefactory.com/file/7hv608q62qc5/RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Hi steve, I am getting "Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL
Did i do something wrong?
EDIT: replaced the gpt file and the motoboot file with the 5.0.1 file.
EDIT 2: at 4.4.4 rectca, imei and radio is back, but there is no update to L, if I rsd the 5.0.1 rectca, the same issue comes back

What else have you all flashed, if you tried the 5.1 soak you likely will have to skip flashing gpt and motoboot.

Steve-x said:
What else have you all flashed, if you tried the 5.1 soak you likely will have to skip flashing gpt and motoboot.
Click to expand...
Click to collapse
I have tried flashing the 5.0 update front the multi tool. I tried removing get and process stopped
Sent from my XT1080 using XDA Premium 4 mobile app

Well I really feel like there is something you're not telling us that you've done in the past to the phone. Please try to give detailed answers.
#1 - Are you 100% sure it is a Telus phone and not a Wind Mobile XT1097?
#2 - When flashing the Telus 5.0.1 image what does the phone say when the process fails?
#3 - You mention flashing 4.4.4 - do you mean a full image or just some of the files like you are mixing and matching some 4.4.4 and some 5.0.1?

#1 - Are you 100% sure it is a Telus phone and not a Wind Mobile XT1097?
No, I won this poem from Motorola and it arrived to my doorsteps unlocked. It might be on Wind, sorry I didn't think of this possibility
#2 - When flashing the Telus 5.0.1 image what does the phone say when the process fails?
The process doesn't fail while fishing to L, it only failed when I tried to flash it from the broken L to KK. When my phone is on L, the wifi, signal doesn't work, and it reboots. As shown in the video
https://youtu.be/pDCCr2BE4n0
#3 - You mention flashing 4.4.4 - do you mean a full image or just some of the files like you are mixing and matching some 4.4.4 and some 5.0.1?[/QUOTE]
Well like I said I tried flashing the KK that you linked to me, but then it gets stuck at gpt and motoboot. So I got the two files from the L zip and KK flashes successfully. Works like a charm too. Other than that fact that it doesn't update
Extra info. I have had TWRP and CM12.1 just because it was the only way for the phone to charge
Sent from my XT1080 using XDA Premium 4 mobile app

It all sounds pretty weird. I suspect the phone may actually be a Wind mobile retail edition. They come factory unlocked, the Telus version would be locked.
The link I gave was Lollipop 5.0.1 for the Telus version. Being I think you have the Wind mobile here is the link for the Wind mobile 4.4.4:
http://www.filefactory.com/file/38yhbfahth0p/RETCA_XT1097_4.4.4_KXE21.187-52_cid14_CFC.xml.zip
When you download the file and try to flash using rsdlite gpt and motoboot will fail as they cannot be downgraded. This is not a problem. Just edit the xml file to remove them and then flash the entire package with rsdlite. When done you will be on factory 4.4.4. At that point you should get prompted to update to 5.0.1.

Related

[Q] rogers 4.4 update?

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

[How-To] Unbrick or Flash Back to Stock(NCE) - G900A Only

***The steps below will work on all Bootloader versions except OC4(Android 5.0), Do not use this process if you have taken the OC4 ota update!***
1. Download the G900A_Downgrade_to_NCE.rar and extract the .tar.
2. Go into Download Mode by pressing and holding the Home, Volume Down, and Power keys on your device until the phone powers on and displays warning screen, then press Volume Up key.
3. Flash the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+).
Note: The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Attention! If you have taken the OC4 ota update and need to unbrick after attempting to downgrade try flashing the: G900A_OC4_Stock_Partitions

So why is it that the g900a is the only gs5 that can't downgrade from 5.0? even Verizon can???

I had a different Downgrade to NCE file. Tried this one and my phone is back up and running. Phew!! Thanks so much!!

Is it safe to flash over ND3? I'm not recieving any ota. Will I receive Ota After flashing this?

DIME8611 said:
Is it safe to flash over ND3? I'm not recieving any ota. Will I receive Ota After flashing this?
Click to expand...
Click to collapse
Yes. You can OTA all the way to OC4.
Sent from my SAMSUNG-SM-G900A

Added G900A_OC4_Stock_Partitions to the OP for those that took the OC4 ota update and bricked while attempting to downgrade.

muniz_ri said:
Added G900A_OC4_Stock_Partitions to the OP for those that took the OC4 ota update and bricked while attempting to downgrade.
Click to expand...
Click to collapse
Muniz do u think there will be root method for those on 5.0 ota unrooted? ???

Phone gets stuck up!
For some reason. i tried to unbrick my phone from the rooted stock firmware 5.0 and it ended up with the boot loop. Already tried the downgrade to NCE. Now it gets worse because all I can see so far is the logo of ATT and that's it. Anyone could help me out with that???

NVQT said:
For some reason. i tried to unbrick my phone from the rooted stock firmware 5.0 and it ended up with the boot loop. Already tried the downgrade to NCE. Now it gets worse because all I can see so far is the logo of ATT and that's it. Anyone could help me out with that???
Click to expand...
Click to collapse
I'm sure you probably already tried this but if not pull the battery for a few seconds and then try going back into download mode and try the process again.
How did you upgrade to 5.0 (which method) You may have to provide more detail, there are a lot people who have way more knowledge than I do, but I hope this helps
Good luck and give the forums a search

unk2009 said:
I'm sure you probably already tried this but if not pull the battery for a few seconds and then try going back into download mode and try the process again.
How did you upgrade to 5.0 (which method) You may have to provide more detail, there are a lot people who have way more knowledge than I do, but I hope this helps
Good luck and give the forums a search
Click to expand...
Click to collapse
Thanks for the reply! I actually upgraded to 5.0 by the flashfire method since before that I already got the rooted 4.4.4. Just yesterday, when I left my phone for a while and came back, it started to stick with the bootloop, , the only method which could help it out is to plug it into the power source. I tried everything which includes removing battery and wiping factory downgrading, flashing original firmware, reinstalling the OTA 5.0 update through sdcard. None of that worked. If you have any information to help me out,I would be way happy to listen! Thank you !

I've had this same problem. Are you still bootlooping?
Sent from my SAMSUNG-SM-G900A

THANK YOU...
I'm with archie above - I tried a different downgrade file and it didn't work either - this one DID.
Thanks so much...

Thank you so much for this. Worked perfectly for a downgrade from 4.4.4. You're the best!
Currently installing updates OTA.

Hi muniz, I posted in your KeepRoot for 5.0 thread and then I saw this one. My phone seems to have spontaneously softbricked (system crashes and then it bootloops). Will flashing the stock 5.0 make me lose root?
EDIT: Fixed with a battery pull!

muniz_ri said:
Attention! If you have taken the OC4 ota update and need to unbrick after attempting to downgrade try flashing the: G900A_OC4_Stock_Partitions
Click to expand...
Click to collapse
Just to clarify, my S5 is on the OC4 build. Will I be able to downgrade to KK using the above file, or is it ONLY to fix a device that got bricked while trying to downgrade? If the latter, are OC4 users just hosed? I have scoured this site, but would appreciate links to any instructive threads that I may have missed. Thanks!

muniz_ri said:
***The steps below will work on all Bootloader versions except OC4(Android 5.0), Do not use this process if you have taken the OC4 ota update!***
1. Download the G900A_Downgrade_to_NCE.rar and extract the .tar.
2. Go into Download Mode by pressing and holding the Home, Volume Down, and Power keys on your device until the phone powers on and displays warning screen, then press Volume Up key.
3. Flash the G900A_Downgrade_to_NCE.tar using Odin's PDA slot(AP in Odin v3.09+).
Note: The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure!
Attention! If you have taken the OC4 ota update and need to unbrick after attempting to downgrade try flashing the: G900A_OC4_Stock_Partitions
Click to expand...
Click to collapse
HI, i flash using this method, everything pass and after rebooting, it got stock on a black screen and the LED light is blue, and i can´t use my pone and i don´t know how to , please help.
---------- Post added at 04:01 PM ---------- Previous post was at 03:56 PM ----------
javierascua said:
HI, i flash using this method, everything pass and after rebooting, it got stock on a black screen and the LED light is blue, and i can´t use my pone and i don´t know how to , please help.
Click to expand...
Click to collapse
and another thing before doing this downgrade i was on 5.0 but using flashfire

Vol4Ever said:
Just to clarify, my S5 is on the OC4 build. Will I be able to downgrade to KK using the above file, or is it ONLY to fix a device that got bricked while trying to downgrade? If the latter, are OC4 users just hosed? I have scoured this site, but would appreciate links to any instructive threads that I may have missed. Thanks!
Click to expand...
Click to collapse
Yes, those that took the OC4 ota are out of luck.

Muniz_ri, thxs very much i use your flash downgrade and solve my problem

Omg i love you!!!!!
It totally work for me, i downgrated from briked lolipop, and safe my phone!!!!!

help please
alright so i accidently flashed the gs5 active kernel onto my g900A and its completely bricked, like i cant even get into download or safemode from power off. please tell me therres a possible solution?!?

Moto X bricked after update

Hi !
I have a big trouble with my Moto X since I bricked it after trying to update the OS.
I was on LP 5.0 and I saw somewhere that an update was available so I searched for that and launched the update.
The problem was I didn't know that it's dangerous to do so with a rooted phone...
So, now, my Moto X is staying on the "splash screen" and if I force the power off, the Moto X restarts... and stays on the splash screen, again...
Is someone can help me to unbricked my phone ?
Thank you very much for your help :highfive:
A+
Edit : for information, it's a French Moto X 2014 (so I think it's a XT1052)

Smh

Can you get into fastboot? From off, hold volume down and touch the power for a second and continue holding volume down.

kcustom11 said:
Can you get into fastboot? From off, hold volume down and touch the power for a second and continue holding volume down.
Click to expand...
Click to collapse
Yes, but I don't remember if I update the bootloader.
The choices I have are :
- Normal powerup
- Recovery
- Factory
- Barcodes
- BP Tools
- QCOM
Thank you for your help

You're not bricked then. I don't know what the recovery instructions are for the French model. Do they have factory images on the support page?
You can volume up on recovery to get into recovery to see options about clear cache and factory reset. Those might help, but I doubt it. I would try.
If you care about your data you can adb pull in recovery to get stuff off your sdcard before you factory reset.

benjo22 said:
Yes, but I don't remember if I update the bootloader.
The choices I have are :
- Normal powerup
- Recovery
- Factory
- Barcodes
- BP Tools
- QCOM
Thank you for your help
Click to expand...
Click to collapse
What model phone do you have XT1092? Do you have the 5.0 system.img for your phone?

kcustom11 said:
You're not bricked then. I don't know what the recovery instructions are for the French model. Do they have factory images on the support page?
You can volume up on recovery to get into recovery to see options about clear cache and factory reset. Those might help, but I doubt it. I would try.
If you care about your data you can adb pull in recovery to get stuff off your sdcard before you factory reset.
Click to expand...
Click to collapse
I don't know if I they have the factory image. Cna you tell where I could get it ? (or where I need to search ?)
Actually, I have a back of my data so I don't care about it. So can you tell me how to use ADB in order to do a factory reset? (ADB is already installed)
JulesJam said:
What model phone do you have XT1092? Do you have the 5.0 system.img for your phone?
Click to expand...
Click to collapse
I think you're right and the French model is 1092 and not 1095 as I thought. But I don't have the system.img...

it looks like motorola didn't post images for models other than the PE xt1095. try the factory reset in recovery. if that doesn't work.
try this.
http://forum.xda-developers.com/mot...tory-image-android-5-0-lollipop-moto-t3001221

kcustom11 said:
it looks like motorola didn't post images for models other than the PE xt1095. try the factory reset in recovery. if that doesn't work.
try this.
http://forum.xda-developers.com/mot...tory-image-android-5-0-lollipop-moto-t3001221
Click to expand...
Click to collapse
Thank you, but in your opinion, there is no other way to fixe my problem ? I'm a little scared of flashing a new image, mainly because I'm not sur at 100% that it's a XT1092.

benjo22 said:
I think you're right and the French model is 1092 and not 1095 as I thought. But I don't have the system.img...
Click to expand...
Click to collapse
You should search for it online and post in the Motorola forums that their OTA messed up your system and ask them for the files. And email and chat and ask them that way too.
---------- Post added at 01:10 AM ---------- Previous post was at 01:09 AM ----------
benjo22 said:
Thank you, but in your opinion, there is no other way to fixe my problem ? I'm a little scared of flashing a new image, mainly because I'm not sur at 100% that it's a XT1092.
Click to expand...
Click to collapse
Put your phone in bootloader mode, connect to your computer and start Motorola Device Manager to see if MDM can repair your phone.

Go into recovery (volume up to select). Try a factory reset and clear the cache first. Attempt to reboot.
Then follow JulesJam advice and try MDM
In the bootloader, the bar code option will tell you your phone version to see if you have the XT1092 (volume up to select)
If that doesn't work, you'll have to go to the link I gave you and flash the 1092 images.
or send it back to motorola

kcustom11 said:
or send it back to motorola
Click to expand...
Click to collapse
I don't think that is how it works outside the US. I think they have to send it to service centers where they decide whether or not it is a warranty issue and if you have rooted or unlocked the bootloader, they refuse the warranty service. At least that is how it is in Brazil.
AFAIK, only the Pure Edition maintains its warranty if you unlock and root.
I know with my XT1096, the qe is now 1/1 after MoFo so I worry that I couldn't get warranty services for it. Good thing I have MotoCare and if I end up with a problem, I am just dropping it in a bucket of water so that it can't be turned on again and paying the $39 deductible.

I didn't say it was on warranty. That's why it should be the last option. I imagine Motorola owns the service centers so you would still be sending it to Motorola.
I wouldn't worry too much about flashing those images. It should work if nothing else does. I think there's also another forum about how to convert the 1092 to a 1095. You can do that if you really want the 5.1 right away. You have to be mindful of the radios though.

kcustom11 said:
I didn't say it was on warranty.
Click to expand...
Click to collapse
But if it isn't on warranty and you are not w/in the 14 day return period, then you have to pay for service.
---------- Post added at 02:31 AM ---------- Previous post was at 02:21 AM ----------
kcustom11 said:
I imagine Motorola owns the service centers so you would still be sending it to Motorola.
Click to expand...
Click to collapse
Idk but it didn't seem that way with the Brazilian phones but maybe.

JulesJam said:
But if it isn't on warranty and you are not w/in the 14 day return period, then you have to pay for service.
Click to expand...
Click to collapse
Obviously

Let me tell you first that it isn't bricked yet, This thing is happening only because you tried to update your device with a custom recovery, to solve the issue you have to go on stock recovery and on the stock Rom as well. That's it and it will work again..
But keep in mind never downgrade, i mean don't flash a lower Rom than what you are on right now otherwise it may surely result in a Bricked Phone:what:
Sent from my XT1052

kcustom11 said:
Obviously
Click to expand...
Click to collapse
well then I wouldn't advise sending it back, I would try to fix it myself since it is just software.
---------- Post added at 02:48 AM ---------- Previous post was at 02:47 AM ----------
vijayid_94 said:
Let me tell you first that it isn't bricked yet, This thing is happening only because you tried to update your device with a custom recovery, to solve the issue you have to go on stock recovery and on the stock Rom as well. That's it and it will work again..
But keep in mind never downgrade, i mean don't flash a lower Rom than what you are on right now otherwise it may surely result in a Bricked Phone:what:
Sent from my XT1052
Click to expand...
Click to collapse
The problems are when you try to downgrade the bootloader and/or partition table or when you downgrade after upgrading and then take an OTA.

Thanks to everyone !
I think that I will try to flash the image because using the MDM doesn't fix anything. But it was written that my current version is :"22.121.1.victara_oraeu.oraeuall.en.eu".
Furthemore, I had this problem when I was trying to install an update. Do you think it's a downgrade if I flash the available version of system.img ? And consequently I risk a real brick ?
Edit : an other question : on the tutorial that explain how to flash a img, it's written that we need to use "Motorola fastboot utility " and not the Android fastboot utility. I installed the sdk android and the MDM program, but the sole fastboot program a have is the android one. Do you know where I can find the Motorola fastboot utility ?
Thanks again )

Hi everyone !
Finally, I decided to launch the flash with the stock rom for XT1092. And it perfectly worked !
I still have a two questions :
- why I don't have anymore the update Moto proposed me at the benining ? Moreover the stock flashed seems to be an old one.
- In the futur, if a need to do an update, how can I do to avoid this problem ?
Thank you very much once again )

benjo22 said:
Hi everyone !
Finally, I decided to launch the flash with the stock rom for XT1092. And it perfectly worked !
I still have a two questions :
- why I don't have anymore the update Moto proposed me at the benining ? Moreover the stock flashed seems to be an old one.
- In the futur, if a need to do an update, how can I do to avoid this problem ?
Thank you very much once again )
Click to expand...
Click to collapse
What Android Version are you running - go to settings and find out the android version. Also, what bootloader version are you running - put the device in bootloader mode, it is a number beginning with a 60.

Note 4 SM-N910T that keeps getting stuck in a boot loop

So i purchased a Note 4 SM-N910T about a year ago. It worked fine but last month shortly after the 5.1.1 update I did it started randomly restarting for no reason. First i taught it was Snapchat because I red somewhere that there are camera problems, so I stopped using it. But it kept restarting even after that. From then I have made a factory and a master reset, rooted the phone and even installed CM 12. No mater what i do it keeps on restarting. The only way to get it out of the boot loop is to connect it to a charger that is not a fast charger. Then it starts charging and works normally and you can do everything normally. After you remove it from the charger it works as long as you do not use it. When you start using it and want to do something with it it starts restarting again. I hope somebody can help me fix this issue. I have noticed that connecting it to WIFI makes it 100% sure that it will restart any moment. If you leave it without WIFI as long as you do not do anything big it will not restart. For example I watched series on my phone I downloaded beforehand. I was able to go to the CM 12 file manager and change series for the duration of my bus drive and it has not reset yet and it has not been connected to a charger for around 12 hours already.
My last resort is to wait 3 hours for the stupid free 5.0.1 official firmware and flash it using the TWRP Recovery or Odin. If that does not work I would have t give it to a service. Any help will be greatly appreciated! Also a link to where I can download the 5.0.1 official firmware for free in normal speed will be of greatly appreciated as well!
Merry Christmas!

That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile

MisterCoolBeans said:
That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile
Click to expand...
Click to collapse
Do you have a link to where I could download that because all I found were sites where the free user speeds took 3 hours to download 1.5 GB?:crying:

Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!

MisterCoolBeans said:
Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!
Click to expand...
Click to collapse
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!

Lazarov987 said:
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!
Click to expand...
Click to collapse
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?

Lazarov987 said:
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?
Click to expand...
Click to collapse
If you flash the stock firmware it includes the baseband and modem

ShrekOpher said:
If you flash the stock firmware it includes the baseband and modem
Click to expand...
Click to collapse
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!

I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.

Lazarov987 said:
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!
Click to expand...
Click to collapse
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
jazzmachine said:
I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.
Click to expand...
Click to collapse
You may have messed up the partitions. There is a thread about the pit file you should check out.

ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
What thread is that and how do I find it? I mean I always checked that in Odin i never had Re-partition on.

ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..

Lazarov987 said:
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..
Click to expand...
Click to collapse
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.

ShrekOpher said:
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179

Ashwin Prabhunerurkar said:
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
Click to expand...
Click to collapse
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!

Lazarov987 said:
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!
Click to expand...
Click to collapse
Don't flash Canadian tar files
We are searching for the answer
Hope to come back to you with a solution

Try Odin flash back to stock.
@dannygoround

dannygoround said:
Try Odin flash back to stock.
@dannygoround
Click to expand...
Click to collapse
Doesnt work. Wont flash the stock rom. It says Fail(Auth)

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

Database Develop

welcome