[Q] Paranoid Android 3.97 - Nexus 4 Q&A, Help & Troubleshooting

Hi,
I have looked but can't find anything on here although I am sure it is here somewhere...
Anyways, loaded the above with gapps 4.3 and consequently titanium backup will not restore batch process at all and wont back up although it states it has been given superuser permission. Is there any work around or something I need to do?
Any help would be appreciated as I rely on TB when rooting and restoring software.
Many thanks.

kumaman said:
Hi,
I have looked but can't find anything on here although I am sure it is here somewhere...
Anyways, loaded the above with gapps 4.3 and consequently titanium backup will not restore batch process at all and wont back up although it states it has been given superuser permission. Is there any work around or something I need to do?
Any help would be appreciated as I rely on TB when rooting and restoring software.
Many thanks.
Click to expand...
Click to collapse
Try this thread.

Cheers
Many thanks, just checked the list and there is another post a few down with the fix very similar to your link. All sorted now, feel much happier

Related

Original Rom - Nandroid Backup?

I hate to ask this, but anyone got the original slide rom nandroid backup?
I ran it on mine, and it seemed to work, but now the file is missing and I have a blank sd card. I'm not too worried about the other data lost, but the loss of the restore file is kind of annoying.
I saw a link posted on another thread here somewhere. I have seen so many trying to root this phone that I don't remember exactly. I believe it was the how to root 6/15/10 thread. Sorry not much help but that should narrow your search.
my bad, here's what I saw and thought it was what you were looking for but I don't think it is:
http://forum.xda-developers.com/showpost.php?p=6828065&postcount=21
I haven't seen anything completely stock 100% yet up here. Good idea though just in case you need it like you do.
I have a new mytouch slide arriving tomorrow and i'm going to take a clean nandroid dump of it. I can put it up and post a link if you still need it.
Yes,
Please if you don't mind, thanks. Never know if we need to go back to stock. Thanks.
Please and thank you!
Good deal Falken. Thanks in the advance for up
No problem, look for it tomorrow night!
I just finished root and installed Titanium backup and grabbed a complete dump of my virgin rooted system.
Not sure if this is the same as nandroid's backup though.
nope. we need the nandroid backup before rooting. Just in case you have to return it, or some such.
Any luck getting this yet?
Not sure if you meant unrooting your phone to flash back to the stock rom, but so far it looks like falken98 was nice enough to make a Stock (rooted) backup for the Slide, so you can flash this if you want all you "stock" feel.
http://forum.xda-developers.com/showthread.php?t=705345

[Q] note 3 beginner questions before custom rom install

