Related
My phone is no longer capable of making a USB connection.
Now i want to revert it to stock, i thought i did so but it turns out the stock CWM rom I installed has some mods like root and busybox.
I was wondering if it is possible to flash an older stock rom through cwm and then have the phone auto update to the newest version? I also wonder if OTA updates update the baseband?
tetsuo55 said:
My phone is no longer capable of making a USB connection.
Now i want to revert it to stock, i thought i did so but it turns out the stock CWM rom I installed has some mods like root and busybox.
I was wondering if it is possible to flash an older stock rom through cwm and then have the phone auto update to the newest version? I also wonder if OTA updates update the baseband?
Click to expand...
Click to collapse
so your phone has a usb hardware malfunction\hardware problem and you need to send it to lg for repairs?
skylinegt77 said:
so your phone has a usb hardware malfunction\hardware problem and you need to send it to lg for repairs?
Click to expand...
Click to collapse
Thats what i think will happen, I want to fully revert to stock first though and check that.
You can use this
http://forum.xda-developers.com/showthread.php?t=1617458
Thou it won't be a clean stock and you probably need the stock kernel for your region to be inside or it can be seen.
If connecting the phone with the battery out, vol down pressed and it still doesn't change into the flash mode you can be sure the usb is dead. (provided the cable is 100% working)
it looks like that might work.
Do you know if Q is older than R and if my phone will auto-update to R?
Status update:
* Manually installed CWM using terminal
* Followed Kag's link and installed that ROM
Rom appears to be fully stock, but I'm not getting an OTA update to v20r.
I need to be on r because q was never officially released, at least not in my country so my phone should not have it.
Any ideas for getting it updated?
Try this thread : http://forum.xda-developers.com/showthread.php?t=1591801
nicorb said:
Try this thread : http://forum.xda-developers.com/showthread.php?t=1591801
Click to expand...
Click to collapse
That one has been hacked and rooted unfortunately
use version 20q the clean one you can find it in android development
tetsuo55 said:
That one has been hacked and rooted unfortunately
Click to expand...
Click to collapse
Oh ,ok then . Can try this one : http://forum.xda-developers.com/showthread.php?t=1609494 .
...And quiet an easy task too.
I managed to create 2 cmw zips myself together with the one posted here : http://forum.xda-developers.com/showthread.php?t=1621016 and been using ever since .
All credits go to the devs ofc.
My 2c
I used those links to flash 10a.
But it still says no OTA updates are available.
Could it be due to CWM?
tetsuo55 said:
I used those links to flash 10a.
But it still says no OTA updates are available.
Could it be due to CWM?
Click to expand...
Click to collapse
That should be due to LG server's load . Guess u could wait for it to appear, eventually, or just create a new 20R.
It looks like it's blocked on the software level and will only let you check once ever X period?
Its telling me that there is no update available without even trying to connect, the answer comes so fast.
Yes...i believe i once read about that somewhere in here.
Which baseband are you on now?
218
Thats a bugger..sorry .Dont think theres another way to update bb except from flashing.
About OTA ,doesnt work for any country.
Ill b checking on this one though as it interests me too.
Hello people.
With cwm it is possible to install futures firmwares from asus?
Thanks.
I think the answer is not right now. It's a one way street. But in the future(as you could do with the original tf101) using NVflash/APX mode. Correct me if I'm wrong. But there is Asus Stock rooted you can easily flash from cwm
It's easy enough to knock up a rooted Asus stock for people to flash. I'm not getting rid of the tab anytime soon
Oh someone was saying you could install stock with fastboot
YayYouFixedIt said:
Oh someone was saying you could install stock with fastboot
Click to expand...
Click to collapse
Yes you can do it that way as well if you want to lose recovery as well
Hey Xda,
Today I present you a guide on how to
REVERT TO STOCK OR REFLASH firmware on the Asus Zenfone 2 Laser ZE5550KL.
This guide is applicable to both types of users ie who use TWRP and who don't use TWRP.After following this guide your phone will also be unrooted.
For TWRP Users
Here I give you links to two firmwares which you can directly flash via TWRP recovery.
Version:1.13.40.496
Link
Version:1.17.40.1234
Link
For Stock/Non-TWRP Users
The procedure is a little long here ==>
1. Download the official firmware from asus website.
2. Copy the firmware to the Micro-SD and rename the file (firmware) by one more(version).This renaming should be according to your current firmware version.If you have 17.something firmware and you download 16.something firmware then rename the 16.x.x file to some thing like 17.x.x For eg. if you have 1.17.40.763 then rename 16.x.x file to 1.17.40.764.
3. Reboot the phone.Android should automatically find the update file and offer to automatically update the software.Do it !!
4. Go to stock Recovery and wipe cache , dalvik cache and data.
5. Reboot device. Your phone will now be unrooted(if it was rooted before).
DONT FORGET TO PRESS THE THANKS BUTTON IF I HELPED YOU.
CREDITS
CREDITS
@abhishekr700
@LuK1337
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
LuK1337 said:
@abhishekr700: You could atleast credit me for TWRP method. The zips you uploaded are obviously made using my guide.
Click to expand...
Click to collapse
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
abhishekr700 said:
Yes ofcourse,
Would you provide me links to your guide? @LuK1337
Click to expand...
Click to collapse
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
is it applicable for asus_z00LD
kris12344 said:
is it applicable for asus_z00LD
Click to expand...
Click to collapse
Yes
Sent from my C2305 using Tapatalk
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Lololololololo
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Does this work with zenfone500kl
LuK1337 said:
Lemme guess. You use that stupid custom kernel? That'd explain why About Phone says it's Z00LD.
Sent from my ASUS_Z00TD using XDA Labs
Click to expand...
Click to collapse
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Sent from my ASUS_Z00LD using Tapatalk
tmjm28 said:
Before going back to stock and re-rooting to see if the issue was still present, I thought I'd ask if this is something to worry about ? I have the ZE551KL (Z00T) and have been flashing for this device with no problems whatsoever. What is it that I did while unlocking , rooting, and flashing twrp that may explain why the build number and device model don't match? Additionally, at times my PC will recognize my device as a MotoG when my device is connected to the PC via USB . I don't have access to my PC right now so I can't say this with certainty, but I think my PC recognises my device as a MotoG only when the device is in TWRP.. Maybe that means something was done wrong while unlocking the bootloader?
Click to expand...
Click to collapse
This issue has been fixed on V4.0of kernel .
Hope you like it.
HampTheToker said:
Lololololololo
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
mohamedelkholy said:
Does this work with zenfone500kl
Click to expand...
Click to collapse
Yes
HampTheToker said:
Well, I'll be damned. I was doing so much flashing at the time that I didn't put it together. Oh well. I've been back on the stock CM kernel for days and everything finally works as it should again.
Click to expand...
Click to collapse
This issue has been fixed on V4.0 .
Hope you like it.
kunalchitara said:
Will flashing this stock ROM on TWRP replace my current TWRP recovery to stock recovery on boot?
Nope !
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
Hi
May I know if the above worked for downgrading from Marshmallow 6.0.1 back to Lollipop 5.x.x ??
Thanks
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13
- Thanks!
jasonshao88 said:
Man, so how should I do if I wanna flash back to LP and upgrade to MM?
The TWRP won't be replace to stock you said above.
I'm now using TWRP and CM13 and stock LP firmware.
- Thanks!
Click to expand...
Click to collapse
How can you use cm13 and stock lp together?
This is for reverting to stock nothing else.
Sent from my C2305 using Tapatalk
.
will get updates again if i flash this? tnx
My friend I installed TWRP and accidently deleted all android system. . . Now only appears the TWRP .... How to do reinstall android 5.0 system ??
hi
I have rooted my ze550kl and unrooted it through su iam not able to install ota updates i have twrp i want removery twrp and install stock rom to get ota updates but i cant find recovery img for my firmware
Can u please provied recovery.img,boot.img,bootdriod.img files for ww.1.17.40.1234 firmware for my asus zenfone2 laser ze550kl
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