Related
Alright guys i have searched and tried and tried. Currently i am on dj11 with kernal version stated as 2.6.32.9 and right below it has [email protected]#3. I am on 2.2
So what ive tried:
-I used heimdall to flash back to stock but as you can see the kernal version says im still rooted although superuser app is not installed. This causes the update to fail
-I tried to use superoneclick method to unroot but it does not work
What i want is to be stock with no root and be able to update. Any help or suggestions would be appreciated.
FYI i also used all the thread procedures on the forum (gizmo ninja and how to unbrick tab)
Try using this stock unrooted rom. Link below:
http://forum.xda-developers.com/showthread.php?t=1136587
TabFreak said:
Try using this stock unrooted rom. Link below:
http://forum.xda-developers.com/showthread.php?t=1136587
Click to expand...
Click to collapse
i believe i tried that already and it still had the words "rooted" under the kernal version. It also didnt allow me to update. I will try it again.
Try this instead.
http://forum.xda-developers.com/showthread.php?t=1033586
The second link takes you to the files.
TabFreak said:
Try this instead.
http://forum.xda-developers.com/showthread.php?t=1033586
The second link takes you to the files.
Click to expand...
Click to collapse
Will try now. Ahh I hope this works!
killerapl said:
Will try now. Ahh I hope this works!
Click to expand...
Click to collapse
Flashed and guess what?? Didnt work. Kernal version still says 2.6.32.9 [email protected] Ugh!!!
Don't know what the problem could be. That has always worked for me. If you go to the "System-- About Device-- System Updates" does it give you the option to update? When I have restocked mine and set up a wireless connection it always tries to download and install the update.
TabFreak said:
Don't know what the problem could be. That has always worked for me. If you go to the "System-- About Device-- System Updates" does it give you the option to update? When I have restocked mine and set up a wireless connection it always tries to download and install the update.
Click to expand...
Click to collapse
Yeah it does. Goes halfway and then stops and has exclamation mark. I tried gizmoninjas method to update but still quits. I'm totally lost.
Sent from my SCH-I510 using XDA App
I don't know what to do. If it were me I would go ahead and grab the EC02 update from here: http://www.blackmugmedia.com/Android/GT/Mirror/Roms/CDMA/Recovery to Stock /
Flash that. You will have the latest official release, or you could get the VZW Leaked Gingerbread release from the Developers section. (That is what I am running on my VZW tab).
Maybe if you flashed the EC02 update and then used the going back to stock instructions it would unroot you. I have always unrooted using that rom and directions when I wanted to start fresh from a custom rom that didn't quite work like I wanted it to work.
TabFreak said:
I don't know what to do. If it were me I would go ahead and grab the EC02 update from here: http://www.blackmugmedia.com/Android/GT/Mirror/Roms/CDMA/Recovery to Stock /
Flash that. You will have the latest official release, or you could get the VZW Leaked Gingerbread release from the Developers section. (That is what I am running on my VZW tab).
Maybe if you flashed the EC02 update and then used the going back to stock instructions it would unroot you. I have always unrooted using that rom and directions when I wanted to start fresh from a custom rom that didn't quite work like I wanted it to work.
Click to expand...
Click to collapse
I will give that a shot. The current gb leak is rooted. I did post asking to see if they (oldmacnut) had the unrooted version. Personally I like the rooted option but I do want to sell the tab and can't sell it rooted unless the person doesn't care. Bedside this issue the tab is fine and working properly.
Thank you so much for all your help. I will keeep you posted on the outcome.
Nope didn't work. Still rooted. I'm so over this hahah
Sent from my SCH-I510 using XDA App
I am at a loss. I know there are ways to get this done, but I have no idea where you can go from here. Not an expert, sorry!
TabFreak said:
I am at a loss. I know there are ways to get this done, but I have no idea where you can go from here. Not an expert, sorry!
Click to expand...
Click to collapse
There has to be. Wish it was like my Droid charge and just flash via Odin. If I can get the ginerbreak leak with no root I will be happy.
Or sell it to someone that doesn't mind its rooted.
Sent from my SCH-I510 using XDA App
There is a unrooted version of Gingerbread that you can flash with Odin:
http://www.mydroidworld.com/forums/...w-sprint-2-3-4-ef01-rooted-updated8-15-a.html
I haven't used Odin, but if you are familiar with it you might have luck with this. I think you use 7zip to extract and then use the resulting md5 file in the One Package location. You might want to look there and get that file.
TabFreak said:
There is a unrooted version of Gingerbread that you can flash with Odin:
http://www.mydroidworld.com/forums/...w-sprint-2-3-4-ef01-rooted-updated8-15-a.html
I haven't used Odin, but if you are familiar with it you might have luck with this. I think you use 7zip to extract and then use the resulting md5 file in the One Package location. You might want to look there and get that file.[/QU
I'm gonna give it a try tomorrow. I just have to make sure if I flash under phone or PDA with Odin. Don't know if you know. For phones its PDA. Not sure with tabs. Thank you so much
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
I just tried this.
Unzip the .md5 file with 7zip, you will get an error about no proper ending or something. Take your zimage, cache, param, dbdata, factoryfs, recovery.bin and place them in the proper locations in Heimdall. Flash your tab and let it boot up.
You should have a fully functional gingerbread without root.
I just did it on my tab.
TabFreak said:
I just tried this.
Unzip the .md5 file with 7zip, you will get an error about no proper ending or something. Take your zimage, cache, param, dbdata, factoryfs, recovery.bin and place them in the proper locations in Heimdall. Flash your tab and let it boot up.
You should have a fully functional gingerbread without root.
I just did it on my tab.
Click to expand...
Click to collapse
You effin rock!!! It worked! I now have non rooted stock gingerbread. Thank you for all your help and investigation for the right files. Youre awesome. Now time to sell this baby
Or i spent so much time doing this i think im attached now hahaha
Glad it worked the way you wanted. I went back to the rooted version of Gingerbread. Everything works the way I want it to so no reason to change (for now anyway).
I didn't flash these files because I'm running hyperdrive and I like my set up. Whoever uses these odin files can let everyone know if they're 100% working or if they have any problems.
https://docs.google.com/uc?id=0B6Lj6PgrbSjibXdaTFlRSWw4NVk&export=download
dkeepitabuck said:
I didn't flash these files because I'm running hyperdrive and I like my set up. Whoever uses these odin files can let everyone know if they're 100% working or if they have any problems.
https://docs.google.com/uc?id=0B6Lj6PgrbSjibXdaTFlRSWw4NVk&export=download
Click to expand...
Click to collapse
Where did you find these because I posted these a little earlier than your post same exact file name?
http://forum.xda-developers.com/galaxy-s4-active/help/link-to-sgh-i537-stock-4-4-odin-files-t2823709
dynamiclynk said:
Where did you find these because I posted these a little earlier than your post same exact file name?
http://forum.xda-developers.com/galaxy-s4-active/help/link-to-sgh-i537-stock-4-4-odin-files-t2823709
Click to expand...
Click to collapse
It's a coincidence that we had the same files. Well my friend Dung (pronounced Young) sent me a link through my email.
Confirmed
Just recovered from a soft brick with them. phone working fine
YAY 4.4 ODIN!!!
firestorm942 said:
Just recovered from a soft brick with them. phone working fine
YAY 4.4 ODIN!!!
Click to expand...
Click to collapse
Nice! :good:
Worked with no problems!
Flashed all 4 files using Odin 3.07 over stock, unrooted, NC9 OTA , which in turn I had flashed over stock, unrooted, ML2 through stock recovery. I had used the same Odin 3.07 to flash ML2 over MF3 (which came with the phone).
I had rooted the MF3 and installed Safestrap on it at some point. Once I decided a couple of days ago to try to upgrade all the way to NE3, I uninstalled Safestrap, all other programs I had installed and unrooted with SuperSu and did a factory reset in preparation for the ML2 flash with Odin (the phone still said custom when it booted after that, but once I flashed the ML2 Odin files, the phone was back to the stock boot animation).
I actually was stuck on the stock, unrooted, NC9 yesterday because after trying to flash the NE3 OTA through the stock recovery, the OTA seemed to be applied, but upon reboot the phone was still at NC9? And today, the solution! Thanks to all involved!:good:
By the way, I checked my knox counter when I entered Download (Odin) Mode before I flashed NE3 and it was at 0x0, so it seems that neither rooting nor installing Safestrap on MF3 changed the knox counter to 0x1
Next step, root with Towelroot, see how that goes (Thank you Geohot!):good:
flashed successfully from nc9. working phone, data, GPS and camera.
Can anybody who has successfully flashed this package post the MD5 for the zip file? I want to make sure people are not trying to flash a corrupt file.
Devo7v said:
Can anybody who has successfully flashed this package post the MD5 for the zip file? I want to make sure people are not trying to flash a corrupt file.
Click to expand...
Click to collapse
If you tell me how get the MD5 from it, I'll give it a try.
Devo7v said:
Can anybody who has successfully flashed this package post the MD5 for the zip file? I want to make sure people are not trying to flash a corrupt file.
Click to expand...
Click to collapse
I found a program by the name of MD5 Checker V4.0.0. This is the MD5 that it gave me: 59E84894B0C760E21955F1194392E61A
this porgram for android phones md5
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
tet1 said:
this porgram for android phones md5
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
If your question was about my last post where I posted the MD5 for the SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip file that I got using the program Checker V4.0.0.? The program is a Windows program, not an Android App.
yes I know that windows program and I said md5 file for android Samsung phobes not program app ... and the odin files 4.4.2 NE3 worked good without problems
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
gcam1964 said:
59E84894B0C760E21955F1194392E61A
Click to expand...
Click to collapse
59e84894b0c760e21955f1194392e61a confirmed using Microsoft File Checksum Integrity Verifier v2.05
OK, I'm in over my head I have i537ucucne3. I flashed s5 conversion v5+ deodex_me. I'm a noob and I didn't make a back up first. Now I just want to get back to stock. If I flash the firmware in this thread, will that put me back to stock? Any help is much appreciated , please, and thank you.
jeffrausa said:
OK, I'm in over my head I have i537ucucne3. I flashed s5 conversion v5+ deodex_me. I'm a noob and I didn't make a back up first. Now I just want to get back to stock. If I flash the firmware in this thread, will that put me back to stock? Any help is much appreciated , please, and thank you.
Click to expand...
Click to collapse
Yeah, if you flash this firmware you will be completely stock. It week completely wipe your phone and you will have to reroot.
Awesome, thank you much for the reply.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Wait. . Do I flash with safestrap, or do I need to use odin
Sent from my SAMSUNG-SGH-I537 using Tapatalk
I figured it out. Flashed the files with odin. It's running great. thanks again for the help. You guys are geniuses.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Hello, friends, but when I flash the firmware, Odin says fail ? Please help MEEEEE !
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Matthew98405 said:
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Click to expand...
Click to collapse
First off you need to give more info about your phone. What build are you on 5.0, 4.4.4 etc. How did you get on that build. Ota update or custom update. We can't really help you unless we know what your running.
dirtydodge said:
First off you need to give more info about your phone. What build are you on 5.0, 4.4.4 etc. How did you get on that build. Ota update or custom update. We can't really help you unless we know what your running.
Click to expand...
Click to collapse
I had 5.0 via OTA
Matthew98405 said:
I had 5.0 via OTA
Click to expand...
Click to collapse
I'll search and see what I can find. Try searching for the OC4 firmware. if I find something i'll post it here
Matthew98405 said:
Help me XDA, you're my only hope!
In attempt to flash a custom recovery to my AT&T Galaxy S5 (SM-G900A), odin failed to flash it. After a while, I tried to root my phone after other forums/threads said I needed to. I tried towelroot, didn't work for $#!t. And the point of no return came when another forum said to flash a custom firmware to help TR, so I did. It failed. Then I decided to give up, but it got stuck in a bootloop, well, if you consider attempting to boot, giving up, and rebooting itself into bootloader a bootloop. And that was followed by attempting to flash stock firmware, which odin couldn't do anything. So, I've tried everything:
Kies won't detect my phone, or it will say it's unsupported
Odin must be broken or my phone is f***ed, because almost immediately, odin will say FAIL
Anti-Virus has been disabled this whole time
So if anyone reading this knows what they're doing, please help me out with this.
Click to expand...
Click to collapse
if you can go into download mode then don't worry you can download another official firmware & flash it.
The firmware you tried & failed may be corrupt file so download new one & try.
Make sure your battery is more than 50%.if not know the battery level do not flash go to repair centre.
Sent from my SM-G900H using xda Forum
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
You can try this. Make sure you are using Odin 3.09. You will need the OC4 stock partitions located at the bottom of the first post. That might work.
I just thought of this, does it matter what cable I use?
(Galaxy S5 USB 3.0 cable or standard micro USB)
Because I just used a regular cable and it worked!
Matthew98405 said:
I just thought of this, does it matter what cable I use?
(Galaxy S5 USB 3.0 cable or standard micro USB)
Click to expand...
Click to collapse
It don't matter. As long as Itty is a good working cable
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Matthew98405 said:
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Click to expand...
Click to collapse
So your back up and running now?
dirtydodge said:
So your back up and running now?
Click to expand...
Click to collapse
Yup, and I restored everything!
Any idea why odin kept failing to flash a custom recovery?
Matthew98405 said:
Yup, and I restored everything!
Any idea why odin kept failing to flash a custom recovery?
Click to expand...
Click to collapse
Because your running 5.0 ota. You can't root that version yet plus they only custom recovery that we have on the AT&T S5 is either safestrap or Flashfire which is still in testing faze. You'll need to wait til you can root the ota 5.0 since it has different bootloader.
Ok, thanks, so I can stop messing up my phone.
Matthew98405 said:
Wait, now it's stuck on the AT&T logo.
Yay, I'm in
Now restoring
Click to expand...
Click to collapse
How did you get it to restore? Im stuck at a soft brick on my s5 at&t with the 5.0 ota bootloader. Please help
---------- Post added at 07:48 AM ---------- Previous post was at 07:12 AM ----------
Matthew98405 said:
I had 5.0 via OTA
Click to expand...
Click to collapse
If u need help i found solution of the same problem. lemme know if u do
sir i have tried to downgrade my galaxy s5 at&t by odin
but odin fails and i,m still stuck on firmware error ..
what i can i do?
shreesam09 said:
sir i have tried to downgrade my galaxy s5 at&t by odin
but odin fails and i,m still stuck on firmware error ..
what i can i do?
Click to expand...
Click to collapse
What firmware were you on originally? Sounds like you we're on 5.0 or above . If so you will have to flash a pure stock rom of the same back to it . And no rooting for any thing above 4.4.4
Sent from my SM-G900F using XDA-Developers mobile app
I woke up and my phone had a message saying it was ready to update to N910TUVS2EQE2. Has anybody updated and rooted this fw yet?
I also recieved the update, I won't update for that reason. But the notification is annoying.
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Unless T-Mobile has suddenly reversed a long-standing policy and locked the bootloader on a previously unlocked device (something I have not ever heard of for any device), you can still flash TWRP recovery from Odin and then flash SuperSU from recovery, which does not modify the system partition. This should just be a minor security update for Marshmallow and not an update to Nougat, which would have much bigger compatibility consequences but which should still be rootable by the above method.
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Would be great if we could get a nougat release.
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
It is annoying as F!!!!! Every 6 hrs or so it nags the F!!!! outa you!
m4f1050 said:
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
Click to expand...
Click to collapse
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
Ok thanks.
t-mobile SM-910T
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
where could I get the QE2 file?
Lsanc1170 said:
where could I get the QE2 file?
Click to expand...
Click to collapse
Not going to say what others say all the time, but I searched for it. (I Googled it.) If you want to easily root it and already have TWRP recovery, go to this post:
https://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
If you want the ODIN version, go to this link:
https://samsunggalaxyrom.com/2017/0...sm-n910t-n910tuvs2eqe2-marshmallow-6-0-1.html
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
what is Smores Rom? what MM base does it use and what are it's features?
slaapliedje said:
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Click to expand...
Click to collapse
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
anyone getting better or worse signal with the QE2? .... feedback?
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
jnyfive said:
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
Click to expand...
Click to collapse
It was the USB cable. Tried different cable and port. Tada.
f4phantomii said:
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
Click to expand...
Click to collapse
That did seem to help, and oddly enough one of the watch faces I'd bought that wouldn't install now installs and works fine.
jnyfive said:
It was the USB cable. Tried different cable and port. Tada.
Click to expand...
Click to collapse
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
jnyfive said:
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
XeoNoX said:
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
Click to expand...
Click to collapse
TMO Note 4, baseband version N910TUVS2EQE2, tried lineage-14.1-20170725-UNOFFICIAL-trltetmo.zip and RR-N-v5.8.2-20170303-trltexx-Official.zip
Sent from my SM-G955U using Tapatalk
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