Hi,
I am looking at flashing some custom roms to see which one I like, I have got root by using the cf-auto root by cahinfire but, before I begin I just want to make sure that I back every thing up correctly to avoid any trouble further down the line.
As I understand it ( I use the term 'understand' loosely ) I need to back up the EFS folder and imei
Is that all that is needed? or is there something else that i should do? essentially I would just like to ensure that I can revert back to a stock rom, im not that concerned about knox or warranty. Im sorry if this has been brought up before but as a novice I would appreciate some assistance in gaining a proper understanding of the requirements before starting off
thanks
Backing up EFS has it's pros and cons - I done it, but then I got a mess up, and restoring my EFS did not work. I had to run the fire script posted in the dev section (this script rebuilds your EFS partition so it can be read properly again) - I have seen countless users brick their devices by backing up EFS with bad/rogue apps, so if you go this method, choose very very wisely.
My advice, install CWM, and make a back up via that. - it'll see you right. - If by chance you do get a mess up, you can run the fire script by firausman in the dev section and it'll fix unknown baseband and bootlooping errors.
Ultimately, I cannot stress that you read as much as you can and are aware of the potential what can and does happen, what cannot happen and ultimately can you fix it if something does go wrong.
EDIT:: here is the SCRIPT if you do indeed need it, keep it on your extSD Card for just in case reasons.
radicalisto said:
Backing up EFS has it's pros and cons - I done it, but then I got a mess up, and restoring my EFS did not work. I had to run the fire script posted in the dev section (this script rebuilds your EFS partition so it can be read properly again) - I have seen countless users brick their devices by backing up EFS with bad/rogue apps, so if you go this method, choose very very wisely.
My advice, install CWM, and make a back up via that. - it'll see you right. - If by chance you do get a mess up, you can run the fire script by firausman in the dev section and it'll fix unknown baseband and bootlooping errors.
Ultimately, I cannot stress that you read as much as you can and are aware of the potential what can and does happen, what cannot happen and ultimately can you fix it if something does go wrong.
EDIT:: here is the SCRIPT if you do indeed need it, keep it on your extSD Card for just in case reasons.
Click to expand...
Click to collapse
Thanks for the reply and advice Radicalisto.
I will check out CWM and how and what that backs up. If I take a guess now it will make an image of my current system that can be restored? If so does that ensure a back up of efs folder?
mjneil.81 said:
Thanks for the reply and advice Radicalisto.
I will check out CWM and how and what that backs up. If I take a guess now it will make an image of my current system that can be restored? If so does that ensure a back up of efs folder?
Click to expand...
Click to collapse
CWM offers an EFS backup yes, it has to be done seperate to the IMAGE back up though. Also note if you back up a 4.3 ROM on MJ7 firmware you cannot downgrade to a lower version ie: MJ1-2-3-4-5-6 etc - you can go to MK2 and back to MJ7 though.
Similar if you back up a 4.3 and upgrade to 4.4.2 then that backup becomes useless as it cannot be restored.
CWM - Install custom ROM, keep that script I posted close by, and you'll be 100% :good:
radicalisto said:
CWM offers an EFS backup yes, it has to be done seperate to the IMAGE back up though. Also note if you back up a 4.3 ROM on MJ7 firmware you cannot downgrade to a lower version ie: MJ1-2-3-4-5-6 etc - you can go to MK2 and back to MJ7 though.
Similar if you back up a 4.3 and upgrade to 4.4.2 then that backup becomes useless as it cannot be restored.
CWM - Install custom ROM, keep that script I posted close by, and you'll be 100% :good:
Click to expand...
Click to collapse
Thanks alot for your assistance im going to get the back up sorted and read up some more there is fair bit that i need to understand before flashing
Wise words my friend. Read up and understand are the two most important words of advice anyone can give and words that anyone should take heed of.
Good luck, if you run into problems, just holler :good:
radicalisto said:
Wise words my friend. Read up and understand are the two most important words of advice anyone can give and words that anyone should take heed of.
Good luck, if you run into problems, just holler :good:
Click to expand...
Click to collapse
so far the best thing I have come up with is to flash the latest 4.4.2 stock rom, I think this is the best option until some of the custom ROMs develop along a bit further.
but this leeds to a few more questions (I hope its not too much of a bother) Im going ( i think) to download the rom from Firmwares|SamMobile but it will be from another country(im in Australia) could this affect the perfomance of the phone in anyway or can I just flash other modems/radios in order to fix any problems that may occur?
mjneil.81 said:
so far the best thing I have come up with is to flash the latest 4.4.2 stock rom, I think this is the best option until some of the custom ROMs develop along a bit further.
but this leeds to a few more questions (I hope its not too much of a bother) Im going ( i think) to download the rom from Firmwares|SamMobile but it will be from another country(im in Australia) could this affect the perfomance of the phone in anyway or can I just flash other modems/radios in order to fix any problems that may occur?
Click to expand...
Click to collapse
So long as your note isn't a Hong Kong model you're alright, Here is a faster download link for XEO (Stock Polish ROM) - So long as it's an Intl N9005 (not HK) should be fine
all done upgraded to 4.4.2 no problems at all thanks radicalisto
mjneil.81 said:
all done upgraded to 4.4.2 no problems at all thanks radicalisto
Click to expand...
Click to collapse
:highfive:
ok now I have a problem I just tried to root the phone again with cf autoroot and its stuck in a boot loop. I cant get it back in download mode or recovery any suggestions
all good i got back into download mode hahaha *stops having a heart attack

