Related
The problem: Overnight my Moto X (xt1056) went dark. Was 80%+ charged, woke up and dead as a door nail.
The day before I took 4.4.4 OTA, flashed TWRP, rooted, backed up the ROM. All turned out fine.
Now when it boots it gets about 80% of the way through the boot animation and then it goes black and nothing ever happens. So I went into recovery and attempted to flash my backup but it fails. NO!!! It says cannot mount \system. Now I cannot wipe anything and I can't mount anything and I cant flash any ROMs.
I have tried flashing back to stock using some unbricking articles, but they all result the same way.
I think I need to reflash the gpt.bin for 4.4.4, but I can't find one. I am open to any ideas, and let me know if you need any other info.
Thanks XDA community!
cnelson3225 said:
The problem: Overnight my Moto X (xt1060) went dark. Was 80%+ charged, woke up and dead as a door nail.
The day before I took 4.4.4 OTA, flashed TWRP, rooted, backed up the ROM. All turned out fine.
Now when it boots it gets about 80% of the way through the boot animation and then it goes black and nothing ever happens. So I went into recovery and attempted to flash my backup but it fails. NO!!! It says cannot mount \system. Now I cannot wipe anything and I can't mount anything and I cant flash any ROMs.
I have tried flashing back to stock using some unbricking articles, but they all result the same way.
I think I need to reflash the gpt.bin for 4.4.4, but I can't find one. I am open to any ideas, and let me know if you need any other info.
Thanks XDA community!
Click to expand...
Click to collapse
How about a standard RSD XML restore?
aviwdoowks said:
How about a standard RSD XML restore?
Click to expand...
Click to collapse
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
cnelson3225 said:
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
Click to expand...
Click to collapse
Did the OTA "take" bringing it to 444? So if you try 442 that would be a downgrade? Right. Try Rsd lite with 444 unmodified. Edit,
But you may have a brick due to the 442 flash.
cnelson3225 said:
I have tried RSD Lite... but with 4.4.2 not 4.4.4
Not sure what you mean by RSD XML...
Click to expand...
Click to collapse
You can't downgrade!!!! Never attempt to flash a previous version. Best/easiest way to BRICK your device!
He means using RSD Lite. But use the 4.4.4 SBF. Use this one: http://sbf.droid-developers.org/download.php?device=0&file=940
samwathegreat said:
You can't downgrade!!!! Never attempt to flash a previous version. Best/easiest way to BRICK your device!
He means using RSD Lite. But use the 4.4.4 SBF. Use this one:
Click to expand...
Click to collapse
Just to clarify, the ROM says VZW but this is Sprint, will it matter?
Are you xt1060 or Sprint? Yes it matters.
---------- Post added at 08:27 PM ---------- Previous post was at 08:24 PM ----------
Choose your phone
http://sbf.droid-developers.org/
cnelson3225 said:
Just to clarify, the ROM says VZW but this is Sprint, will it matter?
Click to expand...
Click to collapse
Yep, there IS NO Sprint XT1060.
All XT1060s are VERIZON. Big deal, and big difference. Your first post said you have an XT1060...........
You are in a tough situation if you are using a Sprint Device. The ONLY 4.4.4 SBF that has been released is for Verizon. You may have a brick for possibly weeks until the Sprint 4.4.4 SBF is released....
I don't think there is a 444 xt1056 XML ? There is a thread in the dev sec.
Edit but there is no firmware link- XML/Rsd file so you are stuck til a release is out.
samwathegreat said:
Yep, there IS NO Sprint XT1060.
All XT1060s are VERIZON. Big deal, and big difference. Your first post said you have an XT1060...........
You are in a tough situation if you are using a Sprint Device. The ONLY 4.4.4 SBF that has been released is for Verizon. You may have a brick for possibly weeks until the Sprint 4.4.4 SBF is released....
Click to expand...
Click to collapse
I apologize, it is xt1056 Sprint
http://forum.xda-developers.com/showpost.php?p=46834711&postcount=1
There is no solution here. You must wait for the official XML.
Let others note : do not downgrade. Which is what happened here. The borked OTA was just bad luck or an example of how things can go wrong. But the op would be stranded anyway with no XML to fix it yet. But He will not know til the XML comes.
aviwdoowks said:
http://forum.xda-developers.com/showpost.php?p=46834711&postcount=1
There is no solution here. You must wait for the official XML.
Let others note : do not downgrade. Which is what happened here. The borked OTA was just bad luck or an example of how things can go wrong. But the op would be stranded anyway with no XML to fix it yet. But He will not know til the XML comes.
Click to expand...
Click to collapse
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
cnelson3225 said:
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
Click to expand...
Click to collapse
Notice how 444 has no firmware button while the others do. Rsd can only flash firmware. Roms are flashed by custom recovery & they only touch boot, system, data & recovery. Rsd does much more. You have borked partitions that, hopefully, only firmware & RSD (or fastboot) can fix.
cnelson3225 said:
But there is a 4.4.4 ROM there, is that not what I want? I apologize for being such a noob but I don't know what the difference between a XML and SBF are? Well I know what an XML is... Just not in relation to my issue.
Click to expand...
Click to collapse
The "XML" is a file inside the SBF that instructs RSD Lite which operations to perform. For all practical purposes, they mean the same thing....
There is ONLY a 4.4.4 SBF for Verizon. You do not want to flash this to your sprint phone - most likely it will get no service.
I'm sorry that your phone is in a non-functional state, but it definitely sounds like you had modified something that caused the OTA update to go wrong. Unless you want to risk permanently bricking your phone, you will do this:
Put it in a drawer somewhere. Re-activate an old device to use in the meantime. Wait until the official 4.4.4 SBF is leaked for the Sprint XT1056 (could be tomorrow, could be next month - no one knows). When it is leaked and appears on the droid-developers site, you can ATTEMPT to flash it, and hopefully you will recover.
Bummer. Bad situation to be in....
aviwdoowks said:
Notice how 444 has no firmware button while the others do. Rsd can only flash firmware. Roms are flashed by custom recovery & they only touch boot, system, data & recovery. Rsd does much more. You have borked partitions that, hopefully, only firmware & RSD (or fastboot) can fix.
Click to expand...
Click to collapse
Oh I get it now! So now I need to hope someone releases the firmware and hope that when I flash it it fixes the problem. Right? lol
Of course the OTA (Blur.update.zip) needs an intact partition/phone structure to add on to so it is of no value now.
samwathegreat said:
The "XML" is a file inside the SBF that instructs RSD Lite which operations to perform. For all practical purposes, they mean the same thing....
There is ONLY a 4.4.4 SBF for Verizon. You do not want to flash this to your sprint phone - most likely it will get no service.
I'm sorry that your phone is in a non-functional state, but it definitely sounds like you had modified something that caused the OTA update to go wrong. Unless you want to risk permanently bricking your phone, you will do this:
Put it in a drawer somewhere. Re-activate an old device to use in the meantime. Wait until the official 4.4.4 SBF is leaked for the Sprint XT1056 (could be tomorrow, could be next month - no one knows). When it is leaked and appears on the droid-developers site, you can ATTEMPT to flash it, and hopefully you will recover.
Bummer. Bad situation to be in....
Click to expand...
Click to collapse
So if I flash VZW it will work but I won't have service? That would be great because I don't have service now! I was already waiting for Ting to whitelist the Moto X. So if I run that now, I can check back when (if) Ting opens up and perhaps the Sprint one is out. Right?
cnelson3225 said:
Oh ...
Click to expand...
Click to collapse
You risk loosing your imei or worst. If you find someone who has done it? Flashed Vzw to a sprint phone, testimony....
cnelson3225 said:
So if I flash VZW it will work but I won't have service? That would be great because I don't have service now! I was already waiting for Ting to whitelist the Moto X. So if I run that now, I can check back when (if) Ting opens up and perhaps the Sprint one is out. Right?
Click to expand...
Click to collapse
It isn't without risk....but another member says that he did it successfully. A member in my SIM-UNLOCK thread has flashed the VZW firmware to his Sprint Moto X. He did not lose the IMEI, and since he used my sim-unlock method, the phone works on any GSM carrier.
But DO NOT take this as me saying that you SHOULD do this, or that it is safe. I'm warning you that it COULD make your condition worse or could cause irreversible damage. I have NOT done this myself, and I would never recommend it.
It *Might* work for you, but *ONLY* if you have unlocked the bootloader, and its still quite risky. If you do it, you are doing it completely at your own risk - I'm not responsible for anything that goes wrong.
I understand. I already F'd up once by taking a risk, I think I learned my lesson. I will wait a bit for the Sprint firmware and if that pans out then I can rethink it.
So the Sprint ROMs page you linked me is the place to watch if it comes?
Hi, recently i managed to brick my Korean F340L G Flex so bad. I've tried almost everything software wise.
-The solution:
I'm planning to change the logic board from a Sprint LS995 model. I think it will work ok. Of course I'll have to some how get an unlock code in order to use it in Greece where I live.
I've seen in ebay some users providing for a small amount of money this code.
So, what do you think. Will it work as I'm thinking? Any comments, suggestions, guides welcome. Thanks
Here is a short story:
"Hello, to all, I'd like to share my experience and problem with my LG G Flex, as a last hope to find a solution to unbrick it.
I know that the talk here is about G2's, but I saw many users reviving their Flexes with OP's method.
So here is what I did in steps:
1)I rooted my Lg g flex F340L
2)New OTA, downloaded, but failed to install after reboot. The message was no OTAs for rooted devises
3)Tried to unroot, but with no success. Still no installation of OTA.
4)Found, and flashed the stock F340L rom , (had an EFS backup), from another user here(.tot file), with LGFlashTool.
5)SIM card was not recognized any more (Greece, Vodafone), so no calls. Did all the updates, but no SIM, still.
6)Hard reset, still no SIM.
7)Decided to flash stock F340K kdz rom, and install CWR. All good, SIM detected, OTA downloaded, but after reboot stuck at CWM nenu. Whatever I do just CWM.
8)No download mode, or usb support, just an LG FLEX unknown device. Got some drivers only to be seen as lenovo ADB device.
9)I found the test point on the motherboard and short circuit it. Got a qhsusb_bulk(qualcomm 9008) under COM ports, but not on a specific port.
10) No flash capability, and no partitions to try and flash the 10 or so, images. Ubundu, no luck with the partition detection either.
11)After many reboots and button long presses the CRW came back...again
Well as I can see, there is not so much support for the korean variants and I might have destroyed my phone. So, I need your advise in changing the motherboard. I found M/B's from AT&T and Sprint variants, to install to my F340L. I think it will work. After I will purchase an unlock code from lets say ebay to unlock it to all GSM networks ( I live in Greece).
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Alex_XV6700 said:
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Click to expand...
Click to collapse
Yes sorry, CWM I was refering to. Well, since I have no other option at the moment. I'll try to find that specific process you've mentioned when I get the board(help or hint welcome)
As, for the M/B change, no system partitions are recognized in order to flash individual .images to unlock them.
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Alex_XV6700 said:
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Click to expand...
Click to collapse
The only stock image I have is in .TOT file for the L variant. I also have stock .kdz file for the K variant. I can sideload to /sdcard/0/ directory only, if that helps. I'll try to find twrp.zip and try it. But the main problem is to find stock rom in .zip format.
I've managed to install twrp 2.8.0.0...
N3M3SYS said:
I've managed to install twrp 2.8.0.0...
Click to expand...
Click to collapse
Ok
now you could try to flash this rom.
let me know how it goes.
Alex_XV6700 said:
Ok
now you could try to flash this rom.
let me know how it goes.
Click to expand...
Click to collapse
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
N3M3SYS said:
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
Click to expand...
Click to collapse
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Alex_XV6700 said:
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Click to expand...
Click to collapse
That would be a miracle for me, I'll be waiting!
Q&A for Bootstack (KK and L) for L90
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Bootstack (KK and L) for L90. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
what can we do with bootstack ?
leandro_sousa said:
what can we do with bootstack ?
Click to expand...
Click to collapse
Bootstack is a bunch of files deep inside the phone. They are responsible for turning device ON and OFF, having SIM card support or download mode for flashing .kdz systems.
If you want to use stock KitKat or any customROM (KK or L) you need KitKat bootstack.
If you want to use stock Lollipop you need Lollipop bootstack.
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
grey heron said:
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
Click to expand...
Click to collapse
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Xemidra said:
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Click to expand...
Click to collapse
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
grey heron said:
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
Click to expand...
Click to collapse
I figured out that you meant baseband
It's not necessary to do a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Xemidra said:
I figured out that you meant baseband
It's not necessary to a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Click to expand...
Click to collapse
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
grey heron said:
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
Click to expand...
Click to collapse
It's for compatibility reasons. To make sure that everything is working fine I changed all files. It's less secure but more effective.
Hi Xemidra and everyone else.
I have used this for about 12-14 times now, going from stock LP to custom ROM and back, and as far as I Know it's working without any problems.
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Is it something that a ROM chef could do?? Or is this a CM thing???
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil??? Anybody know more about this??? I've tried searching for this article again, but couldn't find it. I use google, anybody know a better search engine for these type of querries?
grey heron said:
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Click to expand...
Click to collapse
Yes, it would be. You need to contact you ROM developer about this. I can't do anything about that.
Which bootstacks did you use ?
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil???
Click to expand...
Click to collapse
Maybe. I haven't head anything about that. No one complaint about quality of calls etc. I believe that different bootstacks for different variants are enough. Countrys from which I use the .kdz file to create bootstack are random.
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
---------- Post added at 11:45 AM ---------- Previous post was at 11:28 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
Hi,
Am on a d405N myself, but I would stick to the same version aboot as your firmware: D410 v20a fw >>>> D410_v20a_patched_aboot. Stick with what works.
I wouldn't use just any aboot version. It might work, but why take the chance?
If you can't find the D410_v20a_patched_aboot, consider upgrading your fw to v20b first. Firmware is a bit easier to find.
It would be even better to flash a d410 v10 kdz, aand use a d410 v10 aboot. This way you wouldn't have to worry about using bootstacks.
Hope this helps, and stop spamming.
Odd Report
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
dnuuk said:
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
Click to expand...
Click to collapse
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Xemidra said:
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Click to expand...
Click to collapse
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
dnuuk said:
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
Click to expand...
Click to collapse
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Xemidra said:
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Click to expand...
Click to collapse
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
dnuuk said:
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
Click to expand...
Click to collapse
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
dnuuk said:
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
Click to expand...
Click to collapse
Try to use LG Mobile Support Tool ? It always worked for me. Make sure you really have all the drivers installed.
It will flash the original .kdz meant for your phone.
Sorry for all the trouble I guess that the bootloader was locked ? or it needed to be unlocked using oem-unlocked feature.
Hi
i purchased p7 while ago and then while i search in the internet i find that there is many models of p7 and mine was p7-l11 and it's australian model but i'm not from australia
so this model seems that it doesn't receive any updates and it's still on EMUI 2.3 and probably will not get lolipop update also
is there a way to make it like global model (p7-l10 ) by install another ROM or something ? so it can receive the updates normally
thanks and sorry for my english.
omjo said:
Hi
i purchased p7 while ago and then while i search in the internet i find that there is many models of p7 and mine was p7-l11 and it's australian model but i'm not from australia
so this model seems that it doesn't receive any updates and it's still on EMUI 2.3 and probably will not get lolipop update also
is there a way to make it like global model (p7-l10 ) by install another ROM or something ? so it can receive the updates normally
thanks and sorry for my english.
Click to expand...
Click to collapse
You can flash the latest version manually, but I can't guarantee that you won't damage your device.
I think not much can go wrong as long as you don't change the kernel and have a backup of your current build (use CWM recovery > backup).
http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343
tinyXperia said:
You can flash the latest version manually, but I can't guarantee that you won't damage your device.
I think not much can go wrong as long as you don't change the kernel and have a backup of your current build (use CWM recovery > backup).
http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343
Click to expand...
Click to collapse
thanks for replay
but are you sure if i follow the steps correct it will work without any damage ?
because the phone is new and i dont' want lose it very fast
omjo said:
thanks for replay
but are you sure if i follow the steps correct it will work without any damage ?
because the phone is new and i dont' want lose it very fast
Click to expand...
Click to collapse
Probably only the CUST partition is different, but alas, there is no information whatsoever. If I'm not mistaken the Asian versions have the same hardware, so the number after the L should only mean that it's for another region, and that's all. There are a few ROMs made for the L01 here on the forum, and they are working on the L10, and vica versa. I'm pretty sure it wouldn't create hardware malfunction, so even if the software is buggy on the other variant if you have a backup, you can always flash the original.
First i would check if you have an unlocked bootloader .
When not unlock it by rooting with root genius.
The Kernel is for all models the same .
The different is the system , modem and cust partition.
So when you have one sim slot and one micro SD slot you can try it with the L-10 Software when you have dual-sim you have to try the China devices Software (L-5/7/9/0)
But i would recommend to flash a full update and not only the system partition
But flashing these Software from one on the other should not damege the device ..
But when you do this this youre deal, so don't blame me if something goes wrong...
Araca said:
First i would check if you have an unlocked bootloader .
When not unlock it by rooting with root genius.
The Kernel is for all models the same .
The different is the system , modem and cust partition.
So when you have one sim slot and one micro SD slot you can try it with the L-10 Software when you have dual-sim you have to try the China devices Software (L-5/7/9/0)
But i would recommend to flash a full update and not only the system partition
But flashing these Software from one on the other should not damege the device ..
But when you do this this youre deal, so don't blame me if something goes wrong...
Click to expand...
Click to collapse
i don't know if the bootloader unlocked or not , How could i know ?
i have one sim slot and one micro SD slot so it will be same as L-10 , so do i just follow the steps like in this link : http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343 ?
or should i do something before it ?
omjo said:
i don't know if the bootloader unlocked or not , How could i know ?
i have one sim slot and one micro SD slot so it will be same as L-10 , so do i just follow the steps like in this link : http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343 ?
or should i do something before it ?
Click to expand...
Click to collapse
If think your best bet is to ipdate with the three button method with the original bootloader and recovery. Download the full B609 ROM from here (click on Letöltés), put it in /sdcard0/dload (or on the SD card, doesn't matter), and update either through the system menu or by holding down all three buttons when booting. In case anything goes wrong (which it shouldn't), you can use the same method with the L11's ROM to downgrade.
g4b3rm4n said:
If think your best bet is to ipdate with the three button method with the original bootloader and recovery. Download the full B609 ROM from here, put it in /sdcard0/dload (or on the SD card, doesn't matter), and update either through the system menu or by holding down all three buttons when booting. In case anything goes wrong (which it shouldn't), you can use the same method with the L11's ROM to downgrade.
Click to expand...
Click to collapse
Thanks for reply
is that easy ? so i don't have to change anything like in the link ?
also i don't have L11's ROM and i didn't find it so is the backup will be enough if something wrong happen ?
omjo said:
Thanks for reply
is that easy ? so i don't have to change anything like in the link ?
also i don't have L11's ROM and i didn't find it so is the backup will be enough if something wrong happen ?
Click to expand...
Click to collapse
Updating to the official ROMs is easy since there is a force update option. In your case it will still work and most likely will not cause any harm.
But now that I think of it, if you want to make a backup, you're out of luck. Well, mostly.
If you'd like to create a backup, you'd have to
unlock bootloader / flash an unlocked bootloader
flash recovery
backup your current ROM
All of the above can be done but you cannot flash a B609 ROM on top of a B133 base - you'd have to update with the recovery and bootloader you just lost to make a backup. If you don't have the original ROM's files, you cannot go back if anything goes wrong.
To sum it up:
you can easily update
you (probably) cannot make a backup
Decide for yourself it it's worth the minimal risk.
g4b3rm4n said:
Updating to the official ROMs is easy since there is a force update option. In your case it will still work and most likely will not cause any harm.
But now that I think of it, if you want to make a backup, you're out of luck. Well, mostly.
If you'd like to create a backup, you'd have to
unlock bootloader / flash an unlocked bootloader
flash recovery
backup your current ROM
All of the above can be done but you cannot flash a B609 ROM on top of a B133 base - you'd have to update with the recovery and bootloader you just lost to make a backup. If you don't have the original ROM's files, you cannot go back if anything goes wrong.
To sum it up:
you can easily update
you (probably) cannot make a backup
Decide for yourself it it's worth the minimal risk.
Click to expand...
Click to collapse
mmm i don't know why i'm not comfortable with this ):
so you say that if i flash the ROM like in the link it will not make any difference and i will still lose my phone of something wrong happen ?
omjo said:
mmm i don't know why i'm not comfortable with this ):
so you say that if i flash the ROM like in the link it will not make any difference and i will still lose my phone of something wrong happen ?
Click to expand...
Click to collapse
Well, since the L11's number seems to come from only being sold in Australia, and no hardware differences, the update should go without a hitch. But we can never know since nobody reported anything about it.
Now, just to be clear - L10 users have flashed L01 custom ROMs, and there seems to be no problems apart from the ROMs' bugs.
My opinion is that there will be no problems, but I am no expert as I have never heard of the L11 variant.
g4b3rm4n said:
Well, since the L11's number seems to come from only being sold in Australia, and no hardware differences, the update should go without a hitch. But we can never know since nobody reported anything about it.
Now, just to be clear - L10 users have flashed L01 custom ROMs, and there seems to be no problems apart from the ROMs' bugs.
My opinion is that there will be no problems, but I am no expert as I have never heard of the L11 variant.
Click to expand...
Click to collapse
Ok i think i will wait for a while and see what to do
Thanks for your assistance
g4b3rm4n said:
Well, since the L11's number seems to come from only being sold in Australia, and no hardware differences, the update should go without a hitch. But we can never know since nobody reported anything about it.
Now, just to be clear - L10 users have flashed L01 custom ROMs, and there seems to be no problems apart from the ROMs' bugs.
My opinion is that there will be no problems, but I am no expert as I have never heard of the L11 variant.
Click to expand...
Click to collapse
Hello
could you see this link please : http://forum.xda-developers.com/ascend-p7/general/emui-3-0-b609-errors-vodafone-cust-p7-t3060527
it seems that he has the same problem but different country
he changes the CUST and then flash full version ROM
Do you think it is better if i do the same ?
omjo said:
Hello
could you see this link please : http://forum.xda-developers.com/ascend-p7/general/emui-3-0-b609-errors-vodafone-cust-p7-t3060527
it seems that he has the same problem but different country
he changes the CUST and then flash full version ROM
Do you think it is better if i do the same ?
Click to expand...
Click to collapse
Ah, didn't think about the CUST partition - but yes, this is probably the only difference between the submodels. I you want to make sure you can return, see if your L11 has an update.app for the CUST partition. I remember distantly flashing these when upgrading to B602 (the beta of 4.4) and now when updating to the Lollipo beta.
g4b3rm4n said:
Ah, didn't think about the CUST partition - but yes, this is probably the only difference between the submodels. I you want to make sure you can return, see if your L11 has an update.app for the CUST partition. I remember distantly flashing these when upgrading to B602 (the beta of 4.4) and now when updating to the Lollipo beta.
Click to expand...
Click to collapse
i'm not sure about update.app for the CUST but i find something maybe help
see this link the second file : http://asanfile.com/file?path=huawei/flash file/p series/p7-l11/android 4.4.2/
it has the same build number and same custom version of mine and it's from the same company (Optus) so it seems like it's the same ROM on my phone !
do you think it will help if something wrong happened and i can return with this ROM ?
omjo said:
i'm not sure about update.app for the CUST but i find something maybe help
see this link the second file : http://asanfile.com/file?path=huawei/flash file/p series/p7-l11/android 4.4.2/
it has the same build number and same custom version of mine and it's from the same company (Optus) so it seems like it's the same ROM on my phone !
do you think it will help if something wrong happened and i can return with this ROM ?
Click to expand...
Click to collapse
Yes, the second one seems to me like a complete package. Don't know how to unpack the update.app, so we can't be sure. There is a thread though with an almighty CUST partition, that might help you - also, if you change the CUST, you can surely flash the ROM that' bund to your new CUST - so I think if you flash the international CUST with the international 4.4 ROM, then you can go back to the international B133 if aníthing goes wrong. Make sure you make a note of everything in your system information menu before doing anything.
g4b3rm4n said:
Yes, the second one seems to me like a complete package. Don't know how to unpack the update.app, so we can't be sure. There is a thread though with an almighty CUST partition, that might help you - also, if you change the CUST, you can surely flash the ROM that' bund to your new CUST - so I think if you flash the international CUST with the international 4.4 ROM, then you can go back to the international B133 if aníthing goes wrong. Make sure you make a note of everything in your system information menu before doing anything.
Click to expand...
Click to collapse
when you click at the file it shows that there is update.app so i think that what you mean
so does the files in this link good : http://forum.xda-developers.com/ascend-p7/general/emui-3-0-b609-errors-vodafone-cust-p7-t3060527
or use another ?
and one last thing , in the link he put file to update to B133 before upgrade , should i use it or not ?
omjo said:
when you click at the file it shows that there is update.app so i think that what you mean
so does the files in this link good : http://forum.xda-developers.com/ascend-p7/general/emui-3-0-b609-errors-vodafone-cust-p7-t3060527
or use another ?
and one last thing , in the link he put file to update to B133 before upgrade , should i use it or not ?
Click to expand...
Click to collapse
Yes, you should first update to B133. Don't really know if it is necessary, mind you - but since that's the way he did it, I wouldn't wander off a beaten path The second step he makes is the update.app that modifies the CUST partition. If you flash that, I bet you can always roll back to B133 in the same thread.
g4b3rm4n said:
Yes, you should first update to B133. Don't really know if it is necessary, mind you - but since that's the way he did it, I wouldn't wander off a beaten path The second step he makes is the update.app that modifies the CUST partition. If you flash that, I bet you can always roll back to B133 in the same thread.
Click to expand...
Click to collapse
when i look to the build number it show : L11V100R001C00B133SP04
so it seems that i already have B133 ?!
and also link of B133 in the thread doesn't work anymore so i think i will just change the CUST and flash the ROM
omjo said:
when i look to the build number it show : L11V100R001C00B133SP04
so it seems that i already have B133 ?!
and also link of B133 in the thread doesn't work anymore so i think i will just change the CUST and flash the ROM
Click to expand...
Click to collapse
Good luck
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