Xperia E4g Root method FOUND - Sony Xperia E3

as far as i know, no-one has managed to root on new firmware. Here's how i did it:
1. Get into developer mode by going to Settings -> About phone and keep on tapping 'Build number' until it says 'Congratulations, you are a developer'
2. exit 'About phone' and go to the new tab 'Developer options' and click 'USB debugging.' Press okay.
3. exit 'Developer options' and go to security, allow 'Unknown sources.'
4. Goto www(dot)kingroot(dot)net (can't do URLs. Srry). download the apk. if you downloaded it to your phone just install. if you downloaded it to pc use a usb to transfer or something- your choice on how it gets there- and install it on the phone.
5. run it and attempt root 2 times. both times should fail. straight after the second fail exit the app, shutdown and turn on. Do not reboot, as this doesn't work if you reboot.
6. Device should be rooted. Use Purify to check. If purify isn't installed, the process failed. If purify cant get root access, the process failed. Try an app that uses root. if a tab doesn't come up, the process failed.
this is how i rooted mine. not sure if it works generically or if it was one-time for me.
I posted it here, as there is no E4g forums, and this seemed like a popular place for the E4g posts.

Stay away from kingroot

Why must stay away from kingroot?

mie_shariff said:
Why must stay away from kingroot?
Click to expand...
Click to collapse
Kingroot dosent root the phone fully its an online root so you information can get access by the app, you phone can unroot any time etc..

Related

[SOLVED] UPDATE Bypass Mobileiron and Root Detection ICS, JellyBean

Disclaimer: This is for testing purposes only. I do not condone breaking company policy, or breaking any laws. I am not responsible for you getting fired as a result of you making these modifications. You should always read and abide by company policies and any laws pertaining to such modifications. Use of this tutorial is at your own risk.
Preface: I have tested the new method on multiple devices and it has been flawless so far.
UPDATE: I have found a new method that so far has been flawless across multiple devices so far for me. With this new method you won't even have MobileIron installed when you're done! I have tested this on my Galaxy Nexus, My Nexus 7 and my Galaxy Note II and believe it should work regardless of device. Your company may have different security policies than mine so it's possible this may not work for you.
The easiest way to do this is with one of mskip's toolkits, but it can also be done manually with adb (must have the latest sdk).
Toolkit Method
0. Make sure you have MobileIron and Touchdown installed, configured and syncing. Your phone does NOT have to be rooted to do this.
1. Download mskip's Toolkit Here and install.
2. Make sure you have the adb drivers for your phone installed on your computer and android debugging is turned on in the developer settings on your phone.
3. Open the toolkit and connect your phone to your computer
4. It shouldn't matter what model phone you choose for the purpose of what we're doing, and the options may be slightly different based on which toolkit you download
5. Choose the option backup and restore your device
6. Choose backup all installed apps
7. Choose do NOT include system apps in the backup
8. Choose backup apk's AND respective app data
9. Choose do NOT back up internal storage data in backup
10. Wake your phone and it will ask you to start the backup, choose to do so
Once it is finished you will need to wipe your phone. It may work without wiping and just uninstalling touchdown and Mobileiron before proceeding to the next section, but I haven't tested this.
11. Connect your phone to your computer and enable android debugging
12. Browse to C:\Galaxy Nexus Toolkit (or whatever the name of your toolkit is under c:\)
13. Open the folder backups and rename the backup file to backup.bak. (if you don't see the file extension just name it backup)
14. Open the toolkit and choose a model
15. Choose Backup and Restore
16. Choose Restore apps from a backup file
17. type backup.bak and press enter
18. Wake your phone and choose to begin the restore
19. When it's finished, uninstall mobileiron, open touchdown and see if it's syncs!
ADB Method
adb backup -all -system -shared -apk
recovery> backup, wipe, flash rom, flash gapps, reboot
adb restore backup.ab
Requirements For ICS:
1. Rooted Android Phone running ICS based ROM
2. Titanium Backup (app installed)
3. Hide my Root (app installed)
4. Mobileiron (app installed but never run)
5. Touchdown (app installed but never run)
Instructions for ICS:
0. Make a Nandroid backup
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable. (Its at the bottom when disabled)
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
14. Profit
Now restore your nandroid backup before you get in trouble.
**Update** for Jelly Bean
It seems the builds out there for Jelly Bean use a new version of SuperUser that as of yet isn't compatible with Hide My Root. I wrote the developer of Hide My Root and he is looking into this but currently doesn't have a device running Jelly Bean to test on, so I took it upon myself to figure this out once again. I tested this and it does work. Again this was tested on a VZW Galaxy Nexus only.
Instructions for Jelly Bean:
0. Make a Nandroid backup!
1. Download MobileIron (App installed but never run)
2. Download Touchdown (or any apps that depend on MobileIron and do not launch them)
3. Download Titanium Backup (You may need the premium version to freeze apps)
4. Download SuperSU flashable zip from HERE and place on your SDcard.
5. From the app drawer launch SuperSU (that app already installed, not the zip you just downloaded)
7. Swipe 2 screens to the right to Settings
8. Choose Full unroot.
9. Install and configure MobileIron and dependent apps and let them fully sync.
10. Enable Airplane Mode
11. Reboot to recovery and flash the SuperSU zip you downloaded
12. Boot into Android, open Titanium Backup and freeze MobileIron
13. Turn off Airplane Mode
14. Profit
Now restore your nandroid backup before you get in trouble.
After a reboot all of the lockscreen options will reappear allowing you to have an insecure lockscreen.
This is great
You just saved me hours of frustration.
Thanks!
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
SoCalNewb said:
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
Click to expand...
Click to collapse
I have only tested this as posted. Make a nandroid backup and play around with it
How to re-enable superuser?
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
bhilgeman said:
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable.
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
Click to expand...
Click to collapse
SoCalNewb said:
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
Click to expand...
Click to collapse
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
bhilgeman said:
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
Click to expand...
Click to collapse
YOU ARE THE MAN.
That was so simple, but I spent an hour trying stuff and still missed it
My Android experience is back to awesome despite Mobile Iron - THANK YOU!!!!
Thanks for that. Great idea.
I followed your instructions but I had to switch 9 and 10 because Hide my root cannot restore a deactivated app.
But my TouchDown says "Synchronization Error" --> access denied (update your password). Maybe too strong policies?
And by the way: you have to use tintanium backup PRO to enable or disable apps
---------------------
Edit: I made a system application of "Hide my root" with TI Backup - works. I had to uninstall TI Backup now - currently TouchDown is syncing again. We will see if it works, next: I try to use LBE Privacy Guard... will report. Disabling "MobileIron" seems not working for me...
Hey, is not possible solve it on 2.X version of Andriod? Thanks...
OP Updated to reflect Changes for those running JellyBean. Long live the Android experience!
bhilgeman said:
The SU change needed for JellyBean makes this previous method unusable. I did however figure out how to still get to the same result if you're running JellyBean.
I will so an update to the OP soon to reflect this.
Click to expand...
Click to collapse
Looking forward to the instructions for making this work on JB
SoCalNewb said:
Looking forward to the instructions for making this work on JB
Click to expand...
Click to collapse
OP updated for JB instructions.
Sorry, I haven't tested this on a 2.x build so I'm not sure. If I get time I'll try to test this for you, I'm just super slammed with projects right now...
Will we appear "normal" on the Server that the app links us to our Corp acct??
Yes, you will appear as a non rooted phone. I just updated the JB instructions again. Realized I left out a step.
Anyone test this for Airwatch yet?
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
makelegs said:
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
Click to expand...
Click to collapse
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
bhilgeman said:
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Skanklove!
I was completely under the radar, due to some corporate user configs, until I screwed up and raised the red flag. Then I had to encrypt, and install mobileiron. I was perfectly happy with touchdown until mobileiron got involved. I don't want work email on any device other than my work phone (toro). I can still run email without mobileiron, but no activesync and no email attachments......meh
Steps on ICS
Hello,
I am new to using mobileiron, as my corporation just started to use this program. Can I use your steps on ICS and keep my root undetected or will I eventually have issues. Last question, why is it necessary to restore your nandroid backup at the end?

[Q] Help to root Blu Neo 4.5

Someone help me to root this brand-new smartphone, i tryed framaroot, kingo root and mtk droid root but with no sucess... Someone help me please
M3tt said:
Someone help me to root this brand-new smartphone, i tryed framaroot, kingo root and mtk droid root but with no sucess... Someone help me please
Click to expand...
Click to collapse
i looked around for some suggestions that might work, but sorry, i cant find any.
M3tt said:
Someone help me to root this brand-new smartphone, i tryed framaroot, kingo root and mtk droid root but with no sucess... Someone help me please
Click to expand...
Click to collapse
Just picked up a Neo 4.5 as a gift for someone today. Rooted & installed SuperSU binary & App w/ Framaroot v1.9.4. Maybe the version you tried didn't have the correct strings for the MT6572 yet. I believe it worked with Boramir.
i need root too
Need4Sneed said:
Just picked up a Neo 4.5 as a gift for someone today. Rooted & installed SuperSU binary & App w/ Framaroot v1.9.4. Maybe the version you tried didn't have the correct strings for the MT6572 yet. I believe it worked with Boramir.
Click to expand...
Click to collapse
I try but not work.
Can someone give me some advice or point me in the right direction please
M3tt said:
Someone help me to root this brand-new smartphone, i tryed framaroot, kingo root and mtk droid root but with no sucess... Someone help me please
Click to expand...
Click to collapse
Hi sir its been four months, did you find a way to root your blu neo 4.5? i desire to also, thanks in advance.
I'm also looking for help
Need4Sneed said:
Just picked up a Neo 4.5 as a gift for someone today. Rooted & installed SuperSU binary & App w/ Framaroot v1.9.4. Maybe the version you tried didn't have the correct strings for the MT6572 yet. I believe it worked with Boramir.
Click to expand...
Click to collapse
Could u possibly do a step by step walk through. That would really help .
Kingo Root instructions
mar_sm said:
Could u possibly do a step by step walk through. That would really help .
Click to expand...
Click to collapse
I´'ve rooted several BLUs with Kingo Root (just Google search for it and install it on your laptop). The challenge if you are a noobie is that sometimes you miss a step OR people assume that you know the basics, so they forget to tell you about some important steps that you must take before you root.
Instructions:
1. Install Kingo Root.
2. On your BLU, open Settings (make sure you have allowed applications to be installed from Unknown Sources...you'll find this option under Security in the Settings)..
3. In Settings, go to About Phone and rapidly click on the "Build Number" as many times as it takes to say, "You are now a developer". This will open a new option in the Settings called Developer Options.
4. In Settings, now go to Developer Options and make sure it is ON and also turn on the USB Debugging. VERY IMPORTANT!
5. Now connect your BLU to your computer via a USB cable and wait till all the drivers are installed and the device is READY TO USE.
6. Disconnect your phone from the computer.
7. Run the Kingo Root software.
8. Connect your phone to the computer (Kingo will eventually connect to the phone and then will show you a big ROOT button.
9. Click the big ROOT button and sit back till it does its thing.
10. Wait till Kingo gives you the "ROOTED!" message and then you are done (so go ahead and unplug your phone from USB and close Kingo Root software).
11. Reboot your phone and confirm root (download Busy Box Checker from Play Store). You might also want to download Busy Box X and install the busybox binaries..
OPTIONAL SUPERUSER:
You don't have to do this next part if you're happy with Kingo User.
Note that these days, Kingo Root will install a superuser (su) binary that is controlled by their own app called Kingo User instead of the SuperSU app. If you want SuperSU by Chainfire, you have to search XDA for BETA SuperSU 2.49. You'll find a zip file with a beta version of SuperSU and a script that will eliminate Kingo User and replace it with SuperSU.
Install BUSY BOX X on your phone (download from Play Store).
Place the SuperSU v2.49 zip on your SD card in the phone (IT MUST BE THE VERSION 2.49 NOT THE OFFICIL 2.46 OR THIS IS NOT GOING TO WORK). Then boot into recovery (to do that you turn your phone off and then after it is off, you restart it with the power button while you are holding down the volume UP button). Then you use the menu you find there to "Install a zip from SD card". Select the zip you just put on the SD card, and it will flash the SuperSU program and binaries to your phone, while deleting the Kingo User app and it's binaries. Now select Reboot System at the top of the menu and you're all done.
Need4Sneed said:
Just picked up a Neo 4.5 as a gift for someone today. Rooted & installed SuperSU binary & App w/ Framaroot v1.9.4. Maybe the version you tried didn't have the correct strings for the MT6572 yet. I believe it worked with Boramir.
Click to expand...
Click to collapse
Any chance you could PM me or mirror the 1.9.4 apk? I can't find it from a reliable resource online, and 1.9.3 did not root my new Neo 4.5. Tried several other rooting tools, none of which worked, so I'd love to be able to get my hands on the apk you used to do the root.
Thanks!
CVAngelo said:
I´'ve rooted several BLUs with Kingo Root (just Google search for it and install it on your laptop). The challenge if you are a noobie is that sometimes you miss a step OR people assume that you know the basics, so they forget to tell you about some important steps that you must take before you root.
Instructions:
1. Install Kingo Root.
2. On your BLU, open Settings (make sure you have allowed applications to be installed from Unknown Sources...you'll find this option under Security in the Settings)..
3. In Settings, go to About Phone and rapidly click on the "Build Number" as many times as it takes to say, "You are now a developer". This will open a new option in the Settings called Developer Options.
4. In Settings, now go to Developer Options and make sure it is ON and also turn on the USB Debugging. VERY IMPORTANT!
5. Now connect your BLU to your computer via a USB cable and wait till all the drivers are installed and the device is READY TO USE.
6. Disconnect your phone from the computer.
7. Run the Kingo Root software.
8. Connect your phone to the computer (Kingo will eventually connect to the phone and then will show you a big ROOT button.
9. Click the big ROOT button and sit back till it does its thing.
10. Wait till Kingo gives you the "ROOTED!" message and then you are done (so go ahead and unplug your phone from USB and close Kingo Root software).
11. Reboot your phone and confirm root (download Busy Box Checker from Play Store). You might also want to download Busy Box X and install the busybox binaries..
OPTIONAL SUPERUSER:
You don't have to do this next part if you're happy with Kingo User.
Note that these days, Kingo Root will install a superuser (su) binary that is controlled by their own app called Kingo User instead of the SuperSU app. If you want SuperSU by Chainfire, you have to search XDA for BETA SuperSU 2.49. You'll find a zip file with a beta version of SuperSU and a script that will eliminate Kingo User and replace it with SuperSU.
Install BUSY BOX X on your phone (download from Play Store).
Place the SuperSU v2.49 zip on your SD card in the phone (IT MUST BE THE VERSION 2.49 NOT THE OFFICIL 2.46 OR THIS IS NOT GOING TO WORK). Then boot into recovery (to do that you turn your phone off and then after it is off, you restart it with the power button while you are holding down the volume UP button). Then you use the menu you find there to "Install a zip from SD card". Select the zip you just put on the SD card, and it will flash the SuperSU program and binaries to your phone, while deleting the Kingo User app and it's binaries. Now select Reboot System at the top of the menu and you're all done.
Click to expand...
Click to collapse
I've tried Kingo Root, One Click Root, iRoot, towelroot, framaroot.... I tried lots of rooting methods
... Watched a lot of YouTube videos. I saw one in Spanish and the neo 4.5 is rooted, but I don't understand, and I'm sure its just a show n not a tutorial on how to root... Any help?
CVAngelo said:
I´'ve rooted several BLUs with Kingo Root (just Google search for it and install it on your laptop). The challenge if you are a noobie is that sometimes you miss a step OR people assume that you know the basics, so they forget to tell you about some important steps that you must take before you root.
Instructions:
1. Install Kingo Root.
2. On your BLU, open Settings (make sure you have allowed applications to be installed from Unknown Sources...you'll find this option under Security in the Settings)..
3. In Settings, go to About Phone and rapidly click on the "Build Number" as many times as it takes to say, "You are now a developer". This will open a new option in the Settings called Developer Options.
4. In Settings, now go to Developer Options and make sure it is ON and also turn on the USB Debugging. VERY IMPORTANT!
5. Now connect your BLU to your computer via a USB cable and wait till all the drivers are installed and the device is READY TO USE.
6. Disconnect your phone from the computer.
7. Run the Kingo Root software.
8. Connect your phone to the computer (Kingo will eventually connect to the phone and then will show you a big ROOT button.
9. Click the big ROOT button and sit back till it does its thing.
10. Wait till Kingo gives you the "ROOTED!" message and then you are done (so go ahead and unplug your phone from USB and close Kingo Root software).
11. Reboot your phone and confirm root (download Busy Box Checker from Play Store). You might also want to download Busy Box X and install the busybox binaries..
OPTIONAL SUPERUSER:
You don't have to do this next part if you're happy with Kingo User.
Note that these days, Kingo Root will install a superuser (su) binary that is controlled by their own app called Kingo User instead of the SuperSU app. If you want SuperSU by Chainfire, you have to search XDA for BETA SuperSU 2.49. You'll find a zip file with a beta version of SuperSU and a script that will eliminate Kingo User and replace it with SuperSU.
Install BUSY BOX X on your phone (download from Play Store).
Place the SuperSU v2.49 zip on your SD card in the phone (IT MUST BE THE VERSION 2.49 NOT THE OFFICIL 2.46 OR THIS IS NOT GOING TO WORK). Then boot into recovery (to do that you turn your phone off and then after it is off, you restart it with the power button while you are holding down the volume UP button). Then you use the menu you find there to "Install a zip from SD card". Select the zip you just put on the SD card, and it will flash the SuperSU program and binaries to your phone, while deleting the Kingo User app and it's binaries. Now select Reboot System at the top of the menu and you're all done.
Click to expand...
Click to collapse
I've attached a photo of my device info. Currently the device is locked to GT&T.
AgentNash said:
I've attached a photo of my device info. Currently the device is locked to GT&T.
Click to expand...
Click to collapse
I really hope that someone can show me how to root this phone
Stone Fist said:
I really hope that someone can show me how to root this phone
Click to expand...
Click to collapse
You still have not rooted your Neo 4.5? Can you give us a little more information? Respond to the following questions:
1. Have you turned on Developer Options on the phone?
2. Have you turned on USB Debugging in the Developer Options?
3. Have you installed the USB drivers for your phone?
4. Download and run MTK Droid Tools (as administrator). Just Google it and you will find lots of sources for the software (including here on XDA). Then connect your phone via USB cable. What message is shown on the bottom left corner of the MTK Droid window? Take a screenshot of your computer screen if possible and post it here.
Once you've answered these questions, we'll be able to help you.
Angelo
It is done
i root it
You have to use the latest version of Kingo root apk. and install it on your phone
Make sure u have the usual Debug mode on and to allow unknown apps ......it is simple and easy
try 360 Roo
Hi, for everyone trying to root blu neo 4.5, I have recently got my phone rooted and had tried all the other root apps out there, but the one that did the job is 360 Root, you can download it from google play store or just google it online and download. you should watch the video on youtube also, it's not in English but will still help you to understand the step by step process.
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
drmarc said:
Hi, for everyone trying to root blu neo 4.5, I have recently got my phone rooted and had tried all the other root apps out there, but the one that did the job is 360 Root, you can download it from google play store or just google it online and download. you should watch the video on youtube also, it's not in English but will still help you to understand the step by step process.
Click to expand...
Click to collapse
so I've got my blu neo 4.5 rooted but there is no custom ROMs online to download, especially lollipop. if anyone knows where I can get custom Rom for blu neo 4.5 please let me know.
I was able to root my Blu Neo 4.5 with KINGROOT
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Lol. I rooted my phone with 360 root. A Chinese app and soon after the phone died because of a faulty charger.

G930P_PF2_Stock_Debloated_ROM

**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930P_PF2_Stock_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930P_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
muniz_ri said:
**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930P_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930P_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Thanks can't wait to try this!
Sent from my SM-G930P using XDA-Developers mobile app
muniz_ri said:
**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930P_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930P_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Any chance this will install on an S7 Edge?
Edit: sorry I am a god D*** idiot I was actually restoring my backup. Hey it works haha. <==== stupid
You rock thanks
Sent from my SM-G930P using XDA-Developers mobile app
keep getting 2 errors upon loading up "Unfortunately, the process com.android.phone has stopped" and "Unfortunately Phone Info has stopped
Do those errors affect the ROM, as in not being usable?
I get the same errors. It makes it almost impossible to complete the initial setup
Sooks said:
I get the same errors. It makes it almost impossible to complete the initial setup
Click to expand...
Click to collapse
Is it possible to get by it tho? I wana try it
I got to the home screen still does it. Don't know the issue and its not exactly easy to start back over lol reflash stock. Root. Try to activate restore lol
Sent from my SM-G930P using XDA-Developers mobile app
I can't get it to work also keep getting phone info not working error that won't go away and can't get through the initial setup.
I will take the rom down until i have a chance to look into the error. Stay tuned...
EDIT: Replaced the ROM with a "non-deodexed," debloated version. It seems the currently available deodexing tools don't work well with this build.
I got it set up and it still does it... gonna have to go back to stock, lol
The problem here may be that whenever the OP put this rom together, he might have taken a application out that the rom needs for the phone to work properly. No biggie, he or she just needs to figure out which app needs to be put back for the error to stop popping up...
Edit: at least that is my take on this situation. Someone can correct me if im wrong...
Sent from my SM-G930P using Tapatalk
sniperkill said:
The problem here guys is that who ever put this rom together took a application out that the rom needs for the phone to work properly. No biggie, he, or she just needs to figure out which app needs to be put back for the error to stop popping up...
Edit: at least that is my take on this situation. Someone can correct me if im wrong...
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
You may be right. I seen he has dropped a few rom. Maybe something that can be debloated from att and tmo has to be left in sprint. Maybe just drop one just deodexed and leave bloat. Just a thought. Hell i dunno I just appreciate the thought for him to give us a rom. Hell dev action is low here.
Sent from my SM-G930P using XDA-Developers mobile app
muniz_ri said:
I will take the rom down until i have a chance to look into the error. Stay tuned...
EDIT: Replaced the ROM with a "non-deodexed," debloated version. It seems the currently available deodexing tools don't work well with this build.
Click to expand...
Click to collapse
This. Debloating is not the issue.
Anyway, the current debloated, odexed ROM in the OP has been tested and seems to be working fine. Also, part of the reason for posting it is to encourage others to use it as a base to begin developing new ROM's.
muniz_ri said:
This. Debloating is not the issue.
Anyway, the current debloated, odexed ROM in the OP has been tested and seems to be working fine. Also, part of the reason for posting it is to encourage others to use it as a base to begin developing new ROM's.
Click to expand...
Click to collapse
Thanks for your time
Sent from my SM-G930P using XDA-Developers mobile app
Got it set up and rooted now restoring backups. I can't seem to find the "hotspot and tethering" setting in the settings. Thanks for helping out the sprint s7 community.
I just installed this ROM but I keep getting the device is activating pop up
---------- Post added at 03:11 AM ---------- Previous post was at 03:10 AM ----------
shooterlgk said:
I just installed this ROM but I keep getting the device is activating pop up
Click to expand...
Click to collapse
Edit: and once it's done the device reboots but when it starts back up it does the whole process again and it just keeps rebooting
shooterlgk said:
I just installed this ROM but I keep getting the device is activating pop up
---------- Post added at 03:11 AM ---------- Previous post was at 03:10 AM ----------
Edit: and once it's done the device reboots but when it starts back up it does the whole process again and it just keeps rebooting
Click to expand...
Click to collapse
After rooting?
Sent from my SM-G930P using XDA-Developers mobile app
sml2004 said:
After rooting?
Click to expand...
Click to collapse
I didnt root right away i got everything set up first but it kept trying to activate so I would let it so it can restore my service but every time it would finish itd reboot and do it all again..then i tried with root and same problem so i had to flash stock thru odin

MEO StarAddict 6 root or firmware

Hello, if anyone could help me with this, I've tried to find firmware for this phone I've read in another thread it's from ZTE but no luck in their website, I want to root or update the firmware if anyone could help, currently the phone is freaking out not working properly. It's from Altice MEO and the name is StarAddict 6.
hello you can easily root your starradict 6 by the app named "KingRoot".
its safe and easy ,the app have his proper's root permissions manager's(exactly like super su) ,and works fine.You can also unroot your device by the KingRoot app too;(if you want to unroot definitively ,factory reset your device is hughly recommended)
For the firmware ,its more hard ,its need to use the DFU mode.
But for now i cant help you for where found the firmware.
one good solution is to make a dump of your firmware,its look like a backup in recovery,for mmake this im sure you can easily find how to make this on xda or google.
im looking for the firmware too ,if i found how and where to download it ,i post here for the starraddict community users.
friendly
I found the firmware boys
https://drive.google.com/file/d/1qIgNdLwDc5p6WxrohIwIjpvheBCe6nKR/view
neves2k said:
I found the firmware boys
https://drive.google.com/file/d/1qIgNdLwDc5p6WxrohIwIjpvheBCe6nKR/view
Click to expand...
Click to collapse
Found the password. I looked up the file name on google and it lead me to firmware247 which had the password there. (It's https://firmware247.com).
How to unbrick:
Get any SDCard on your PC and paste the l730.v1 folder inside the root of the sdcard.
Put it back on the phone.
While pressing both Vol +, Vol - press Power Button.
This will put you into the "recovery mode" (if you can call it that...) which will read the files and install them
If you've reached this far hopefully your phone is working again
ROOT with Magisk:
Download and install Dr. Fone root tool (make sure it's the root tool and not the management/backup tool)
Go into phone developer settings and enable OEM Unlocker and USB debugging
Root the phone with Dr. Fone root tool (it will ask to install supersu, accept it)
When you open supersu, DO NOT UPDATE THE BINARIES, or you will go into bootloop (happened to me at least)
Install magisk manager apk
Open magisk so you get the prompt to allow on it supersu
Restart magisk and super su app (for some reason some options don't appear on magisk if you don't do this)
Download and install (patch) magisk to directly.
Reboot as prompted by the tool.
Open supersu and go into options.
Select delete supersu and remove "root" (you will need to allow supersu root permissions on magisk)
That's it, you now have your phone rooted with magisk.
Unfortunately I wasn't able to find a way to fix safety net, please let me know if you do. (CTS Profile is flagged)
Edit: Organized the post and added small guide.

Tutorials Wanted On Using The New Magisk App 22.0

Hello:
I've never used Magisk before, so I am trying it out for the first time.
I've downloaded and installed the new app, 22.0, but I am not sure if everything is perfectly done.
After installation, I am put on the home page, and there I find magisk install button, installed. Setting, n/a a/b no ramdisk yes S/R noapp install button 22.0 22000 18 installed.
Then I tap on the safety net and this is what I seel SuccessBasicIntegrityctsProfileEvalTypeBASIC When I scroll to the right, I see try again button.
When I tap on the install button on the right of the home page, I see Options: method then preserve ADB 2.0 for DM verity check box not checked, and and then preserve forced encryption checkbox checked.
When I explore the next button, I find option, I find method, download pache file. and then on the right, I find lets go button, unavailable.
Please kindly help me to understand all these.
What am I not doing properly, and how can I properly get the app to work.
I am actually blind, and I use a screen reader to access the phone.
Finally, how will I use the app to root my phone. I use a Samsung Galaxy Grand prime J2 phone.
Hope my issue is very well understood.`

Categories

Resources