NB4 Safestrap Restore and System Dump

NB4 Safestrap Restore: https://drive.google.com/file/d/0B2CETO5oJqxFVENCOGZqZWZPQjg/edit?usp=sharing
NB4 System Dump: https://drive.google.com/file/d/0B2CETO5oJqxFYThxc096ZG9BUVU/edit?usp=sharing
Similar to what megalomanic14 posted for MJ5, these are backup and restore files for stock NB4 with nothing removed. This is mainly for people who already updated to NB4 but altered their system, removed stuff, etc., and just want to get their system back to a basically stock setup. The Safestrap restore can be extracted and placed in the same folder where your other backups are stored(TWRP/BACKUPS/*device serial number*), and then restored in recovery. The system dump is for anyone who wants to poke thru the system without actually installing it, or for those who deleted stuff from their system but didn't back it up.
I was helping someone on NB4 who had messed up their system, so i figured I'd post this here for anyone else who might need it. Plus it can be handy to have.
Note: the backup contains root, which can of course be removed thru SuperSu. And i can't remember but the system dump might have xposed framework installed into as well lol. enjoy..
So with the stock_nb4_safestrap.zip, how would I go about recovering from these images? My phone is currently sitting at the boot screen, showing an unlock.
Thanks!
- derek
[derek] said:
So with the stock_nb4_safestrap.zip, how would I go about recovering from these images? My phone is currently sitting at the boot screen, showing an unlock.
Thanks!
- derek
Click to expand...
Click to collapse
if you have Safestrap recovery installed and can put the extraced folder into the TWRP backup directory on your storage, you can restore the system at least. unfortunately this isn't a full firmware restore for real emergencies or anything..
For anyone wondering if they can use this to do the upgrade if the OTA fails, the answer is "sort of". In my case at least the baseband and build numbers differ, not sure what else if any is/isn't updated
neoman4426 said:
For anyone wondering if they can use this to do the upgrade if the OTA fails, the answer is "sort of". In my case at least the baseband and build numbers differ, not sure what else if any is/isn't updated
Click to expand...
Click to collapse
Yeah this will only give you the system portion of the update.... Not the baseband, kernel, or anything else. It's mainly for anyone who already updated to NB4 who wants to restore a stock setup after they altered their system, removed stuff etc. Perhaps I'll mention that more clearly above. But I guess it is a way to update just the system
neoman4426 said:
For anyone wondering if they can use this to do the upgrade if the OTA fails, the answer is "sort of". In my case at least the baseband and build numbers differ, not sure what else if any is/isn't updated
Click to expand...
Click to collapse
have you tried this: http://forum.xda-developers.com/showthread.php?t=2559715, or this: http://forum.xda-developers.com/showthread.php?t=2619005 to get the update to work?
YrrchSebor said:
have you tried this: http://forum.xda-developers.com/showthread.php?t=2559715, or this: http://forum.xda-developers.com/showthread.php?t=2619005 to get the update to work?
Click to expand...
Click to collapse
Tried the SafeStrap restore, didn't help. haven't tried the full restore yet, requires Odin as far as I can tell and I haven't been assed to reboot into Windows to use it
neoman4426 said:
Tried the SafeStrap restore, didn't help. haven't tried the full restore yet, requires Odin as far as I can tell and I haven't been assed to reboot into Windows to use it
Click to expand...
Click to collapse
Just letting you know, someone I know was getting stuck at 25% when updating. They used the Odin/Heimdall MJ5 restore and then the update went thru fine
YrrchSebor said:
Just letting you know, someone I know was getting stuck at 25% when updating. They used the Odin/Heimdall MJ5 restore and then the update went thru fine
Click to expand...
Click to collapse
Finally got around to doing the full restore, it did indeed work for me as well. Figured it would, had all the files downloaded but didn't care enough to reboot into Windows until today

[Q] Rooting a Sprint S4 SPH-L720

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.

Root Asus Memo Pad 176 on lollipop .36 newest firmware plus Xposed

***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

Categories

Resources