I just wanted to split this discussion from the leaked ROM thread. From what I have gathered and understand, this newest update is the US equivalent of the Europe 2.51 update. I know many of you have already upgraded your devices to this, so users like me who are late/slow to the game, aren't there yet. In my case I still had the stock 3.6.160 up until last night. I know many have had the concern about 2.51 and not being able to go back. Has US TMobile done us a favor by releasing this OTA update? It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated. It also seems that if the US and Europe version are the same, any thing that works for 2.51, would work for the US version. Like the 3.4.2 Nandroid backups. It should just be a matter of a simple restore and everything should work, correct? Sorry if I seem a little off. Prior to this device all of mine have been HTC devices which didn't have the locked bootloader. So this concept of of firmware/roms is a little off to me. I haven't had a chance to test any of this yet, I just want to know if the theory is correct. If I'm wrong please point me in the right direction. I'd like to be able to contribute to this forum constructively, especially as I am in charge of deploying DEFYs on our corporate network. The nice part of this is my Director is all for rooting our phones. He looks at in the manner that we need to do what needs to be done. If a phone gets bricked in the process, well we will just buy another. Warranty really isn't a concern.I'd like to get playing on it this weekend, especially with Froyo.
runeblade said:
It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated.
Click to expand...
Click to collapse
Nope.
The only update for the US DEFY is an incremental one (still 2.1) and it has only been released to 500 or so users according to the offical Tmo forums.
They are testing that one now.
The official froyo for DEFY is probably still a couple/few months away from public release, but let us hope they get it out faster.
More info in this thread:
http://forum.xda-developers.com/showthread.php?t=931212
The Incremental has been released to the wild. Both of my Defy's received it OTA. I also know this is not an OS upgrade. Still stuck at 2.1. But my understanding was that the US update changes the boot loader to the same one as the Europe 2.51 update. If this is indeed true it would mean that we should be able to boot any of the 2.2 Roms out there without using the European update. Thats what I'm trying to confirm/Deny.
I registered for the "testing update", and received it this morning. Overall the phone is so much smoother. I'm now using Blur instead of ADW or LP. As a matter of fact all scrolling is smoother. The homescreens, app drawer, lock screen, widgets. Everything. Before the update if I was on Wi-Fi and sent a MMS I would get a delay, and have both icons in the notification bar for Wi-Fi and 3G, but now they send instantly, and I only have the Wi-Fi icon. Battery seems to be lasting longer today too which is one of the included functions. I'm impressed overall with what they did.
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
darknetone said:
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
Click to expand...
Click to collapse
I noticed the same thing. No more root access after the update. I tried to re-root with z4root, super 1 click to no avail. Not familiar with the ADB process. Kinda nervous to be honest. First Android phone and all. Had it 2 weeks. Hopefully a new 1 click method comes from one smarter than I soon.
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
runeblade said:
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
Click to expand...
Click to collapse
Did you need to do anything special with Super1click, or was it as simple as z4root? Can you just run it, and wait for it to finish? I mean I read some stuff that you may need to do the "turn debug off, turn it on, turn it off" thing with it because some phones give a "waiting for device". If you did certain steps other than just clicking root can you share? Thanks.
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
runeblade said:
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
Click to expand...
Click to collapse
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Mine as well. Just keeps saying waiting. It got further once but stuck in a loop and came back to waiting. I unmount the sd, put it in debug, not sure what usb mode to use or where this admin option is found though. Quite frustrated since the bloatware I froze with Titanium Backup is back and all my root permissions are one. Any help for a newAndroid guy would be awesome.
Make sure when you have it connected to your machine that you are in Portal mode, as well as making sure that your machine is actually picking up the MDB interface. I know with mine it took a couple of plug ins to get it to actually install correctly.
bobbyphoenix said:
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Click to expand...
Click to collapse
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
This is based on the assumption you are using windows 7 or vista. You right click on the program and in the drop down menu select Run as Administrator. It will then open up the program.
slipknotfn said:
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
Click to expand...
Click to collapse
Exactly, "Head Honcho of the computer"! Do what runeblade said.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Yep. That was my problem. Didn't have it in portal mode. As soon as I did, it went fast. It went through a bunch of steps. I see it says "Running psneuter... ROOTED" It should be almost done. It's on "Reading OS Version properties..." now, and it's been there for like 10 minutes now.
cargohook said:
Exactly, "Head Honcho of the computer"! Do what runeblade said.
Click to expand...
Click to collapse
What if one were running, say, XP? Then head honcho would work? I have no computer here that has 7 or Vista. Just my old, trusty laptop. Thanks for all your help.
And which version of S1C? The one for 2.51 or the 1.63 version?
The 2.51 version.
runeblade said:
The 2.51 version.
Click to expand...
Click to collapse
where is that version? I'm using 1.6.3 and it's still stuck on "reading OS" thing.
Hi guys,
I am having a nightmare finding the developer options on my tab S 8.4 (SM-T705). I have enabled it by pressing build number 7 times and had the pop up stating that it is enabled, yet I cannot for the life of me find the menu. Does anybody have any idea where I am going wrong?
Thanks in advance
general tab... before the about menu... try reboot your device
edan1979 said:
general tab... before the about menu... try reboot your device
Click to expand...
Click to collapse
Thanks for your reply
It's really weird because it is not there. That is where it is found on my phone and my old tab 3 but it's nowhere to be seen on the Tab S.
I have rebooted and it's still not there. I have also tried to enable again by pressing build number 7 times but I get a pop up saying "no need, developer mode has already been enabled." I even factory reset to see if that would sort it but still the same thing.
hmmm.. back to the drawing board i reckon..
Were you able to solve this? im having the same problems
It's a firmware base issue.
Update manually using Odin T705XXUX1ANJ3 (Russian CSC) and "hey presto".
Download from sammobile or samsung-updates
My phone is a Redmi Note 5 Pro (whyred), 3GB RAM model, running MIUI Global9.5.19.0(OEMIMIFA). I already waited the 360H requested but still I can't unlock it.
Most of the times I get a (-1) error, others I get a chinese error, either at 99% or 50% but, when I don't get any of these, the message I get says my account can't unlock this device which doesn't make sense, I already connected that account on the phone, went on developer settings and enabled USB Debugging and OEM Unlocking, and added my account in Mi Unlock State. Also I connected to the Mi Cloud and made sure everything was synced. Any ideas?
A big thanks in advance.
Screenshots: https://imgur.com/a/V7eVL1I
EDIT: Solved the problem, just tried on another computer and voilà, problem solved
are u sure drivers are installed properly and hope ur internet is fast and stable
frankyval said:
are u sure drivers are installed properly and hope ur internet is fast and stable
Click to expand...
Click to collapse
Yeah drivers work just fine my phone gets detected and all that, the main thing I think is the fact that it says the account isn't allowed to do such!
Hi everyone, anyone know how to enable the device encryption with the lock screen password? There's no that option in settings.
Looking for a solution , someone say to use a strong lock screen password and that option will appear.
Not work.
Others say to enable the voice from developer option, and is no working even this, there's no such option in developer settings.
Any chance to get FDE working or I have to give the phone back?
Thanks
Edit: I call the Xiaomi customer care, I have no word, never seen something like this. They say isn't exist the FDE. If you want to full secure this phone you need to unlock and root the phone losing the warranty. Else you can keep your damn unsecure phone as you buy...wtf unbelievable I give the phone back today
If you're running Android 10, full disk encryption is not available anymore and file based encryption is used instead:
Since I cannot post links here, you can read about it at: source [dot] Android [dot] com /security /encryption
I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!
nevertechdose said:
I bought this phone from second hand, and sadly it had been officially updated to the latest Oreo firmware (A720FXXU9CSKA) so I'm now stuck with binary 9.
I have tried every and each method to enable OEM unlock in my dev options (date trick, MiracleBox and z3x procedures) to no avail :/
I was wondering if I'm really screwed up or if anyone can help me or if anyone has OEM unlocked with binary 9. Thanks for any info!
Click to expand...
Click to collapse
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
matkali said:
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
That's the date trick I was trying to refer to. Have tried it a few times but not working for me
It finally worked!
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...
nevertechdose said:
Dear lord, I'm finally on Lineage OS. My life is complete now!
I found some steps here. In summary, flashing latest firmware for your binary and then following the steps (verbatim) included in the link did the trick for me. It looks like the date trick works but you need to first set it 10 days behind, then after first reboot set it 10 days ahead, and after the other reboot add it up to 8 days.
After that if you don't see OEM unlock under developer options, give it a day or so and it will eventually show up! By the way, the steps were shared by the user "nacho2018" so make sure to check that info out.
I'm so freaking happy right now lol hope this helps somebody. I really had lost any hope; this is surely the hardest Android device I have ever worked on...
Click to expand...
Click to collapse
can you explain in more details!
matkali said:
can you explain in more details!
Click to expand...
Click to collapse
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
You can find out what bl/modem rev you have by checking the current build number of your current rom. Let's take A520FXXU7CRL8 - in this build number 7 is the revision, leave other numbers and letters for some other time. To be able to flash older firmware it must be same revision, or odin will fail. Search on the firmware related websites for older fw of your phone/region that has that same revision. So for the device mentioned before A520FXXU7CRHA is the oldest fw that can be flashed.
Click to expand...
Click to collapse
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.
Thanks
nevertechdose said:
For this to work, you must flash the oldest firmware available for your binary version through ODIN.
IMPORTANT: Make sure your SIM card is not inserted before flashing firmware.
How do I know what's my binary version?
Answer below, quoted from a post by @corsicanu on his RMM state issue thread:
Once the firmware has been flashed, follow these steps:
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later)
Enable developer options and disable automatic system updates from there
Connect to a WiFi network and go to software update under settings and disable automatic software update
Go to date and time settings and select for the time to be set manually. Set the date to be 10 days BEHIND from your current date
Go to developer options and turn it off (click on the right top corner toggle)
Now go to software update and check for a manual update, after result is shown restart your device. IMPORTANT: After the phone has rebooted, your date and time should be reset to the current time automatically
Go to date and time again but this time set it to be 10 days AHEAD, then check for software update one more time and reboot once finished
After reboot, go to date and time and add 8 more days AHEAD (you should be 18 days ahead of your actual date at this point) and perform a software update check once again and restart your phone
As a last step after the final reboot, enable developer options again and OEM unlock should be available!
If this didn't work for you at first try, wait a day or two for the toggle to show up. If you still don't see OEM unlock after those 48 hours, start over and try again.
Click to expand...
Click to collapse
Firmware in newer or older
---------- Post added at 06:55 PM ---------- Previous post was at 06:22 PM ----------
The first time you ask to delay 10 days and the second time to delay it again for another 10 days.
step 6- time does not reset to current time automatically
drjis said:
step 6- time does not reset to current time automatically
Click to expand...
Click to collapse
didnt for me either..