Related
Hey guys,
I am new to flashing and rooting and stuff and am needing some help with all this. I'm kinda getting lost in the forums, reading all this stuff I have a stock Vibrant that i want to root and put a Froyo rom on it. I am currently on 2.1 of course. Can anyone kinda guide me through this?
Thanks!
I would suggest starting here:
Vibrant Guides
And here:
Newb Guide
Get the basics and understand what you will be doing. These guides can help you allot. If then you still don't understand then come back with a more specific question.
Good luck and have fun!
everything is here hxxp://forum.xda-developers.com/showthread.php?t=732458 (change xx for tt). read, its good for you
Thanks guys, I'm going to have to read this more carefully apparently. Let me ask this before i do anything to the phone. What backup program should i get if i need to restore it back to stock everything? I want to make sure i have that done before i try any of this. I've done Iphones and stuff, unlocking them and jailbreaking them, those were a piece of cake, but never done a custom rom on an android phone before, nor have i ever rooted one. so im kinda nervous at all this
you should make a nandroid backup, that will be a failsafe but your lifesaver will be odin. when you think you bricked your phone it will rise from the grave. i love odin
sisco22 said:
Thanks guys, I'm going to have to read this more carefully apparently. Let me ask this before i do anything to the phone. What backup program should i get if i need to restore it back to stock everything? I want to make sure i have that done before i try any of this. I've done Iphones and stuff, unlocking them and jailbreaking them, those were a piece of cake, but never done a custom rom on an android phone before, nor have i ever rooted one. so im kinda nervous at all this
Click to expand...
Click to collapse
Use Odin to get back to Stock. The Bible in the Development thread has the links for Odin download, also the links for the stock android ROMs to odin back to. Make sure you can get into the Download mode before doing anything. Especially using your hardware keys. (to verify that your phone is not hardware locked). If it is you have to install the JI6 to get the hardware key issue fixed.
Also read the wiki page http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959
my noob guide (signature) has videos... you can use your pc (ODIN) and have a rooted 2.2 phone in like 2 minutes!
sisco22 said:
Hey guys,
I am new to flashing and rooting and stuff and am needing some help with all this. I'm kinda getting lost in the forums, reading all this stuff I have a stock Vibrant that i want to root and put a Froyo rom on it. I am currently on 2.1 of course. Can anyone kinda guide me through this?
Thanks!
Click to expand...
Click to collapse
Hey bud. If you need some visual help, I should have my videos up by tonight and ready for viewing tomorrow morning. I've dubbed it my choose your own samsung vibrant adventure, so hopefully you can see what it looks like and get your questions answered.
thanks guys, the videos are a big help. 2 things that im trying to find is the Odin download and the Nandroid download. Can't seem to find a link for those.
^ the noob guide has a link to download ODIN (and the files needed).
The ALT METHOD listed is Froyo with root already enabled... doesnt get much easier! It's in my signature, or the sticky in the Q&A section.
Also, to clarify, once you use ODIN and flash this (which gives you froyo+root) you can download Rom Manager from the market.... you use it to instal clockwork recovery.... you use clockwork recovery to make a nandroid backup of your system. You can't do this until you have root.
This link should get you to where you can download what you need:
http://forum.xda-developers.com/showthread.php?t=771111
^ to even make it THAT much easier.... here is the thread that I was referencing (and is in the sticky)
http://forum.xda-developers.com/showthread.php?t=799105
s15274n said:
^ to even make it THAT much easier.... here is the thread that I was referencing (and is in the sticky)
http://forum.xda-developers.com/showthread.php?t=799105
Click to expand...
Click to collapse
Thanks! I was looking at it and i found this link http://forum.xda-developers.com/sho...ost in all this stuff haha! its alot of info.
^ please read both sticky's in my signature before you proceed. If you read those, this is very straight-forward.
You would need to root and download rom manager
install clockwork recovery
move the .zip to sdcard/ (internal memory)
reboot into recovery
flash the file
reboot
but please read my guide... if it doesnt make it obvious, please let me know what needs to be updated.
s15274n said:
^ please read both sticky's in my signature before you proceed. If you read those, this is very straight-forward.
You would need to root and download rom manager
install clockwork recovery
move the .zip to sdcard/ (internal memory)
reboot into recovery
flash the file
reboot
but please read my guide... if it doesnt make it obvious, please let me know what needs to be updated.
Click to expand...
Click to collapse
Thanks for your help! I finally understand all of it. Apparently the Flash Clockworks didn't install correctly...so when i tried to open the zip it would open. I installed Axura on it just now and it looks like its running smoothly! Thanks for everyone's help and sticking with me!
I froze this app because I decided I would try freezing some apps and was going by the thread on here that has a big list. When I froze this app my phones email and calendar stopped working. I tried unfreezing it and instead of it going back to the app list it just seemed to disappear, it was no longer in the frozen list or the app list. So I just tried a factory reset and now I can't do anything as the phone I keep getting force closes on Accounts, is there anything I can do?
If you REALLY want to stay blurred, go with a fruitcake:
http://forum.xda-developers.com/showthread.php?t=1163009
Otherwise, improve your phone by going with one of the many nice ROMs in the Dev section. Neutrino/Joker's CM9 are my favorites.
And in case you aren't all ROMtastic yet, unlock your bootloader (MAKE SURE THIS IS OK FOR YOUR BLURRED SELF FIRST. I HAVE NOT BEEN KEEPING UP WITH 2.3.6 ISSUES AS I LEFT BLUR A LONG TIME AGO), flash Romracer's most recent recovery, and then flash the CWM zip for whatever ROM you go for.
If you end up bricking yourself, this may or may not be useful:
http://forum.xda-developers.com/showpost.php?p=22583493&postcount=139
well it isn't an issue of a new rom or anything I want, my phone is unusable right now because I froze the blur.res 2.3.6, and with the factory reset I can't do anything because the second it comes on I get force closes on 'Accounts'
And my suggestion is flash a new ROM. If you are concerned about keeping your data, try an adb pull of whatever you want to hang on to.
Oh, and try adb install (ing) the specific apk you froze (grab it from the /system/app under the fruitcake for your ROM).
ohhh haha sorry I misunderstood, but I guess I'll give it a try if it's really all I can do. I'll try to find the apk from the fruitcake rom first though and see if I can do that first, is there any link for how to do an adb install? Thanks!
I just read that people who OTA'd to 2.36 without unlocking earlier have lost the ability to do so. Just regurgitating, again I unlocked forever ago and don't worry about ATT's ball and chain anymore.
---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------
Flaresaint said:
ohhh haha sorry I misunderstood, but I guess I'll give it a try if it's really all I can do. I'll try to find the apk from the fruitcake rom first though and see if I can do that first, is there any link for how to do an adb install? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=532719
Crap, so best option right now would be to unlock the bootloader and load up a custom rom?
Flaresaint said:
Crap, so best option right now would be to unlock the bootloader and load up a custom rom?
Click to expand...
Click to collapse
No what I read says people on your version (2.36) can't unlock. You should verify this by reading around.
---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------
Just a quote... Don't hold ME accountable.
Dark9781 said:
The only way currently to root a phone on 4.5.141 is to use the fastboot method. The procedure and files can be found here:
http://briefmobile.com/motorola-atrix-4g-root
As for unlocking, I've been told that the old method for 4.5.91 works on 4.5.141. It can be found here:
http://forum.xda-developers.com/showthread.php?t=1182871&highlight=unlock
Romracer's recovery can be found here:
http://forum.xda-developers.com/showthread.php?t=1204500
Click to expand...
Click to collapse
In this post http://forum.xda-developers.com/showthread.php?t=1182871 people say it worked for them hopefully it will for me too, thank you for all the help
Flaresaint said:
In this post http://forum.xda-developers.com/showthread.php?t=1182871 people say it worked for them hopefully it will for me too, thank you for all the help
Click to expand...
Click to collapse
No problem, man. Let the community know how it goes, and for future reference, use the Thanks button (I don't care too much haha). Welcome by the way. A well-asked first post, though it should have been in Q+A
Haha and I will post again with results probably tomorrow
Okay i'm back and very pleased, I unlocked the bootloader with the automatic script tool linked earlier and then used the script for Tenfars recovery in it as well. After that, since I couldn't actually get on the phone to update CWM I just went ahead and tried flashing a ROM. I used Gingermod, I wanted to try Neutrino ROM but I couldn't get to the download links for some reason, anyway Gingermod is now installed (after trying the tegrapart 1100 kernel, I didn't know which one I have so I tried that one after looking at some forums saying most ATT Atrix's are 1100). I had everything backed up with Titanium Backup previously so restoring all my apps was simple, and everything seems good so far thanks again to omni_angel7!
Flaresaint said:
Okay i'm back and very pleased, I unlocked the bootloader with the automatic script tool linked earlier and then used the script for Tenfars recovery in it as well. After that, since I couldn't actually get on the phone to update CWM I just went ahead and tried flashing a ROM. I used Gingermod, I wanted to try Neutrino ROM but I couldn't get to the download links for some reason, anyway Gingermod is now installed (after trying the tegrapart 1100 kernel, I didn't know which one I have so I tried that one after looking at some forums saying most ATT Atrix's are 1100). I had everything backed up with Titanium Backup previously so restoring all my apps was simple, and everything seems good so far thanks again to omni_angel7!
Click to expand...
Click to collapse
No problem, man. Glad it worked out for you. I'd give neutrino a chance when the links work for you again. Welcome to ROMaholics anonymous! Oh, and to prevent any future error, make sure to get ROMRACER's recovery (recommended) or the most recent CWM. Tenfar's is outdated AFAIK.
Yeah, I heard that as well so I updated CWM with ROM manager. And I found a download for Neutrino so I have it saved on my computer currently, I'm going to wait a few days though and just see how Gingermod goes (since it's smooth and the battery seems good so far)
Hey there. I rooted my Vibrant successfully, but realized I left some important things out. I used this guide to root my Vibrant: http://forum.xda-developers.com/showthread.php?t=723479
The problems:
1) I can't nandroid (not that I need to, I only have 4 apps)
2) I would like to install either Miui v4 or CyanogenMod 9 but cannot as my recovery screen does not show me the options to do so (I only get the 4 options you normally would get unrooted, such as "Reinstall Packages"), so I'm stuck with the lame default homescreen.
3) I'm currently on 2.1-update1; should I upgrade to 2.2? If so, must I unroot to upgrade, and then reroot? And if this were the case, how do you unroot, and can I reroot using the same method in the link above?
Also, I was looking at this guide: http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery
and noticed the line "This guide assumes the Samsung Vibrant already has Android 2.2 build UVKB5 already installed on it."
Does this mean 2.2 is required to install the CWM Recovery?
Thank you.
I'm not sure how you don't have CWM recovery if you followed the guide as it is written. Maybe its because the 2.1 is updated? I would do the following and see if that's all it takes. You definitely don't want to update to stock 2.2 via Kies or anything of that nature.
Worst case scenario, we can have you Odin back to stock JFD. You'll be smooth sailing from there.
Search the forums and find the update.zip for CWM for our Vibrant.
Put that on the lowest level of your INTERNAL storage. Not your microsd card. For example f:\update.zip
Now go to your boring 4 option stock recovery and select reinstall packages. It will reboot to the same boring screen. Select reinstall packages again, and it will reboot into Clockwork Mod Recovery.
Let me know if that does anything for you. Also what version of stock recovery do you have?
Toast6977 said:
Search the forums and find the update.zip for CWM for our Vibrant.
Click to expand...
Click to collapse
Can pull that directly from my signature, if OP wants. (Only works on Eclair [JFD] build btw)
Also OP, You will have to have a ROM that you are going to want to flash saved on your Internal SD card. Jsut download it, put in a folder and follow the ROM OP's instructions. Since you are fresh and new, I would NOT suggest flashing anything of ICS or JB until you get the hang of things first.
Read, read and then read somemore. When it comes time to flash ICS or beyond, there is a guide in my signature. Good luck and make sure to hit Toast's "Thanks" button. He is a good asset to have around here.
Wow! I was hesitant to even check today, let it alone this early! Did not think that I would have two very useful replies waiting for me. Thanks guys, much appreciated!
I'll try the Odin thing out first before I even try to flash (you need root first before flashing, I'm assuming). Just out of curiosity, what is JFD and Odin? I'm still gonna try it out using the guides found here, but just curious.
EDIT: Damn, it worked like a charm! Now I have CWM. The mistake I made was that I only installed the Superuser/ROOT and not both. Gonna play with it for a bit now
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Toast6977 said:
I'm glad that your issue was solved
If you have any other questions/issues feel free to hit us up. We tend to lurk around these parts from time to time.
--you could now modify the title of this post to add [Solved] to the title or contact Oka1 and let him know it's case closed.--
Click to expand...
Click to collapse
Thank you for teaching me the etiquette around here as well
Sorry for asking this question. I am guessing that it has been answered a number of times, but I can't seem to find anything recent or usable.
I have an S4 running 4.4.2
Baseband L720VPUFNG2
Kernel 3.4.0-2162929
Build KOT49H.L720VPUFNG2
I have been attempting to root it, but any of the information I am finding is pre-current updates. Is there a way to root this, or am I too late to the game? I have spent the last 3 days reading up, going to different forums, checking Youtube, etc. but I haven't located anything.
Any advice?
Brian
C.f. auto root. This will trip the Knox flag.
Thanks for the quick reply
I jumped on your advice and ran with it. Ran Root Checker and it looks like I have root access.
Thanks again for the advice.
Custom recovery
As an aside, with the cf auto not coming with a custom recovery, which would be the best to install here? Or should I just leave it stock?
BinstRagu said:
As an aside, with the cf auto not coming with a custom recovery, which would be the best to install here? Or should I just leave it stock?
Click to expand...
Click to collapse
TWRP or Philz Touch are the ones most liked. But really it's up to you and what you're most comfortable with.
Hey, which one did you use? I went here:
http://autoroot.chainfire.eu/
but didn't find one for KOT49H.L720VPUFNG2
BinstRagu said:
I jumped on your advice and ran with it. Ran Root Checker and it looks like I have root access.
Thanks again for the advice.
Click to expand...
Click to collapse
I am pretty sure this is what I used.
I am trying to get you the information, but xda is being annoying as hell. I can't share a link or post an image or do anything to get you the name of it.
Google search this: Root L720VPUFNG2 Android 4.4.2 Stock Firmware On nasirtech
It should be your first return.
Hey, thanks
Actually, I had previously found that source, but the download file seemed tied to build KOT49H.L720VPUFNAE, so I was nervous about applying it. But sounds like it worked for you, so I'll give it a try
BinstRagu said:
I am trying to get you the information, but xda is being annoying as hell. I can't share a link or post an image or do anything to get you the name of it.
Google search this: Root L720VPUFNG2 Android 4.4.2 Stock Firmware On nasirtech
It should be your first return.
Click to expand...
Click to collapse
BinstRagu said:
I am trying to get you the information, but xda is being annoying as hell. I can't share a link or post an image or do anything to get you the name of it.
Google search this: Root L720VPUFNG2 Android 4.4.2 Stock Firmware On nasirtech
It should be your first return.
Click to expand...
Click to collapse
Thank you for this! Successfully rooted my S4 on Sprint!
Glad I could help. It feels nice to contribute.
I installed TWRP and ran nandroid to restore my apps and SMS from by backup.
TWRP comes with a nice stock looking wifi hotspot.
I just have to personalize all my settings and I am back on track.
Odin won't work
BinstRagu said:
Sorry for asking this question. I am guessing that it has been answered a number of times, but I can't seem to find anything recent or usable.
I have an S4 running 4.4.2
Baseband L720VPUFNG2
Kernel 3.4.0-2162929
Build KOT49H.L720VPUFNG2
I have been attempting to root it, but any of the information I am finding is pre-current updates. Is there a way to root this, or am I too late to the game? I have spent the last 3 days reading up, going to different forums, checking Youtube, etc. but I haven't located anything.
Any advice?
Brian
Click to expand...
Click to collapse
I have the same phone and Odin hangs on "Get PIT for mapping.. ". Can't get past this with any Odin attempt. Small print on phone says "WRITE PROTECTION: Enable"
Any Ideas ?
Actually, one more question: did this rooting method wipe your data? Instructions indicate a lot flashing going on. Thanks!
BinstRagu said:
Glad I could help. It feels nice to contribute.
I installed TWRP and ran nandroid to restore my apps and SMS from by backup.
TWRP comes with a nice stock looking wifi hotspot.
I just have to personalize all my settings and I am back on track.
Click to expand...
Click to collapse
kunchers said:
Actually, one more question: did this rooting method wipe your data? Instructions indicate a lot flashing going on. Thanks!
Click to expand...
Click to collapse
Let me think about what I did here.....
The autoroot itself did not. I installed it and it was all normal. My next steps could be ill advised and all over the place, but what I did was:
Installed JS backup and created a backup to the PC.
I like having that assurance just in case I break anything along the way.
Then I installed the TWRP recovery and let it run through everything. I have always been taught to wipe my dalvik, user, etc. cache when I am installing anything. So I did the wipe. After everything was installed fresh, I went back in and got nandroid backup and restore and was able to pull my JS backup data in, recreating my SMS log, my call log, etc. The only issue that I ran into, which isnt even a big issue, is that it cleared out my apps that I had installed. They mostly all errored out when trying to reinstall them via Nandroid.
I think that I could have probably used Titanium Backup once I got the initial autoroot done. I was just all over the place with it because I was burnt out from searching for answers for the past week or so.
betoweb said:
I have the same phone and Odin hangs on "Get PIT for mapping.. ". Can't get past this with any Odin attempt. Small print on phone says "WRITE PROTECTION: Enable"
Any Ideas ?
Click to expand...
Click to collapse
What version of Odin are you using and did you get the correct root file? I know that each of these sets of instructions runs with different Odins and I found that depending on the installation attempt, it was important to use exactly what the instructions stated. So if someone is posting to use v1.85, that is the one to use. Please remember that I am not at all an expert on this. I just seem to be the first guy who recently got lucky enough to assemble the pieces and successfully push this thing onto a phone. I also had the PIT mapping problem, until I followed the link that posted the other day and followed the instructions exactly. Also, make sure that you are using your real Samsung cable, you are running it directly to your pc, and your usb port is good. Also, make sure that you have your Samsung drivers installed on the pc.
Root File
Where did you find the correct root file ?
I see now that I have KOT49H.L720VPUFNAE not KOT49H.L720VPUFNG2.
I have looked for a week. I have been looking for a week.
betoweb said:
Where did you find the correct root file ?
I see now that I have KOT49H.L720VPUFNAE not KOT49H.L720VPUFNG2.
I have looked for a week. I have been looking for a week.
Click to expand...
Click to collapse
It is all in this thread. I cannot share links, so you will have to do the legwork on that one. If you google search what I entered previously, you should see your version in the list of headers.
***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