Related
Did anyone update to the new 2.3.3 firmware for UK or the USA yet?
Can you create and upload the ftf files please?
A few days ago I updated my firmware to v2.3.3 but now it is full with Chinese apps again and no Google apps installed at all. I don't know what other way there would be to remove the Asian apps and install all the Google goodies.
HK
http://u.115.com/file/clwlnrqu
Global
http://u.115.com/file/e60c0hcd#
BTW,I don't test the ftf.
I'm waiting for rooted rom.
Thank you so much Froce !!!!!!
It worked like a charm!
I've updated my phone with the "Global" firmware.
-----
For anyone who wonders how to update the phone with this firmware:
Before you start be aware that all your information stored on your phone (except for SDCARD) wil be wiped. The apps that you have installed will be gone, your message history will be erased, your contacts (unless synched with Google account) will be gone too.
And... like froce wrote... the ROM is not rooted.
As far as I know there'e no rooted 2.3.3 (3.0.1.A.0.145) out yet. For those that need a rooted F/W. Please go to Bin4ry's post [How-to] Root your Arc (Xperia NEO file included) for a 2.3.2 (3.0.A.2.181) F/W. Also that F/W worked like a charm on my Neo.
Software preparation
Download and install Sony's Update Service. I needed this to install drivers that later on are necessary.
http://www.sonyericsson.com/cws/sup...updateservice/1.349192/xperia-neo?cc=gb&lc=en
Download and extract X10flashtool. This is the program that you need to install the .ftf firmware images. To be able to install the ftf firmware images it needs to connect to the phone through the drivers that you just installed with Sony's Update Service program
Find the download link for Flashtool in: (I used v0.2.9.1 Beta)
[TOOL] [UPDATE 22/03/2011] Flashtool BETA version 0.2.9.1
Copy the firmware image into flashtool's "firmwares" folder. This folder should have been created when you extracted the flashtool archive
Phone preparation
Enable "USB debugging"
Switch off your phone
Connect the USB cable to either your phone or to your computer but not to both yet.
Flashing
Start Flashtool (administrator rights necessary)
press "Flash" button. You should get a new window that shows the device type and firmware content
press "OK" button. A new windows should appear that is asking you to connect your phone. Don't connect yet.
hold down the "back" button on your phone and keep it holding down while connecting your phone to your computer
the window should disappear and flashing should start.
release the "back" key that you were still holding down and sit back, relax and wait.
after flashing is complete, the text message window should say "now unplug the device and power it on". That's it.
Firmware details:
Global firmware came installed with:
Sony apps: Timescape, Music, Gallery, Calendar, Support, Synch, TrackID, Postcard, Media Server, PlayNow Store, FM Radio, Clock, LiveWare manager
Google apps: Market, Facebook, Maps, Gmail, Talk, Navigation, Places, Lattitude, YouTube, News&Weather, Google Search, Voice Search
Other apps: Lets Golf, Media Discovery, NeoReader, UEFA.com, OfficeSuite, Hanashi
For the Global Firmware, where do you go on the page to download the file? I've put it through Google translate, and when I go to the box beside file size, I'm prompted to download and run 115br_u1.exe. Is it safe and/or the proper download method? Thanks in advance!
Sorry,I forgot that is a Chinese web space.
I upload it to mutliupload.
http://www.multiupload.com/FI7016ZECR
Can the UK FW be installed in a Rogers LT15A Arc? And is this FW a generic one, no brand?
Thanks
This is a neo thread,not arc.
I think that froce's Global firmware is unbranded as inside build.prop:
ro.semc.version.fs=WORLD-1-8
If you can install Neo firmware on an Arc? I don't know. Why would you want to do that if there's more Arc firmware copies available than there are Neo copies.
So no one is able to make a rooted and updated IMG for the Neo, even with the FTF file? It's fustrating. I flashed the 2.3.3 rooted ARC firmware and it works, but I have to turn "auto rotate" screen off, so stop the screen going mental. Apart from that phone is much faster and responsive.
Weird. No problems here with the screen. Works as normal on my phone.
Yeah, wish the firmware was rooted too. I wish I could 'patch' the firmware myself to get root. If anyone would explain how to do that then I'd do it .
Ask for tester.
Please tell me the result.
neo global rooted img.
http://www.multiupload.com/T0FNM2L0EC
This rooted img is ok.
Thanks
Can I use this rooted image for unrooted 2.3.3 HK version?
Worked fine here on my Neo! I flashed from the ARC firmware. Thanks so much!
Yes It works!
ERM, i update to 2.3.3 from SONY update service, if i apply the root version, is it mean i need to unlock the bootloader?
Installed and rooted on my Neo (HK 2.3.3) without data loss.
Yes, unlocked BL is required with cleaning of every data.
Hi, can anyone explain to me why there are some SE apps which keep on coming back even after uninstalling? I'm talking about the infamous Hanashi, Neoreader, and UEFA.com apps...
In the firmware that came with my device (Netherlands) they were not there, but the global has them. I tried removing them but even after uninstalling with TitaniumBackup they come back at some point. Also Hanashi seems to eat up some memory all the time!
Tnx!
bassie112 said:
Hi, can anyone explain to me why there are some SE apps which keep on coming back even after uninstalling? I'm talking about the infamous Hanashi, Neoreader, and UEFA.com apps...
In the firmware that came with my device (Netherlands) they were not there, but the global has them. I tried removing them but even after uninstalling with TitaniumBackup they come back at some point. Also Hanashi seems to eat up some memory all the time!
Tnx!
Click to expand...
Click to collapse
Maybe because the old f/w wasn't deleted. Yesterday I flashed the rooted ROM and I came to find out that all apps and settings were left untouched. The ROM that I had on my Neo before flashing the rooted version was the same version (2.3.3) but unrooted.
If you don't mind then you could try flashing the old ROM first (2.3.2). The link is in one of the replies in the top of this post. Maybe that will delete the old apps (and all your settings and contacts too). After that flash the 2.3.3 version.
I'm unsure if it will help but maybe it is worth a try
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.
I have a S4 SM-S975L from Straight Talk laying around. It was my wife's phone before I convinced her to switch to Tmo with a S7.
I would like to know if its possible to install firmware for the T-Mobile SGH-M919 on to the SM-S975L
THANKS!!!!
If the model # is identified in the ST phone as the sm-s975L, a stock m919 ROM from sammobile.com can't be flashed to the phone.
@audit13 Well in the about device its says sm-s975L, BUT if connected to a PC while in TWRP recovery it shows as SGH-M919
The real model # is found in download mode, not in the ROM settings.
Ok. Just checked that. It shows sm-s975L
What options do I have with this phone???
I'm not familiar with the phone but if it has a locked bootloader, there is not much you can do in terms of custom roms.
[No message]
You will need to unlock the phone the easiest root for this phone is Towel root. TowelRoot is an APK that you install directly to the phone from the web, and it roots the phone without help from the computer. So if you want root access on the SM-S975L, TowelRoot is the way to go.
First you’ll need to allow 3rd party apps to be installed. To do this, go into settings, tap “More” in the top right, select “Security” and check the box next to “Unknown Sources”. This will popup a warning message, just tap “OK”.
Then, on your phone, go to https://towelroot.com/
Click on the lamda icon in the middle of the page, and this should download the APK file to your phone.
Run the application. You may receive a warning about it trying to violate certain security policies, but that’s sorta the whole point, isn’t it? Just acknowledge the error and continue.
The process should complete and notify you that the SM-S975L has been rooted. If your phone reboots, something went wrong.
sorry guys Magisk currently does not pass safetynet checks (24-06-2017) so this guide is a bit out of date but you can still use it, I will make another guide for this once magisk v13 comes out and fixes this problem
Hi guys! just a quick guide on how to install magisk, re-enable use of Samsung Health, and pass SafetyNet and be play store certified.
This guide will be pretty brief as i don't have the time or commitment to do an in-depth guide and I believe if you are here that you should know what you are doing (if anyone wants to make this in-depth, please be my guest).
this guide is for people who have tripped knox and still want to use s health while still getting the most out of their phone
You will need:
Odin:
https://www.androidfilehost.com/?fid=529152257862705230
TWRP for your device (you should be able to find guides with the download link)(you should also flash back to complete stock if you are already rooted to avoid any problems with previous roots)
no-verity-no-encrypt_ashyx.zip:
https://www.androidfilehost.com/?fid=24591000424951049
Magisk v12.0:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now that you have those 4 files we can start.
Skip steps 1-6 if you already have root and only wish to use samsung health
1. put magisk v12.0 and dm-verity patch onto the sdcard in the phone
2. flash TWRP using odin
3. boot into recovery and swipe to allow modifications.
4. under wipe there should be a button to format data (its in the bottom right). you will need to do this to flash magisk and dm verity.
5. flash Magisk and THEN dm verity
6a. boot into phone and complete setup to get to home page.
6b. download any systemless root app that you want (adaway works you just have to turn on systemless host files in magisk settings + viper4andriod has a module in magisk that you download for it to work)
(DO NOT TURN ON HIDE MAGISK UNTIL THE END)
7. download the app buildprop editor, open it and grant it root. search for the line ro.config.tima=1 and change the value from 1 to 0.
8. reboot the phone and you should now be able to use s health.
continue following if you wish to pass safetynet and be playstore certified (set up your root apps like viper and adaway before doing this)
9. go into magisk settings and enable the setting Magisk Hide. reboot phone. check that you pass safetynet in magisk manager after booting up again
10. go into app manager, find google play store, tap storage and then clear the data.
11. open app again and you should be certified. (this took me a few tries. not sure if it was play store needing to update the property or me needing to reboot the phone)
12. Yay! your device should now be able to pass safetynet and will be play store certified in the play store app. you should soon be able to see netflix in the play store again.
source: I done this on my a520 just on the weekend to be able to update netflix
I'll try this next update, thnx!
Does this require an external sd card?
korwynkim said:
Does this require an external sd card?
Click to expand...
Click to collapse
Yes i believe so, although I have never tried doing it without
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse
oh i did not know that it supported it already so maybe its not? not sure, try it out and see what happens?
the config change make it so that the rom thinks you still have knox enabled to you are able to use samsung health still (it got a "security update" that makes it so that phones with knox tripped will not be able to use it)
Good to know ! Thank so much !
But what's the real possibilities of this recent "magisk" ?
It can root with systemless ?
And in theory with systemless-root ,that don't trip the knox and we can use all apps and full hardware ....because it consider that the system is safe and untouched ===> i'm truth or wrong ?
Loulou-13 said:
And in theory with systemless-root ,that don't trip the knox...
Click to expand...
Click to collapse
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.
reayard said:
According to some other threads (and if I remember correctly from my own experience with the S7) Knox gets triggered as soon as you flash a custom recovery.
A positive effect of Magisk vs. SuperSU could be that system updates are still possible as the system partition is still unchanged. On the other hand the custom recovery will most probably cause the update to fail.
What seems to make Magisk superior to SuperSU is MagiskHide so that the system appears to be unchanged for PlayStore and apps using SafetyNet.
Click to expand...
Click to collapse
Thank so much for sharing Samsung experience
Before i have had olds goods samsung fully customised ! It was funny before ,at this time ....and then always have had LG phones and just an unlock of bootloader+Systemless root din't have problem at all (full playstore&experience)
Now with the samsung evolution and my new A5 ,i don't want at all loose OTA updates,knox flag.... and all functions+playstore as you have said . And magisk is recent...
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....
Loulou-13 said:
I want to be sure at 100....0000% that "magisk" systemless root doesn't affect anything .
i'm not interested at all by TWRP ...completely useless until there eventually have "real" customs developments and many things can be flashed by flashfire,flashify....
Click to expand...
Click to collapse
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.
reayard said:
I doubt that FlashFire or Flashify can flash anything without root. The website of FlashFire for example says "FlashFire is the most advanced on-device firmware flasher available for rooted Android devices.". And the same for Flashify: [APP][4.0+][ROOT] Flashify.
Click to expand...
Click to collapse
Yes yes....sure...i didn't have precised...
Root with a method who din't need twrp and don't touch samsung things....and then flash what we want with these apps ...
Hi, Im XxViRUsPRO.
1.You Need Magisk Manager (Removed Form PlayStore) So this is the Download Link https://mega.nz/#!olRzFRTZ!eNOb6yVtvsAlb3V8sIOaRRfsHtQG952_WU--3TCDvck
2.To Use S Health On Rooted Phone You Need To Edit /System/Build.prop
and Change ro.config.tima=1 to ro.config.tima=0 using (Es File Explorer or Root Browser)
safety net check does not pass in Samsung galaxy a5 2015
What is this dm verity and for encryption? I have the latest magisk and i see those options in my magisk manager but donot know its utilization! and probably for the same reason my safety net check does not pass in Samsung galaxy a5 2015
reayard said:
According to the XDA page of Magisk it already supports dm-verity and forceencrypt. So is the separate download of no-verity-no-encrypt_ashyx.zip still necessary?
Edit: What does the change " ro.config.tima=0" do?
Click to expand...
Click to collapse
Dis any one could enable the fm chip in nougat once rooted ,in Canada Samsung disable the fm chip and i would get it back
why does flashing magisk wipes all user data including internal storage?
Samsung A5 sm-a500f
Global Update is there.
For those who installed it already, give us some feedback.. and one question, should factory rested be done before or after installing update? What is better, because i never did reset before, just apply update, but now would like to do reset also..
Works fine without reset. Smartphone was very hot during update. After installation I made a reboot. All Apps are working and Dark Mode is now available for most Apps.
This update broke my GooglePay, no longer passing ctsProfile in safetynet.
Seems to work fine. Before this update I was getting more and more bugs, but they seem to be gone now. Rebooting after the update took a long time, however. I was stuck on the Mix logo for 5-10 minutes.
There are some visual tweaks here and there, but that's all I can notice.
Themes available, region uk!
Latest update has caused my home launcher to crash. Am only able to use it cause of 3rd party launcher.
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
*update*
I had an out of date version of exposed installed that caused boot loop.
I can't install work email, and because my phone is CN region, of course, Google Pay not working. Not sure if boot options for the kernel changed, going to look and see if I need to update my flashable patcher zip.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Yes...work perfectly.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Not with the latest stable version. Take a look here so solve your problem: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Anybody found a solution for viper4android? I tried rootless 2.7 but driver will not install.
Quality_con_troll said:
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Click to expand...
Click to collapse
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
spyke180 said:
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
Click to expand...
Click to collapse
Just went through this process myself and came back here now to report on it.
This was my process for anyone also looking for guidance.
This will work for the new android 10 updated. I came from MIUI10 (10.0.3.2.0) using system update to go to MIUI11 and android 10 (11.0.3.0) via OTA update, which reverted to stock recovery and obviously lost root as well.
1. Saved most recent twrp 3.3.1-7-recovery.img for perseus by mauronofrio found in these XDA threads, magisk 20.3.zip found on magisk site and repository, and just to be sure disable forced encryption-treble.zip (just search for it) to my phone AND adb directory on Windows 10 computer.
ENSURE USB IS PLUGGED INTO 2.0 or 2.0 COMPATABILE HUB (Flashing recovery failed when connected to a USB3.0 port) and ADB/FASTBOOT is installed on your computer.
2. Booted into fastboot. (Power + Volume down)
3. Ran cmd.exe and entered "cd C:/(wherever you installed/platform-tools" without quotes.
4. Entered "fastboot devices" to ensure fastboot is connected. It should show device_id# and fastboot next to that.
5. Flashed TWRP3.3.1-7 for MiMix3 perseus (latest unofficial TWRP) by entering "fastboot flash recovery twrp3.3.1-7-recovery.img"
6. Entered "fastboot reboot recovery" the phone will reboot now, ENSURE YOU HOLD VOL+ ASAP or you will lose TWRP with stock recovery.
7. After booting into TWRP, entered password, wiped data and cache only.
8. In TWRP go to install and choose your disable_forced_encryption-treble.zip and flash it but do not select reboot device, it is selected by default.
(NOTE: Don't know if #8 is a necessary step especially for Global devices but did it anyways and it didn't hurt anything)
9. Go to install again and choose magisk20.3.zip, this time you can select reboot device.
10. After completing android setup download magisk manager 7.5.1 from play store and verify 20.3 is installed, if it is then congrats, you're rooted.
That's it! Like the above post said ctsProfile is reading false meaning you most likely will not be able to use Pay apps like Google Pay, etc.
Other apps that use google play services for verification may not work as well like Pokemon GO, Mario Kart, Harry Potter, or other banking/security apps. (Not sure about this one yet, try MagiskHide in the manager. Spyke180 is reporting above they do not work currently.) So if you can't live without Samsung Pay, or one of these games wait until a ctsProfile:true/SafetyNet passes solution is available.
Hopefully the next magisk update or someone in the community will be able to solve these issues in a timely manner, shouldn't be much of a wait.
Hope this made sense and can help some peeps out there perhaps.
CTSProfile is failing on my device as well. I tried using the boot cmdline patcher I made and it's still failing. I am wondering if Xiaomi released this update before getting the fingerprint in the CTS approved list. I can't think of anything else. My device is a CN device, so the BL is unlocked. I don't know if flashing Magisk with CN device and Global software still results in a boot loop but may try it.
Also, Magisk is detected through some methodology. I read all the posts made in both the release and beta threads in the last 3 days and it seems broken for everyone.
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
siuyan187 said:
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
Click to expand...
Click to collapse
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
spyke180 said:
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
Click to expand...
Click to collapse
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
siuyan187 said:
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
Click to expand...
Click to collapse
I see.
If you're rooted, you could try using the systemize module to make it a system app.
I verified my Google Messages and its notifications are working for me, even with both Wi-Fi and mobile data turned off.