Related
Here's the zip of the OTA that was pushed out. It won't install through either CWM or TWRP, so can someone who's more knowledgeable in these matters make it flashable?
https://dl.dropboxusercontent.com/u/821854/OTAPkg.zip
And in case it helps, here's the log from CWM from trying to flash it manually:
https://dl.dropboxusercontent.com/u/821854/recovery.log
And yes, as with any OTA, you run the risk of losing root, etc. But for me, I really don't care. I've even tried pushing the included stock recovery, but it doesn't work like this. You get a phone with an exclamation point over it (I'm sure you all know what I'm talking about) when you try to boot into that recovery. A quick push of TWRP back onto the phone fixed that error, but I still can't flash the update, obviously. Anyone want to take a crack at it?
Thanks to nuclear_eclipse for getting this and the log for us!
chrisliphart said:
I've even tried pushing the included stock recovery, but it doesn't work like this. You get a phone with an exclamation point over it (I'm sure you all know what I'm talking about) when you try to boot into that recovery.
Click to expand...
Click to collapse
That symbol just means that it doesn't know what file to use for the update; this is part of what get's communicated somehow from the OS to the recovery during reboot, but I'm not familiar enough with the way recoveries work to know how to trigger that myself. I would assume this is a similar mechanism to how ROM Manager et al can tell CWM/TWRP what to flash.
nuclear_eclipse said:
That symbol just means that it doesn't know what file to use for the update; this is part of what get's communicated somehow from the OS to the recovery during reboot, but I'm not familiar enough with the way recoveries work to know how to trigger that myself. I would assume this is a similar mechanism to how ROM Manager et al can tell CWM/TWRP what to flash.
Click to expand...
Click to collapse
That makes total sense. I guess it's not automatically checking the folder that Software Update puts it in. I've got another 22 hours until I can get Software Update to check again. I'll push the stock recovery before I do that, unless someone makes this flashable through TWRP or CWM before then.
In my stock Rom thread there are new files up. They are the ota roms. So if you are running stock, download the odex one ending in 1.08 and flash in recovery, no need to wipe data. Then pull boot.img and fastboot flash it. You now have the ota software. I will post instructions to upgrade the firmware that came with the ota
Sent from my M7 using xda premium
jmz said:
In my stock Rom thread there are new files up. They are the ota roms. So if you are running stock, download the odex one ending in 1.08 and flash in recovery, no need to wipe data. Then pull boot.img and fastboot flash it. You now have the ota software. I will post instructions to upgrade the firmware that came with the ota
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Rooted and all! Thank you sir!
OTA wich version
Does anyone use it, what does it include, will upgrade to jelly bean 4.2 or will stay on 4.1 I mean it was posted but no one actually tell us what to do with that?
henry_acevedo said:
Does anyone use it, what does it include, will upgrade to jelly bean 4.2 or will stay on 4.1 I mean it was posted but no one actually tell us what to do with that?
Click to expand...
Click to collapse
Its just a hboot patch I think. No serious software update. So yes still android 4.1
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Its just a hboot patch I think. No serious software update. So yes still android 4.1
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will be ever get Jelly Bean 4.2 or kit kat.. not even a decent rom is out there, i really want to know how to port but i don't know, why android cannot be be like windows ahahaah, download drivers for internet and taran,,,:crying:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
tinodevoe said:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
Click to expand...
Click to collapse
can you take a screenshot of the 6616 screen? and can you go to the firmware by customization thread and follow the instructions? what is your cust.# ?
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
I think you can flash c6606 Software without problems... Maybe even of C6603 via Flashtool.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
OK, that is really very strange. You could try to contact DoomLord or Apollo89, they have knowledge of such things.
Are you rooted? Can you do a CWM Backup? I suggest having a full backup before flashing another rom. So in case you need it, you can flash it back.
I am not sure if you have the same kernel as the rest of us. If you can not do a CWM backup, and are not rooted, you need to find a way to extract the file "boot.img" from the phone. This is the kernel, which you can easily flash back. But for this operation, a bootloader unlock will most probably be necessary.
If you can get no help from Doom or Apollo and can not extract boot.img, you might need to flash hoping for luck, or stay on the firmware you have.
Disclaimer: I might be much too paranoid, after all your phone seems to have the same hardware as the normal one, and a flash of a 10.4.B.0.569 ROM should be no problem. I just don't want to be the one that did not warn you and be responsable for a broken phone...
===============================================================
EDIT: Just had a look at the thread, C6616 is bell Canada, if you had found that, you could have reported back and told us that you solved the problem.
===============================================================
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
tinodevoe said:
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
Click to expand...
Click to collapse
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
N1k0la89 said:
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
Click to expand...
Click to collapse
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
tinodevoe said:
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
Click to expand...
Click to collapse
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
akisg said:
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
Click to expand...
Click to collapse
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
tinodevoe said:
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
Click to expand...
Click to collapse
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
akisg said:
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
Click to expand...
Click to collapse
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
tinodevoe said:
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
Click to expand...
Click to collapse
As soon you are installing a stock rom, you don't have to worry about root.
But if you wanna root, your only choice is to flash a 4.2 rom, root it with a method of your choice and then upgrade to a prerooted 4.3.
Can someone please point me in the right direction to a FW that works with my phone? the only one that I seem to be able to use with flashtool is this one here which is 4.1.2. http://forum.xda-developers.com/showthread.php?t=2390178
however it won't let me update the system!
I'm guessing that I need a C6616 firmware to make this work, but I also tried this one, http://forum.xda-developers.com/showthread.php?t=2612159 and I get an error in flashtools, in red writing 'ERROR - error flashing. Aborted'.
I've been searching on here and all the other firmwares are 6603 which I tried a couple and again errors in flashtools.
trying again with that 4.1.2 its flashing it but its not the firmware I need!
ok, finally got one of them to work! I'm not sure what it was but I downloaded a bunch of firmwares until one of them finally updated me to 4.3.
thanks for all the help!
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
Hi all,
I've Z1 which is not used in last 2 years. It has dirty unicorns 9.something, unlocked bootloader and root.
My Nexus 6p is giving troubles so I need to use Z1, I was wondering is there an active ROM right now or devs moved away from Z1 (I ask this cause most of the threads in original development seems to suggest that). I normally don't use ROMs from Android development since I've already deleted those DRM keys and stock drivers/firmware won't be useful (I looked in there as well though, and see only lineage active but the dev doesn't have display anymore)
I'll check AOSP branch from Sony itself until then thought I might as well ask the community.
Thanks
wis3m0nkey said:
Hi all,
I've Z1 which is not used in last 2 years. It has dirty unicorns 9.something, unlocked bootloader and root.
My Nexus 6p is giving troubles so I need to use Z1, I was wondering is there an active ROM right now or devs moved away from Z1 (I ask this cause most of the threads in original development seems to suggest that). I normally don't use ROMs from Android development since I've already deleted those DRM keys and stock drivers/firmware won't be useful (I looked in there as well though, and see only lineage active but the dev doesn't have display anymore)
I'll check AOSP branch from Sony itself until then thought I might as well ask the community.
Thanks
Click to expand...
Click to collapse
Carbon Rom is the only one active right now which is only for Security updates (they're working on Oreo that's why) and they might update faster if a there's a new vulnerability to fix.
AbduSharif20 said:
Carbon Rom is the only one active right now which is only for Security updates (they're working on Oreo that's why) and they might update faster if a there's a new vulnerability to fix.
Click to expand...
Click to collapse
Awesome thanks.
I tried the ROM, does it remove TWRP on flash? (I will ask this in ROM thread I guess)
wis3m0nkey said:
Awesome thanks.
I tried the ROM, does it remove TWRP on flash? (I will ask this in ROM thread I guess)
Click to expand...
Click to collapse
It does not overwrite recovery.
Twrp is there after you flashed the rom. If the recovery disappears just flash it from fastboot again
SUPERUSER said:
It does not overwrite recovery.
Twrp is there after you flashed the rom. If the recovery disappears just flash it from fastboot again
Click to expand...
Click to collapse
I did and then I can't boot in ROM
wis3m0nkey said:
I did and then I can't boot in ROM
Click to expand...
Click to collapse
may i ask what you did?
Flashed something in fastboot?
SUPERUSER said:
may i ask what you did?
Flashed something in fastboot?
Click to expand...
Click to collapse
I think I figured out my mistake.
I flashed TWRP with fastboot flash boot instead of fastboot flash recovery so it was giving me single use TWRP and so on.
Thanks a lot
wis3m0nkey said:
I think I figured out my mistake.
I flashed TWRP with fastboot flash boot instead of fastboot flash recovery so it was giving me single use TWRP and so on.
Thanks a lot
Click to expand...
Click to collapse
yes I figure it was it
This command sends and boots the image you specify to the device.
Similar to live booting a live linux dist
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