Related
I have a Advent Tegra Note 7
Upgraded to kitkat and OTA 2.4.1
Used Tomsgt supertool 2.4.1 tool to root, installed TWRP (and made a backup image of my freshly installed system)
I've since added some games and apps and spent a fair bit of time customizing the system, but when I attempt to run Titanium Backup it tells freezes when "asking for root rights" so I ran "root checker basic" from playstore, which tells me I don't appear to have proper root access..
Here's a break down of what I've done, I've tried to keep it conscise...
I have tried installing a SuperSU, SuperUser and SU Update fixer, Also reinstalling the SuperSU-v1.94.zip using both cwm and twrp... Still no proper root access.
Ideally I'd like to try some other things to get root access before reflashing and having to reinstall my apps and settings, can anyone help or suggest anything else I could do.? I can't think of anything I could of accidentally done to break root access, this is still quite a clean system just setup in the past two days.
P.S.When using the supertool impacter tool and scan for usb driver I get a "no such device" error, even though the device is listed in the previous screens.. also I suspect the correct drivers are there as ADB seems to work fine
they flashing SuperSU-v1.99r4.zip from http://download.chainfire.eu/447/SuperSU/. I haven't had issues with root via either method.
If that fails you can use the n7root.img which is downloadable here: https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true then go into fastboot mode and then type fastboot boot root_tn7.img. DO NOT USE FASTBOOT FLASH BOOT with this image as it will make it bootloop, just use fastboot boot command.
SOLVED
Thanks for the pointers hacktrix2006.. I tried supersu-v1.99r4.zip also v2 no luck. Had a quick look for how to get into fastboot mode.. couldn't access it from the bootloader.. so decided to take a backup image and restore to stock kitkat 4.4.2 via tomsgt latest tool 2.4.1 including doing Wipe data. then reinstalled TWRP then applied root.... AND noticed a screen saying something like ROOT ACCESS MAY BE FAULTY.. WOULD YOU LIKE TO FIX THIS.. I also think there was a warning about "be careful this action is irreversable" - I suspect the previous time I hadn't understood this properly and selected NO !! Anyway this time I said yes and now have ROOT YAY!
Now I start a re setup of the system and installation of apps etc.. I guess it's often a bit smoother 2nd (or 3rd 4th etc) time around
OK thx again for the encouragement, plus now I have a little more experience to offer someone else who may be struggling in this area.
no problem!
Hi everyone!
This is my first post, hope there is a solution.
I have Samsung Galaxy A3 [A300FU].
I wanted to get rid of branded firmware, so I've found stock ROM here: mrcrab.net/stockrom/sm-a300fu.html and flash it with Odin and it was ok.
Then I wanted root, so I've followed this guide: trueandroid.com/root-samsung-galaxy-a3-sm-a300f-easy-guide and now, whenever I restart the phone, it boots to the screen with yellow text: set warranty bit : recovery (file_1.jpg). Then it goes to the screen with opened green robot (file_2.jpg) and after I choose: reboot system now, it loads to OS normally.
How to fix it?
Ok guys, I don't know what happened, but I've managed to save the day
What I did was connecting my phone to KIES and select Firmware Update and Initialization from the Tools menu. It wipes all the data so be prepare for that. This helped to get rid of the yellow text on the screen while booting, but the phone still kept booting to the recovery mode.
Then I've installed TriangleAway from this thread: forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114 but it didn't seems to work (and, by the way, it doesn't support my phone). I've also installed SuperSU from Play Store, and also didn't work, so I've uninstalled both and reboot the phone. And guess what - it booted normally, straight to the OS.
Magic.
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
Hello, I recently bought a A3 as well and im quite dissapointed to see there are no custom roms or forums dedicated to the A Series (A3, A5, A7). Ive been itching to root and install a custom rom seeing the stovk is starting to slow down a A LOT! Could you help me out by guiding me through the bloatware removal as i dont want to uninstall something i shouldn't
Sent from my SM-A300FU using XDA Free mobile app
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
You flashed a custom recovery meant for Galaxy Alpha on Galaxy A3? Doesn't doing that bricks the device? I'm having the same problem too.
Sent from my SM-A300F using XDA Free mobile app
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Is TWRP 2.80 Working?
locovibe said:
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Click to expand...
Click to collapse
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Etnad07 said:
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Click to expand...
Click to collapse
Well, it seems it only solved yellow text and can't boot into recovery at all. It can't be that way! So!
I've installed unbranded software once again and was waiting to update to Lollipop via Kies. But it took so long that I couldn't resist to root, but I did it differently this time. I've found KingRoot app which works like a charm. Just download the apk [mmgr.myapp.com/myapp/Kingroot/webapp_kingroot/image/KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk] from [kingroot.net/down#root], run it and voila! No hassle, no Odin. After rooting there will come up two apps: Kinguser and some app in Asian. I've uninstalled the second one - it cleans memory and stuff. Stock recovery stays untouched and booting is normal.
Hi Everyone!
I Hope There Is a Solution....
I have galaxy a500g running with stock lollipop and I need to install a custom rom so I flashed TWRP_2.8_SM-A500-LL.img and booted into recovery once it booted into recovery it struck at set warranty bit:recovery and struck at recovery loop....is there a way to install a working custom recovery for galaxy a500g
Thanks in advance
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx
Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F
I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.
Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)
I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped
SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight
Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker and I am now receiving a security notice about unauthorised actions.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
ElronVonSexbot said:
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
Click to expand...
Click to collapse
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
jaannnis said:
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
Click to expand...
Click to collapse
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
ElronVonSexbot said:
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
Click to expand...
Click to collapse
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
jaannnis said:
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
Click to expand...
Click to collapse
Thanks, I was going to custom ROM eventually anyway so I may as well bite the bullet, and Renovate ICE seems to be the best out there, thanks for the advice.
I think you are right, it was my thought that because I used CF-Auto-ROOT no backup of the original/stock Boot.img was ever created giving me no point of return. god knows what actually went wrong with the root. I shouldn't have been lazy and avoided the TWRP step in the first place.
Again, thanks for the help, I am Downloading Renovate ICE now, only 1.5 hours to go, yay Australian internet.
I had a Media Pad M3 with unlocked bootloader, rooted and TWRP as recovery. As I wanted to update my ROM to BTV-DL09C100B311 I had some problems in TWRP an thought updating step by step would be a good idea. So I downloaded all missing ROMs throught FrimwareFinder and startet with BTV-DL09C100B307_fullOTA.
The installation in TWRP with ADP sideload worked and when I restartet my device a was a bit suprised that the yellow "Bootloader is unlocked - your device is unsecure" message was missing. I restarted again and the message is still missing. I thought OK perhaps I can now install all updates through the EMUI build in process without FirmwareFinder or TWRP.
EMUI downloaded the update and asked me to restart and install. After the restart the install process went to 20% and told me then there was a verification error. When I restarted the tablet again I got a screen similar to the yellow "Bootloader is unlocked - your device is unsecure". The screen is red an told me "Your device has failed verification an may not work properly".
Now I'm stuck. No updates work and TWRP could not be started or installed again.
I tried reinstall TWRP with fasboot (https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232) but I get the error FAILED (remote: "command not allowed"). I tried the newest TWRP mod from https://androidfilehost.com/?w=files&flid=125388 but same error.
Phone and FRP are still unlocked, as shown in FASTBOOT&RESCUE MODE so this is not the cause of the above mentioned fastboot error.
I installed the Android SDK completly and downloaded the newest toolkit (https://developer.android.com/studio/releases/platform-tools) but still get the above error. So I dont think its a driver problem either.
I did not try to unlock the bootloader again. I don't think this makes sense even if I still have the original codes.
I would like to get TWRP back and update the tablet to the newest ROM version. And it would also be nice to know what happened here
Thanks in advance for everyone helping me back on track. I think the first step should be get over the FAILED (remote: "command not allowed") error and install TWRP again.
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
sebbo2015 said:
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
I am also looking for a way to update my rooted M3 (WiFi edition) to the latest available version with security patch line of November.
Now I wonder whether with this updater in your post above this works immediately or if I also have to go through all the difficulties you faced?
Is it possible to install updates with a rooted device with this updater or do you always need to unlock the bootloader again?
Thanks for your help!
Just tried it out now and it worked! Data is still there, homescreen icons are a little bit messed up and root is gone (no problem).
This is great because I was looking now for a long time to find a way to update a rooted M3 with new OTA updats (all the usual way fails).
I used to do it with going back to stock and a factory reset being involved.
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Borkse said:
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Click to expand...
Click to collapse
Im happy I could help. I dont use Xposed.
Hi, can you, please, describe this in steps? What I have to do before standard OTA update should work? And when (and how) to open bootloader once more? Thank you very much.
Standard ota updates will not work. If you already have an unlocked bootloader you have to use this method https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 to manual update your M3 to the newest version.
If you have no unlocked bootloader please check this first https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232