Related
Hello.
I try different way to root nexus but I have no lucky.
To root I use superboot.
In first i update on ERE36B.
After i use superboot ere36b himem.
It install but superpermission doesen't work.
I try to reflash wwith ERE36B upgrade (with RA-nexus 1.5.3).
Retry superboot but same result.
I try to downgrade to ERE27, same problem.
I try to restore ERD79, superboot. Same problem.
Now I try to reupgrade to ERE36B but I think there is a permission problem on my Nexus.
Anyone can help mo to root my Nexus?
Thanks
have you installed the usb drivers? ive got the same problems, then i installed them and anything worked
biggerbigboy said:
have you installed the usb drivers? ive got the same problems, then i installed them and anything worked
Click to expand...
Click to collapse
Yes.
I also try the develop mode on application but the problem not solved.
Now I try on mac.
www1 said:
Yes.
I also try the develop mode on application but the problem not solved.
Now I try on mac.
Click to expand...
Click to collapse
forget the superboot.... i mean, if you don't mind to go for cyanogenmod ROM, the steps are very simple:
1) unlock bootloader
2) flash amon_ra (i think you have done that)
3) flash latest radio (i think you have done that too, otherwise, can obtain from cyanogen's thread)
3) flash cyanogenmod 5.0.3.1
4) flash google bits (can obtain from cyanogen's thread)
then you should be good to go.... i never used superboot, but then I am a heavy cyanogen fan, so that's all i needed
pm me if you need more help... i am however in China. here it is 10:16pm now, so i may be gone in an hour or so
www1 said:
Yes.
I also try the develop mode on application but the problem not solved.
Now I try on mac.
Click to expand...
Click to collapse
by all means, you have to keep the "development mode" (= debugger) enabled at any time when working with customized roms
shmigao said:
by all means, you have to keep the "development mode" (= debugger) enabled at any time when working with customized roms
Click to expand...
Click to collapse
I know.
I have it all time enabled
The problem is that I can't root the Nexus.
I try different way but nothing.
Anyone can wrote me a guide to restore completly the phone and after try to root?
Superuser Permission start but are black and doesn't work.
I try many reflash but same problem.
have try with dev mode or not.
Nothing change.
Plese help me.
www1 said:
I know.
I have it all time enabled
The problem is that I can't root the Nexus.
I try different way but nothing.
Anyone can wrote me a guide to restore completly the phone and after try to root?
Superuser Permission start but are black and doesn't work.
I try many reflash but same problem.
have try with dev mode or not.
Nothing change.
Plese help me.
Click to expand...
Click to collapse
please tell me at what step are you right now? do you have amon_ra recovery? can you go into recovery?
hi there.
since this thread is in the totally wrong section of the forum (it should be in Nexus General, i am afraid it will be closed by the moderators soon.
so you can send me Private Message - i will try to help
shmigao said:
please tell me at what step are you right now? do you have amon_ra recovery? can you go into recovery?
Click to expand...
Click to collapse
Yes.
Now I have upgrade to ERE36B with amon ra, I have launch superboot and I have superpermission on Nexus but It not work.
I think I have to restore the Nexus to all original setting and rom (radio i think it's not important) and after do all update and rooting.
I think there is a problem that can be solved because I made only upgrade with Amon ra.
www1 said:
Yes.
Now I have upgrade to ERE36B with amon ra, I have launch superboot and I have superpermission on Nexus but It not work.
I think I have to restore the Nexus to all original setting and rom (radio i think it's not important) and after do all update and rooting.
I think there is a problem that can be solved because I made only upgrade with Amon ra.
Click to expand...
Click to collapse
i don't understand why you want to stay with superboot... i never needed it.
to get root, just do this:
1) download the cyanogenmod rom (5.0.3.1) from the cyanogenmod thread
2) download the google apps from the same thread
3) put both on your sdcard
4) in amon_ra, flash cyanogenmod rom first
5) reboot
6) reboot into amon_ra recovery
7) in amon_ra, flash google apps
8) reboot
then you should be good to go and should have root
after that you can flash other roms, if you don't want to stay with cyanogen's rom
solved
1. this is related to roms not general.
2. its resolved, so its ok if anyone moves it.
3. superboot is very easy. no command line. just click install.
4. Best of all... PROBLEM SOLVED
For those of you still having trouble, before doing anything to technical, just boot to the recovery image and hit wipe device. then reinstall whatever rom.
worked like a charm for me.
also thanks to you all for quick responses. i got 6 in like ten minutes. here in texas, its like 9am on Sunday lol. I love xda.
are you the OP or is www1 the OP?
it seems like www1 still has the problem or not???
i agree, this is general, not development thread. but i am trying to help the OP.
i am sure superboot is a good tool, i just saw so many confused people at the beginning with it... and i never needed it, so
Sorry, I'm Italian and I can't speak english very well.
Not I try to flash with cyanogen mod to have the root (I hope) and after I reflash with standard rom.
I always do a wipe but the problem are not resolved.
I hope the mod can move this tread if is in the wrong section.
Thanks for the help.
So I think there are a permission problem.
ANyone can suggest how to manually install super boot? By insecure image boot for example.
www1 said:
Sorry, I'm Italian and I can't speak english very well.
Not I try to flash with cyanogen mod to have the root (I hope) and after I reflash with standard rom.
I always do a wipe but the problem are not resolved.
I hope the mod can move this tread if is in the wrong section.
Thanks for the help.
So I think there are a permission problem.
ANyone can suggest how to manually install super boot? By insecure image boot for example.
Click to expand...
Click to collapse
sorry... then i can't help you, because i never worked with superboot.
THanks
I don't know how but problem solved.
Now It work.
www1 said:
THanks
I don't know how but problem solved.
Now It work.
Click to expand...
Click to collapse
perfect
Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead
NOTE: THIS IS MY FIRST POST ON XDA, HOPE YOU WILL ENJOY
NOTE: ALL THE FILES ARE ACTUALLY NOT MINE, AND ALSO I DONT KNOW WHO THEY BELONG, THIS POST IS ONLY FOR TUTORIAL
THIS TUTORIAL WILL SURELY WORK ON XPERIA Z C6602(MY DEVICE), IF YOU FOLLOW THE STEPS CORRECTLY
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY MISHAPPENING TO YOUR PHONE AND YOUR HEART
THIS TUTORIAL WILL HELP YOU TO GET ROOT USING KINGROOT AND THEN REPLACING KINGROOT WITH OUR BELOVED SUPERSU :laugh:
1. FIRST OF YOU WILL NEED KINGROOT APP. (LATEST ONE WILL BE BETTER)
(as I am a new user, I am not allowed to post outside links, so plz find uself on google)(its easily available)
2. INSTALL IT ON UR DEVICE.
3. OPEN AND LET IT BE PROCCESSED.
4. TAP ON "START ROOT", MAKE SURE YOUR DATA IS ON.
5. LET IT BE FINISHED, SOMETIMES IT FAILS BUT DONT WORRY TRY AGAIN, IT WILL WORK.
6. AFTER COMPLETION, DOWNLOAD "ROOT CHECKER BASIC" APP FROM PLAYSTORE(ITS FREE).
7. GET YOUR SUCCESS RESULT. :fingers-crossed::good:
8. NOW, IN ORDER TO GET "KINGROOT" REPLACED WITH "SUPERSU", DOWNLOAD
----> TERMINAL EMULATOR APP (FREE)(PLAYSTORE)
---->ATTACHED FILE(S)
9. UNZIP THE ATTACHED FILE INTO YOUR INTERNAL MEMORY(NOT IN ANY FOLDER).
10. OPEN TERMINAL EMULATOR APP
---->TYPE
Code:
su
---->GRANT PERMISSIONS
---->TYPE
Code:
sh /sdcard/mrw/root.sh
11. LET IT BE FINISHED. (DONT WORRY IF PHONE HANGS OR LAGS OR RESTARTS, DO A MANUAL RESTAR)
12. AFTER THIS UPDATE SUPERSU BINARIES USING NORMAL MODE(PREFFERED).
13. REBOOT ON SUCCESS, UNINSTALL KINGROOT IF ITS NOT GONE AUTOMATICALLY.
14. DONE, CHECK YOUR ROOTING RESULT USING ROOT CHECKER APP.
:good::good::good:
ALL THE VERY BEST...
YOU CAN ALSO GET THIS TUTORIAL IN THE FORM OF SEQUENCED IMAGES(BETTER TO UNDERSTAND), DOWNLOAD IMAGES ZIP FOR THAT.
IF YOU LIKE MY WORK PLZ DO NOT FORGET TO PRESS THANKS BUTTON, IT WILL NOT COST YOU MORE THAN YOUR HAPPINESS
NOTE: AS I AM A NEW USER, I CANT SHARE LINKS, PLEASE COPPY THE URL AND ADD "h" TO HTTPS
FILES:
----> ZIP ttps://drive.google.com/open?id=0B6JGe-_gG3ftX2JJU1pWd2xobDg
---->IMAGES ttps://drive.google.com/open?id=0B6JGe-_gG3ftazBsRHBsQ3E5dFU
AN IMPORTANT NOTICE.
This is only for stock.
It will not work on other custom roms.
A guy commented on the post, after trying this method on existence rom.
See below.
Anyways this method I personally tested by me, it works fine. :good:
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-xperia-z-android-5-0-t3151618
you really had to make new thread bout it ?
indycar said:
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-xperia-z-android-5-0-t3151618
you really had to make new thread bout it ?
Click to expand...
Click to collapse
Dear
The method of using "supersume", doesn't work surely. I tried it personally.
And the other link u provided is for replacing kingroot with supersu only.
I made this thread for people to get the whole procedure at the same place, no need to Google more.
Hope you understand ?
And ur question is really appreciated ?
Sent from my C6603 using XDA-Developers mobile app
Doesn't work for me. Did everything exactly like you said, but trying to update supersu binaries didnt work.
I then rebooted and got a soft brick until I wipe dalvik and cache from recovery.
Natschlaus said:
Doesn't work for me. Did everything exactly like you said, but trying to update supersu binaries didnt work.
I then rebooted and got a soft brick until I wipe dalvik and cache from recovery.
Click to expand...
Click to collapse
Bro now tell me, is that problem still exists.
If yes.
U can just flash system using Twrp backup.
And then follow the procedure again but with a new version of kingroot.
Bro this method is personally used by myself, and always works for me. You can check the images.zip file. That is my own phone.
No fake things, my only motive.
????
What do you mean does it still exist. I literally just tried it yesterday.
I used the newest version of Kingroot and still that happened, but then again I dont use stock rom so that is probably interfering with it.
I probably just stick with Kingroot, it doesnt seem so bad.
Natschlaus said:
What do you mean does it still exist. I literally just tried it yesterday.
I used the newest version of Kingroot and still that happened, but then again I dont use stock rom so that is probably interfering with it.
I probably just stick with Kingroot, it doesnt seem so bad.
Click to expand...
Click to collapse
As u wish bro.
And u can stick to kingroot.
Happy root to u btw.
And being an xz user, u can join WhatsApp group for xz, there u can find the solution (same as above, many people did like this only)
Or find another thread.
????
Tried this method. The phone was stuck at the bootanimation. I forced restart it and now it is stuck at the App Optimization page.
C6002, 5.1.1, Bootloader Locked, Completely Stock. Any help?
dj.adil said:
Tried this method. The phone was stuck at the bootanimation. I forced restart it and now it is stuck at the App Optimization page.
C6002, 5.1.1, Bootloader Locked, Completely Stock. Any help?
Click to expand...
Click to collapse
Bro try to wipe dalvik cache in twrp. Otherwise the method is sure shot.
If the problem still persits then tell me how you did, i will try to simukate the same to find best solution as possible.
Thanks
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards