Related
Hi all,
I'm a bit of a n00b at this, so please forgive me.
I started with Android 4.1.2, Kernel 3.4.0-g298631f-02047-gec59411, build 10.1.C.0.370.
I rooted it using Doomlord's easy-root and then when attempting to flash custom recovery, I accidentally flashed some other .img and the tablet wouldn't even turn on. I cried. Like, a few good tears.
Went online, found out I wasn't screwed, and figured out how to flash SGP312_10.4.B.0.577_VMo DE_1273-3719_WIFI312G.
But, as I said, I lost root, and am confused about how to downgrade back to 4.1.2 properly without bricking.
Here is my current info:
Version 4.3, Kernel 3.4.0-g1b44cd5, build 10.4.b.0.577
In this thread, under "Downgrade your rom" and "back to 4.1.2 and rooting" it says "if you're in 4.3, Flash this SGP 351 4.1.2 FTF using Flash Tool and it will be booted in 4.1.2. if you have different Variant downgrade to your Variant FTF file"
What is a variant FTF file? Can I just use any SGP 312 4.1.2 FTF? Does anyone know a safe one to use?
Thanks!
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
worf_1977 said:
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
Click to expand...
Click to collapse
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
UberBaumer said:
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
Click to expand...
Click to collapse
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Cat McGowan said:
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Click to expand...
Click to collapse
THANK YOU, SIR.
I really appreciate it!
Back onto 4.1 and just rooted again. Now I just need to manage not screwing up installing CWM like I did last time!
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
UberBaumer said:
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
Click to expand...
Click to collapse
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Cat McGowan said:
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Click to expand...
Click to collapse
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
UberBaumer said:
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
Click to expand...
Click to collapse
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Cat McGowan said:
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Click to expand...
Click to collapse
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
UberBaumer said:
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
Click to expand...
Click to collapse
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Cat McGowan said:
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
Damn, maybe I was a bit too hasty in rooting my tablet; why is it that I can no longer to OTA updates? If I were to buy SuperSU PRO (for survival mode) is there any benefit to me? I see that it allows for OTA updates.
I am currently rooted via Superuser (by clockworkmod).
When you say I'll need to install 4.2.2 by flashing, you mean through Flashtool, right? Which build should I get (and where, one of the development forums)?
Is the reason why one is advised to install custom roms via recovery mode in order to maintain root access (which I'm assuming doesn't happen if you flash through Flashtool)?
Something I forgot to mention earlier is that I did unlock the bootloader. I'm not sure if that helps or hinders me at this point.
Thanks again for taking the time to answer all my questions. I really love this new toy, and I'm so terrified of bricking it.
Cat McGowan said:
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
UberBaumer said:
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
Click to expand...
Click to collapse
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Cat McGowan said:
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Click to expand...
Click to collapse
Thank you again my friend.
Is there a list of apps that are safe to uninstall, or, rather, a list of apps that I shouldn't tinker with (for fear of uninstalling an app that has a dependency on something critical)?
Also, I'm on the Google Play store and I see both Titanium Backup Pro and Rom Toolbox Pro. Should I buy both? If you had to buy just one, which would it be?
My main goal is to just make the smoothest experience possible. I want to take maximum advantage of the hardware in the tablet and have as few unnecessary programs running as possible.
DO NOT USE ON FOF6 FIRMWARE. WILL "BREAK" YOUR CAMERA. CHECK YOUR FIRMWARE VERSION.
Root method for FOG6 / 5.1.1 for the G900t THIS WILL TRIP KNOX. If you don't want to trip knox don't use this. If you do use it and whine you tripped knox because you didn't read ,we will all point and laugh at you.
Named it TrapKernel because well its not my normal HispAsian Kernel and I listened to a crap ton of Trap Music while doing it.
Thanks to @g.lewarne and his root method with his Unibase and Unikernel for the s6 , we finally have root after I ported it over to us. So be sure to thank him for his work.
What's included:
Auto installation of root and busy box
SuperSu.apk
A stock build prop with secure storage set to false so wifi passwords and etc aren't forgotten after reboots.
Kernel set to permissive
Otherwise stock
So here's the deal. Stupid simple.
1. Download the kernel
2. Flash in recovery (if twrp asks if you want to install su say NO)
3. Reboot and profit.
If you need more detailed help go HERE
Download
TrapKernel G6 [TWRP ZIP]
TrapKernel G6 [ODIN TAR]
Do NOT mirror this link. That means you "Android Geeks".
Special thanks to:
@g.lewarne for the obvious reason of being awesome and his root method for the s6. I suggest donating to him here [emoji14]
@ashraf sharif for testing
@Chainfire for SuperSU
also mine
This is wonderful. Thank you, sir.
EDIT: Works perfectly.
i just flashed it and somehow it broke the fingerprint scanner. nvm after a reboot, it is working now.
Awesome... thanks man!
Thanks! Working good. This. Is the 5.1.1 we should have gotten.
So when I come BAck I have everything.... is this new update faster the older one. was so buggy like 4-5 random restarts and freezes
I tripped Knox thanks bro ahaha!!!!
edited. My questions seemed too dumb
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
dpluigi said:
Great news about Trap Kernel root method for FOG6/5.1.1.
Background: I got a rooted TMobile GS5 4.4.2 last year and lately I had problems with storage from contact list file cache filling-up, over heating phone/cpu. Shortage of storage was fixed by clearing contacts app cache but still it prompted me to upgrade to 5.1.1 Lollipop, rooted earlier this week (see details below), but the camera app is broken. Glad that ShinySide was able to provide a Root method which won't break the camera app.
Just reviewed the detailed help links and took note about not letting TWRP install SU - note that I had let TWRP install SU with HispAsian kernel. I am using Android Unified toolkit PRO (with Odin3 v3.09), which was used to install TWRP 2.7.1.0 (latest available there). Before installing this new Trap Kernel when I get a chance:
Is it recommended to first update my current TWRP 2.7.1.0 to a newer version?
Is tripping Knox really an issue for phones if they are past 1 year since purchase (i.e. 1 yr manufacturer warranty expired)?
Thank you for clarifying,
Current system (rooted but broken camera app):
Baseboard: G900TUVU1FOG6
Kernel ver: 3.4.0_HispAsian_Kernel ShinySide #1 Thu Aug 6 23:52:39 2015
Build #: LMY47X.G900TUVU1FOG6
Recovery: TWRP 2.7.1.0
Click to expand...
Click to collapse
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Just did mine. All seems good. Camera working.
Question. Lately, anytime I flash anything, when clicking on twrp reboot, it gets stuck on tmobile screen on reboot, and sometimes I long press power button and it's finishes boot and my homescreen loads. Other times, I gotta pull battery, and then boots fine and all further reboots are fine, no hang ups. What you think this is? Something in my twrp? I leave everything checkmarked in twrp restore, cache and everything. Wonder if that is causing it somehow. Should I wipe cache and dalvik in twrp reboot?
Thanks for the new trapkernel! I missed my root access those past two days and not having my adaway to block ads.
ShinySide said:
Flash which ever version. I always use the latest
You've already tripped Knox considering you have HispAsian kernel installed.
Install this kernel camera will work
An updated hispasian will be posted soon. It's already up to date plus some as the F6 version, I was just waiting for Kernel Auditor to accept a pull request so we're officially supported by its kernel download feature so I can push updates thru the app and can flash it via the app
Click to expand...
Click to collapse
Thanks, that was quick and easy. TWRP was updated to 2.8.7.0, and with TrapKernel both Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not letting TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. So under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks,
Donat
dpluigi said:
Thanks, that was quick and easy. Camera and MHL connection work fine. Note though that I forgot to deselect Auto Reboot in Odin Option tab, so the phone did boot up fully after TWRP update and before flashing TrapKernel from Recovery Boot. It seems fine.
Regarding your note about not let TWRP install SU, I already had SuperSU installed under my previous Kernel by TWRP. SU (already installed) seems to work fine but it is now prompting to update the SU binary. Under TrapKernel is it ok to proceed and update -or- should it be removed?
Thanks
Click to expand...
Click to collapse
Because hispasian kernel doesn't contain the auto root.
You should be able to update it. I've havent been prompted yet
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
CptCrackers said:
Since the more details link seems to be dead or at least down, is there another way I can find out how to do this? It seems like you already have to know a number of things to follow the instructions in the first post.
Also, does this method reset your phone? OR are your settings, etc still intact after the root is complete?
Thanks.
Click to expand...
Click to collapse
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
What dhould the wake and sleep be set at and what do they do ?
Thanks
Sent from my SM-G900T using XDA Free mobile app
ShinySide said:
Their down for maintenance.
Put zip on SD card
Flash twrp with odin
Reboot directly to recovery
Flash kernel
Hit no if asks to install SU
Reboot.
No settings or data loss.
Click to expand...
Click to collapse
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
CptCrackers said:
Thanks.
As far as lost settings. So far, I've had to re-enter wifi keys.
Is it possible or even advisable to put the original recovery back in after it's rooted?
Click to expand...
Click to collapse
Yeah you can
what will happen if I try to do this with SM-G900V ?
Ok.. so.. I keep seeing people saying there is a way to root still if you are on GOC1.. but I can't find anything that says what that way is. I also see 5.1 roms for this phone, but nothing that says how to install the bootloader it requires to install them. On my old phone, a Droid X2 you had to root before you could install a bootloader before you could install a rom. I am not seeing any straight up guides on here for working with this S4.
What I really want is just a basic root, so I can uninstall all the hardcoded crapware on this phone (NFL Mobile, Trip Advisor, etc..)
Short of that I want to install CM 12.1, which is probably a better route anyway, but the page for that says you must be on so and so bootloader without telling you how to INSTALL said bootloader. I'm totally lost here, things were a bit more straight forward on that old phone.
Edit: Yeah, I think what I really want to do is install CM 12.1, but I don't even know where to start.
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
skepticmisfit said:
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
Click to expand...
Click to collapse
Kingroot doesn't work. I don't know what its saying in the orange text after I run it since its not in english, but it doesn't work.
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Try getting KingRoot desktop version 3.0 I just used it on Version I545VRUGOC1 that I did the OTA update with and got it rooted I can use Titanium Backup to remove all samsung Knox and other bloat wear.
bangdosa said:
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
Click to expand...
Click to collapse
I gave kingroot another try since I had rebooted a couple of times since making this post, it worked this time! Huge thanks for that tip.
XxD34THxX said:
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Click to expand...
Click to collapse
Thank your for that. Flashfire is in the process of installing the rom. We'll see how it goes.
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
DallasDave said:
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
Click to expand...
Click to collapse
Just use the KingRoot app to root. It worked for me on first try.
Hey there fellow XDA forum members, I am currently running stock 6.0 Marshmallow on my Moto E XT1527 Surnia (Telus) and have that squid build of TWRP and it runs fine. Now here's where I run into issues... I've tried twice now to flash the SuperSU Update zip but when I boot into recovery TWRP doesn't ask me if I want to install SuperSU, and not sure but I didn't check the box for "keep read only" and just swiped right; does that matter? Anyhow; back to my OP, is there a way to get SuperSU Update to stick? Cause after flashing the zip as aforementioned, and reboot system, it just hangs at the white warning bootloader unlocked screen...why?? And I heard about systemless root for 6.0 but honestly don't know where to begin, and thought there would've been a tutuorial or a guide but have yet to find one, any help is greatly appreciated, thanks!
I posted this recently.. [XT1527] Install Systemless Root on Marshmallow
It was on page 2
I used that method and i have the same phone as you.
It's still working good for me but you may want to toggle namespace separation on or off
if some app's give you issues.
If you have Busybox installed then make sure it's using a recent newer version that is fixed for this issue too.
Okay so I have not seen anything new in regards to us unfortunate enough to have the Cricket variant of the grand prime, so I decided to put together a little step by step to get xposed installed and running on this device, I think it may work on others as well, but since I have not attempted it then do not just assume it will. This guide is as stated in the sub line of the post for the SM-G530AZ running 5.1.1 Lollipop. I am not responsible if you brick or bootloop etc etc your device. So long as you can follow directions you should be fine.
1. First of all you must already have root access on your device, mine is using SUPERSU to handle root requests. If you do not have root yet then check forums for way to do so it is there already, however you must root with kingroot or manually with the same exploit that kingroot is leveraging in order to obtain it before attempting the install of xposed, otherwise it will fail.
2. You need to download the zip file attached to this post to your desktop or device and unzip it into your device sdcard.
3. Once you have extracted the apk and zip files into the sdcard you need to install the xposed installer apk so make sure you have enabled Unknown Sources from your settings/Security menu and you may get a warning from the device as well that is okay just tap okay and finish the install.
4. Now you need to download flashfire from the play store and install it as well. Open flashfire and flash the xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip that you will have extracted Choose flash zip in flashfire and make sure you leave automount unchecked. You can open the xposed installer app to make sure it recognized it, which it should if you flashed it properly.
5. Now you can enjoy the Xposed Framework on your device.
I am currently attempting to learn as much as I can about the trust zone and smc as I can tell you that is the only way we are going to get custom recovery and roms on this thing sadly. I am also following someone who claims to be able to rollback android from 5.0+ to 4.0-4.4.4 via jtag which is something I too have pondered on if it was possible and honestly I think it would be, I would like to explore the possibility that their may have been more vulnerabilities within the device prior to the 5.1.1 update I currently have 5.1.1 installed which is what the device had at time of purchase for me, however some may still be running 4.4.4 if you happen to be using 4.4.4 still then I cannot say whether this guide will work or not for you I think it would but you would probably need to use a little older version of the xposed installer but I am not certain, I would probably just update to lollipop if you really want to be safe about it and the firmware has been posted on these forums as well. Please hit the thanks if this helped you out at all, and if you are confused or have an issue you can pm me and I will try my best to get back to you whenever possible. But this is how I got xposed working on my device by simply rooting with kingroot, then using the mrw script to remove kingroot and replace with supersu and enabling unknown sources. The root guide that exists for this device however stated to flash some other boot.img and I actually had issues when I did that step, so after i went back to stock again I did the root guide with kingroot and did not ever flash that other boot image and all worked fine for me.
Awesome thanks. I assume install King root then flashfire then SuperSU binary then uninstall king root. For SuperSU?
Sent from my DROID Turbo using XDA-Developers mobile app
THANK YOU THANK YOU THANK YOU! Thank you so much!!!!!! I have been trying to do this for 3 days now!!! I have soft bricked my device, restored it, got it going again, soft bricked again. Over and over. Until finally, today on my first day off all week I took the time to read your posts over again. I found this one and it finally got me there! I have the same exact phone, Cricket Samsung Galaxy Grand Prime Model SM-G530AZ. I have been struggling to find a TWRP or CWP recovery and I am pretty sure there isn't one available currently. So then I found this method and FINALLY SUCCESS!!!!! Anywhere I can donate to you?