Related
Hi guys,
I posted a question similar to this before, but did not get much reply.
I have a chinese Razr, and I would like to install an English stock 4.1.2 onto it. This is mostly because for some reason gapps do not work and I really do want gapps.
I have not flashed phones for two years so I have no idea what everything is. And it seemed like all these requires root. Which is my other problem: I cannot install root on this phone no matter what I try. Someone suggested to me that this was because someone had rooted this phone before in an unconventional way and this locked the phone for any future roots. And when I had updated to 4.0.4 I had lost the root and cannot regain it. I must have tried 20 different methods to root this phone already so I'm pretty sure this is hopeless until I flash a different rom.
In any case, my android version is 4.1.2 and system version is 672.300.384.XT910ChinaRetail.en.CN
And I would like to flash a stock 4.1.2 on it.
Check in the dev forum, you'll find links to the correct gapps for your
version.
Sent from my XT910 using Tapatalk 2
This is the gapps you need : http://www.4shared.com/get/HDGIsCws/update_gms_jb_spyder_r4.html
This is the china 4.12 root tool : http://dl.projectlense.com/download.php?file=spyder/razr_legacy_jbroot_034.zip
This is bmm apk : http://dl.projectlense.com/download.php?file=bmm/com.projectlense.bootmenu.getinfo.apk
What you need to do is simple, root your phone using the legacy jbroot by whirleyes, install the bootmenu manager apk file. Reboot into bootmenu recovery and flash the Gapps R4 package.
Dont thank me !
Q&A for [Official] Acer Liquid E3 / E380 / ALE3
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
CWM recovery method?
tiliarou said:
Updated yesterday to KK and it seems to work quite well !
I tried using OTA voodoo rootkeeper but it failed to restore the root after update so I used the CWM recovery method and it worked great.
One annoying thing is that I cannot quickly switch the sim card I want to use while in the SMS app. I used to dropdown the notification bar and there were 3 buttons to choose (sim 1, sim 2, always ask).
Now I have to dropdown notif bar, expand settings, click on the Message icon and change the behaviour for sending SMS... Very annoying !!!
Click to expand...
Click to collapse
Hi everybody!
Like everyone else I had lost root after updating to KitKat. I also tried to recover it with OTA Rootkeeper, but it wasn´t possible.
So what exactely is meant by the before mentioned "CWM recovery method"? I´d really like root back, but nothing is said/written about what to do AFTER having updated to KitKat.
Every answer is very much appreciated.
THX
bruceboss said:
Hi everybody!
Like everyone else I had lost root after updating to KitKat. I also tried to recover it with OTA Rootkeeper, but it wasn´t possible.
So what exactely is meant by the before mentioned "CWM recovery method"? I´d really like root back, but nothing is said/written about what to do AFTER having updated to KitKat.
Every answer is very much appreciated.
THX
Click to expand...
Click to collapse
It is as simple as reading the topic start / first post!
Just use the Flash / CWM method like aways/before!?
So download my (or your) scatter file and CWM recovery by vache (or Carlivs CTR) and flash it with SP Flash Tool (older version) etc. and install SuperSU from ZIP (SD) in your new CWM recovery.
Great!
hackwerk said:
It is as simple as reading the topic start / first post!
Just use the Flash / CWM method like aways/before!?
So download my (or your) scatter file and CWM recovery by vache (or Carlivs CTR) and flash it with SP Flash Tool (older version) etc. and install SuperSU from ZIP (SD) in your new CWM recovery.
Click to expand...
Click to collapse
Thx Hackwerk!
I thought so, but wanted to be sure.
I usually use One-Click-methods, but none is working for KitKat so far.
Thx again!
---------- Post added at 06:36 PM ---------- Previous post was at 06:04 PM ----------
hackwerk said:
It is as simple as reading the topic start / first post!
Just use the Flash / CWM method like aways/before!?
So download my (or your) scatter file and CWM recovery by vache (or Carlivs CTR) and flash it with SP Flash Tool (older version) etc. and install SuperSU from ZIP (SD) in your new CWM recovery.
Click to expand...
Click to collapse
WOW!!!
That was simple indeed!!!
Got root!
Thx a lot!!!!
Root Acer liquid e380
Ola
pode me ajudar por favor
estou a tentar fazer root no acer liquid E3 mais não funciona e não sei porque ja tentei com muitos programas e nada , pode me ajudar ?
Acer e3 4.4.2
I have the single sim version (1gb of ram) in the UK on Three network. I still have not had the kitkat update and many on the Acer forum haven't. If & when I do what is the best way to root it as I'd like to try out an app the supports part of the memory card to be used as RAM. Assuming these actualy work that is.
Edit:- just seen post above about rooting. Are the memory card to ram apps any good?
Thanks.
Kitkat already available in Belgium?
I've seen numerous post of people claiming they have gotten the kitkat update for acer liquid e380 in Belgium. I own the single-sim version and also live in Belgium but still haven't gotten any update notification. If I check for updates it says that I'm up-to-date. What is going? Hasn't it rolled out for everyone in Belgium yet?
how can I root ACER E3 _ E380 with KitKat 4.4.2
Hi,
how can I root the newest version of Acer E3 / E380 KitKat 4.4.2. ?
Thank you
ACER_E380 said:
Hi,
how can I root the newest version of Acer E3 / E380 KitKat 4.4.2. ?
Thank you
Click to expand...
Click to collapse
Read post #3 above. Someone already explained how to.
4.4.2 Update Single Sim UK on Three
Does anyone know who is holding up the update for the single sim uk Acer E3.
Build number:- Acer_AV052_E380_1.006.00_EMEA_3UKs
Three say they have not yet recieved it from Acer. Would this be true?
That's the build number I had on three,that's not even the most up to date jellybean build,I flashed the 1.016.00 gen1 build from the development thread and that jb build was so much better than the three UK build,it also had the kitkat ota ready to go on first boot after flash
Hi Gary,
That's a Three branded build. I think officially you should ask Three for the upgrade. Unofficially I am quite sure you should be able to upgrade to the GEN1 release using the instructions in the thread.
Regards,
Nika.
1.016.0 ?! I'm on 1.005.0, is something wrong with my device? It still says up-to-date.
Acer_AV052_E380_1.005.0_EMEA_BGCs
Btw, will I void my warranty when flashing an official rom? I'm not new to flashing, but because I haven't flashed anything on an acer device I'm pretty much lost already, and I don't want to brick my acer either.
Diddover said:
1.016.0 ?! I'm on 1.005.0, is something wrong with my device? It still says up-to-date.
Acer_AV052_E380_1.005.0_EMEA_BGCs
Btw, will I void my warranty when flashing an official rom? I'm not new to flashing, but because I haven't flashed anything on an acer device I'm pretty much lost already, and I don't want to brick my acer either.
Click to expand...
Click to collapse
BGCs = Belgacom Single SIM device. It's under control by Belgacom, so please contact them if you want an official upgrade. Can't say anything about warranty. I would expect that if a flash causes a system to fail it would not be covered by warranty...what they do when the original BGCs ROM is not on it when you have another issue, I don't know either... sorry...(officially they would always be allowed to deny warranty as soon as you start doing stuff like this I guess)
Diddover said:
1.016.0 ?! I'm on 1.005.0, is something wrong with my device? It still says up-to-date.
Acer_AV052_E380_1.005.0_EMEA_BGCs
Btw, will I void my warranty when flashing an official rom? I'm not new to flashing, but because I haven't flashed anything on an acer device I'm pretty much lost already, and I don't want to brick my acer either.
Click to expand...
Click to collapse
Yes you will void you're warranty flashing the Roms from these two threads as you need root and a custom recovery,and yes this acer had me stumped for a while but actually this device is the most simple device to flash that I've had,using sp flash tool it's all done effortlessly in just a few clicks in just a few minutes,I've bricked my device so many times
Flash it is then
Ok I want to flash to unbranded latest firmware, or newer Jellybean & the OTA kitkat if you guys will help.
I have:- SP_Flash_Tool_exe_v3.1344.0.212, USB VCOM Driver MT6589 & I've just downloaded 635475739172038202_OTA_Acer_1.0_AV052_A but this from from under Hackwerks sig so this is the duo 4.4.2 firmware. Mine is the 1gb single sim model. Is this the same or will I need different firmware.
A dumpties how to would be great. I am competent in these thing if shown how to do them. Last phone I flashed was Sony K750i !
Garyg124 said:
Ok I want to flash to unbranded latest firmware, or newer Jellybean & the OTA kitkat if you guys will help.
I have:- SP_Flash_Tool_exe_v3.1344.0.212, USB VCOM Driver MT6589 & I've just downloaded 635475739172038202_OTA_Acer_1.0_AV052_A but this from from under Hackwerks sig so this is the duo 4.4.2 firmware. Mine is the 1gb single sim model. Is this the same or will I need different firmware.
A dumpties how to would be great. I am competent in these thing if shown how to do them. Last phone I flashed was Sony K750i !
Click to expand...
Click to collapse
You have same phone as me,here's how I killed two birds with one stone with regards latest jellybean and kitkat,I created folder on desktop and called it acer tools so sp flashtool would find it easy,then I downloaded the latest jellybean Rom which vache posted on page 28 of the dev thread and copied it to the folder acer tools,then downloaded the supersu zip and placed it in my folder,then downloaded vache's cwm and Carliv touch recovery and placed in folder,fire up sp flash tool and do not connect phone to pc just yet,click on the word scatter file then to the left find you're folder and click on you're downloaded Rom and click scatter file then click open at the bottom,it should all then load up,now click download,now,with you're phone switched off(blue led) connect to pc,watch the loading bar and wait for green circle,all done!,reboot and you will have latest jellybean Rom with the kitkat update ready and waiting
Nearly there !
OK I now have all the downloads you mentioned from the sources you did.
I unzipped the rom file.
So I click on Scatter Loading on the right & load that txt file in the rom folder. All the files load in the bottom window all ticked.
Does the phone need to be rooted first?
Where does Acer E380 - Recovery - Carliv Touch Recovery 2.5 & Acer E380 - Recovery - CWM 6.0.5.0 by vache come in play in all of this?
I need to know how to turn my phone off with the blue LED. (is this USB de-bug mode)
Does it all sound good so far?
Garyg124 said:
OK I now have all the downloads you mentioned from the sources you did.
I unzipped the rom file.
So I click on Scatter Loading on the right & load that txt file in the rom folder. All the files load in the bottom window all ticked.
Does the phone need to be rooted first?
Where does Acer E380 - Recovery - Carliv Touch Recovery 2.5 & Acer E380 - Recovery - CWM 6.0.5.0 by vache come in play in all of this?
I need to know how to turn my phone off with the blue LED. (is this USB de-bug mode)
Does it all sound good so far?
Click to expand...
Click to collapse
I never unzipped the Rom,just copied the download to my folder,now you ask,I'm not sure about root,this method completely flashed a totally bricked phone so I assume root does not matter because when you do this the New Rom is unrooted with stock recovery hence the custom recovery downloads needed for when Rom is flashed,the blue led appears after you have just plain and simply powered you're phone off and plugged it into pc after clicking on download,once Rom is successfully flashed go back into sp flash tool(download hackwerks scatter file) and load hackwerks scatterfile like before then tick the recovery box,then click on the word recovery and load one of the custom recoveries you downloaded then click download,plug in you're switched off phone,blue led will show and sp tool will do its thing,you will then have Rom with custom recovery,place supersu zip on sd card and flash it from recovery then you are also rooted but if you decide to update to kitkat you must flash back stock recovery
flash
I couldn't get the flash programming to recognise the zip file, so had to unzip.
I'm not too bothered about root after its all done, as my Lloyd's banking app won't work.
So I won't really need the other files will I?
Q&A for [ROM][STOCK][5.0.2][D620] V20C Flashable Zip
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 [ROM][STOCK][5.0.2][D620] V20C Flashable Zip. 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!
then the wifi with KDZ work?
KDZ with CSE FLASH works and WIFI NETWORK : D
nanni1989 said:
KDZ with CSE FLASH works and WIFI NETWORK : D
Click to expand...
Click to collapse
Actually, all that's needed is modem.img from the KDZ for the WiFi to work. Also normal flash should do it too.
Sent from my D620r [Stock 4.4.2 , -V- Kernel]
:good::good:
it's ok
Upload the screen shots.
Can I flash this with twrp recovery over stock kk?
D620r lolipop
When flashed via TWRP it works wifi, but not GSM. When flashed via KDZ, everything works.
Boot loop
I have a d620 that came with a v10e firmware. Two nights ago my phone updated to the 5.0.2 and I got stucked on the lg logo. Fortunately I've managed to flash it back using the stock rom. I really want to update to lollipop and I was wondering if any of you guys know how to get around the bootloop problem.
sviktoro said:
When flashed via TWRP it works wifi, but not GSM. When flashed via KDZ, everything works.
Click to expand...
Click to collapse
Use the latest version and it will work.
Can't install
IH after i'm try to install vkernel the phone is bricked now i flash stock and reunlock but when i try to install the phone doeasn't boot . is stucks on lg bootanimation, any solution?sorry for my bad english
Will It work when ive flashed another kernel?
Ive got a D620 with CM 12 installed and an Overclocking Kernel that (as far as I know) only works with the CM Rom...
How can I undo this and flash the stock kernel? I havent found it as download here...
D618 V20b lollipop BUG on COC
is there any bug on COC graphic failures on war logs and etc.? on clash of clans?
im using the stock-rom lollipop - CIS version and the bug on the COC game.
you have Screen wake up notifications with Glimpse Notifications from google play, for all lg g2 mini. perfect.
I've flashed the zip on my d620r, everything works great. There are no bugs, battery life is very good compared with KitKat 4.4.2, and smoother overall. Great job!
Upgrade from V10g to V20a keeping data
First of all, thanks to all putting effort into this development.
I own a D620r with software V10g and KitKat 4.4.2, unlocked bootloader and TWRP. I used towelroot to root it. Everything runs fine so far.
I got a notification for the official OTA update to V20a and downloaded it to the device. I tried to apply it but were stuck in a recovery loop. I learned that official OTA updates need stock recovery and I cannot apply them having TWRP installed. I applied this fix to escape from recovery loop. The device is alive again, but the LG updater app asks to apply the downloaded update once a day.
Now I found this thread. The phone is my main device and contains lots of apps and settings. I want to keep the data if possible.
A) Do I have to expect trouble when I flash the V20a from this thread without wiping the data partition?
B.1) Or would the following procedure be an alternative:
Flash stock recovery (I made a backup using Rashr)
Revert bootloader to original locked aboot
Apply OTA update
Root
Replace bootloader with the unlocked one
Flash TWRP
B.2) I read that towelroot is based on a security vulnerability of the linux kernel that is fixed with Lollipop . If that is true, can someone give a hint how to root on Lollipop?
C) Can I choose between V20c/D620 and V20a/D620r or do they belong to different devices and are incompatible?
Thanks for your time reading this post.
Thanks
Thank you for the Rom and the instructions. It works great, there are no functions that are not working.
It also solves the bug for the smartwatches that caused battery drains on Kitkat.
when a version with xposed???
peligropowers said:
when a version with xposed???
Click to expand...
Click to collapse
Never, because this is the stock rom in a flashable .zip for custom recovery.
And xposed for android 5 ist still alpha and doesn't work correct on our phone.
If you want to try xposed you can just install it.
Read the xposed thread for that.
Please don't ask any further questions about xposed here, this thread is only about zip flashable stock rom.
Thank you.
Installing this ROM
This post was a mistake. Question is below this.
I just flashed this ROM and a problem appeared
Every time I boot my phone up I get this message.
WARNING!
Current version is not available for user. Can't find matched cust for NT-code mcc/mnc[29403],subset[FF]
What does it mean?
EDIT:
Also one more question, can I update my phone OTA in case there is a new software?
[Q&A] Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or
Q&A for Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other
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 Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other. 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!
Mega 2 as well.
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Custom Recovery?
Any luck with a working custom recovery?
running backup before running the app.
Thank you shockazulu for your post on the mega2 root.
I'm new to this and have been looking and searching for the best way to do it and most have refurred the king root app.I do have a questions .
Do I still need to do a backup of the phone before running the app.?
Is this a preferment root as I noted your phone reverting back to it's original state?
Noticed there is a newer version of the king root app now 4.5 and would it be better to run that app ?
Thanks Again and I'm sure I'll have another question before I get into doing this !
Chris
I manage to root the galaxy mega 2 on the newer baseband G750AUCU3AOFA. Since for some reason you can't root it on that build. but with the modem flash it worked
Matt Cajon said:
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Click to expand...
Click to collapse
The problem with the att version of the mega 2 is that the bootloader is locked. So there is no way to use a custom bootloader like Clockwork. Without a custom bootloader we can't load/flash roms.
But what we can do is........
We can use a program called Flashfire. Flashfire is a way to flash things on our phone without having to use the bootloader.
We can also use exposed launcher and wanam exposed. This is the tools we can use to make customise our stock rom.
One of us could customize a rom and create a step by step for how they created it. If it is a stable setup then instead of others flashing that custom ROM, they would fallow the steps to create the same custom ROM.
whats with the vague answer ...
if you rooted it on OFA how did you do it?!?!
WHAT MODEM?! please elaborate I need to know asap..
Any of you had luck on installing a custom recovery for it? i am trying to help another forum member who have this S750A .
I recently ported a custom TWRP for my device which is a SM-J105B. Found out that TWRP was easier to port/works better on it than CWM for instance. Maybe this is the case for you guys device, i want to help out.
i know this is a 1 year old post but if any were successful please share the knowledge cheers from Brasil!
Pindroid is trying to help me i have a samsung galaxy mega 2 sm-g750a also it said "unlocked" on the ad when i got it but anyways we are looking for the original 4.4.4 kitkat firmware and can't seem to find it anywhere but the one we did find that has repair in its title has never worked as far as flashing with it goes. I have lollipop right now and it works fine but it hasn't solved the problem im having with my IMEI so we are trying a downgrade to see if that helps. Anyways thanks for any help
I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops then I gotta reflash 5.1.1 firmware via Odin ...I've looked and looked just the run around on how to root this device,I really wanna root this phone love the screen and it's my go to phone for work ,if anyone could figure this out that would be awesome
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Surgeman said:
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Click to expand...
Click to collapse
Thoughts on how to root or how to fix the bootloop?
Piridroid said:
Thoughts on how to root or how to fix the bootloop?
Click to expand...
Click to collapse
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Surgeman said:
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Click to expand...
Click to collapse
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Piridroid said:
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Click to expand...
Click to collapse
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Piridroid said:
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Click to expand...
Click to collapse
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Surgeman said:
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Click to expand...
Click to collapse
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Piridroid said:
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Click to expand...
Click to collapse
Ok let me know what you find with the firmware when you get the chance.I have used 360root also in the past myself on devices when nothing else would work.I have tried several times and different ways.Disabled Knox via terminal with temp. root and still no go.It's the SELinux enforcing is the biggest problem.Kingo will install as a system app..but you won't have full root unless you run the apk to root the device again and it reboots on it's own after about 5 minutes or so.I'll keep stabbing at it..and post my findings.I assume I'm not the only one that could use this.Thanks for your time Piridroid.
Anything new on this?
First, I had a rooted G3. Never updated it. Now, I have an H830 (T-Moble) variant. I've been rooted since I bought the phone and have never updated because I don't know how to do it without losing root. I'm still on software version H83010d (Android 6.0.1).
From what I've gathered, I just download the .zip in here and install via TWRP and then flash superSU afterwards?
I'm not completely sure what the talk of modifying boot.img or removing recovery-from-boot.p...
My reason for updating is because I want to try the Fulmics ROM or any optimized ROM for that matter. I had one on my G3 and it ran so much better.
But then as a follow up question, is the update process the same from a ROM? Do you just flash an update over the Rom and then re-flash the ROM?
Any links or answers are appreciated so I can finally figure out how to update while retaining root on my devices. :laugh: