Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
KiD3991 said:
Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
Click to expand...
Click to collapse
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
SimonTS said:
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
edit:
Figured out how to enter download mode... haha
Will keep Continue my effort!
I've gone through hell Unlocking Sensation XE, 4X wont beat me!
SimonTS said:
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
KiD3991 said:
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
Click to expand...
Click to collapse
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
SimonTS said:
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
Click to expand...
Click to collapse
Via LG mobile supporter I'm installing 20a or something. Then I will redo it. Thanks for your effort in helping. Hahaha. :good:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
henning_ said:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
Click to expand...
Click to collapse
Download this...
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g930be6d.zip
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
henning_ said:
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
Click to expand...
Click to collapse
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
MrMike2182 said:
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
Click to expand...
Click to collapse
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
henning_ said:
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
Click to expand...
Click to collapse
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
MrMike2182 said:
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
Click to expand...
Click to collapse
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
henning_ said:
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
Click to expand...
Click to collapse
Glad you got it fixed because I couldn't find anything for you about the RUU for 64 bit... So I was pretty sure you could fix it by rooting it!
I need the stock recovery image (from 23.16.3.victara_retca.retca.en.CA) so I can flash the 6.0 update since it won't work with TWRP.
Any help? Google isn't providing me with much.
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
I have no clue. I doubt it would have to be the retCA version. I'm sure everything besides radio and system will be the same.
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
Gus.Ottawa said:
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Thank you both! I'll play around with these files and make it work
DonDizzurp said:
Thank you both! I'll play around with these files and make it work
Click to expand...
Click to collapse
Any update on whether this worked for you? I'm in the same boat
jullyfush said:
Any update on whether this worked for you? I'm in the same boat
Click to expand...
Click to collapse
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
DonDizzurp said:
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
Click to expand...
Click to collapse
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
jullyfush said:
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
Click to expand...
Click to collapse
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
DonDizzurp said:
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Click to expand...
Click to collapse
Something odd has happened since upgrading to 6.0.
'adb devices' still sees my phone, but 'fastboot devices' no longer sees anything, and making a desktop back-up with adb now creates a file containing 0 bytes.
Everything else seems fine. Are there some new permissions I need to give before this will work?
Thanks again.
Edit: I managed to get fastboot working, however now I've run into a new problem.
To confirm, when you say flash the cracked boot.img for Marshmallow, I should execute 'fastboot flash boot boot.img' for the cracked boot.img?
I'm getting the error: mismatched partition size (boot)
I can still enter TWRP with fastboot, but it's not permanent without the cracked boot.img
Am I missing a step?
Edit #2: Finally got TWRP to stick another way and have root now. Thanks for everything!
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
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