Related
I did a PaSSIMG FRG33 version, but I can not root with universal androot also can not return to the version of PASSIMG FRF91, indicates that it is old version. Anyone know?
As it stands, if you want root you're back to having to unlock the bootloader.
You could try: http://forum.xda-developers.com/showthread.php?t=726258 and seeing if you can revert to FRF91 afterwards.
Try?
But someone made with good results?
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
kam187 said:
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
Click to expand...
Click to collapse
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Androith said:
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Click to expand...
Click to collapse
Android exclamation is STOCK recovery. Kam is saying "custom recovery" like Clockworks or RA.
Ok,
I got it, but unlocking fastboot to install the superboot. Now I have total control
Now we have to wait to close lock
Thanks!!
Which version of superboot should we be using to root this frg33?
The superboot FRF91
http://www.mediafire.com/?4nnez0uddqk519r
Thanks a lot. I opted not to wait for a new 1-click version. Unlocked the bootloader by cmd prompt. It was weird though. I thought when I was reading about superboot that all you had to do was dbl-click it from windows, but I ended up having to run it for cmd prompt, too. Either way, I'm rooted now. My only remaining question has to do with the custom recovery stuff. I flashed the "latest clockwork recovery" in ROM Manager. Then I flashed the modaco rooted/deodexed/busybox/etc. version of frg33. Is that all I need for my phone to be "safe" at this point? I guess ROM manager let's me flash just about any of the custom ROMS, but if one hangs on load, I just wanna make sure everything is restoreable.
BTW....Android clearly has the best and most helpful community of users that I have ever seen!!!
makelegs,
Glad you got it all worked out and are truely unlocked and rooted. As long as you nandroid, you are safe on what ever yoy wan to do. The dreaded, botched radio flash is probably the only way to get hurt. At least that is my understanding.
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
makelegs said:
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
Click to expand...
Click to collapse
Can't speak for Clockwork but on Anom the backup goes in /sdcard/nandroid/DEVICEID/dated-subdir
Each time you make a backup using nandroid, it's a new directory.
And you can NOT restore a nandroid made from a different recovery from what I've read. If you make it with Clockwork you gotta restore it with Clockwork.
makelegs,
It has become a general term with the advent of Rom Manager/ClockworkMod. If you look at the top of the Clockwork screen when in recovery, it say nandroid. The term generally means a full image backup of your phone as opposed to just backing up apps/data. In the nandroid the OS and all else is backed up. So, I wouldn't give it a second thought.
What khaytsus said is the only important thing. Restore thru whichever recovery you backed up with. Clockwork to Clockwork or Amon to Amon.
Amon is put into the nandroid file on your sd and Clockwork is put into Rom Manager under Backups. Although, you can get to them a couple different ways in Clockwork. Thru Install Rom From SD Card or Manage and Restore Backups. Also by booting into Clockwork Recovery. You probably already know that if you use Clockwork.
Ken
Is it actually probable that 1 click might be made to work for 33? It doesn't seem like there are many other users with stock/33 like myself. I feel like a horses ass for flashing it and screwing up my protected apps. All through the incremental updates that led us from 2.1 to froyo went thru easily with no paid apps issues so I didn't have my guard up for this one. (Unless they all had a modded fingerprint status which I starting to think I may remember them having, whatever, this is a bummer...)
Maybe it will be updated, but the folks on frg22 (i think) have been waiting even longer. I was just too busy and OCD to wait it out.
It was probably only ever a matter of time before I went the unlocked bootloader/root route. This was just the catalyst for me. I learned an awful lot in the process. Alas, my phone is back to "normal", but running modaco's rooted/deod/busy/frf91 finger/etc... version of FRG33. And I now realize that if I had just flashed the clockwork recovery to begin with, when I was 1-click rooted on frf91, then this whole thing would've been substantially less of a PITA for me.
Good luck!
FRG33
I got caught out i had 1 click root with cm6
But then installed FRG33 not realising i would lose root if i reverted to it after i had done a backup of cm6 .
I had a lot of things including adfree working on FRG33 prior to recovery .
I think the universal androot app uses the "exploid" method which indeed was patched in FRG versions. But I believe someone on the forum reported that FRG22 or FRG33 was still vulnerable to the "rageagainstthecage" root exploit.
Can someone here verify whether FRG83 is still rootable using "rageagainstthecage"?
You can try the instructions for rooting FRG33 in the Wiki on FRG83.
I am copying a reply I posted on another thad in hours that more people see anf it might help then.
Fyrmedic654 I'm gonna look for the page I got my 1 click method from, but it worked for me on the first time. I rooted immediately after flashing the odin file. Then I screwed something up before I pout clockwork on so I reflashed since I lost everything (not really, thanks to Titanium Backup). Then I immediately flashed the clockwork after and then the 1 click failed twice. Reflashed the official dl09 then 1 click and, boom, rooted on the first try. After doing a little searching, apparently the clockwork.tar flashes a DI01 kernal. So if people are flashing clockwork before rooting, this could be the culprit.
I use this method found here http://m.forum.androidcentral.com/sh...ad.php?t=33899 Hope this helps some people out.
Edit: Solution found look below!!!
As I posted in a different thread:
I managed to do it, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
EDIT: The kernel is stock for ACER_A500_1.016.05_COM_GEN1
Take a look at the thread linked below, get the 1.016.05_COM_GEN1 files (system, flexrom, and boot). If you are not offered an online update (System>About>Check for updates), you need the official update.zip from Acer. Extract the update.zip from the official Acer update THAT MATCHES YOUR FLEX VERSION using the XOR 12 method (see here - http://forum.xda-developers.com/showthread.php?t=1065360&page=20 - note in that post the link is for 03_COM_GEN1, NOT 05_COM_GEN1. For 04_COM_GEN1 and 05_COM_GEN1 see here - http://forum.xda-developers.com/showpost.php?p=14052165&postcount=184. For 03 and 04 you will need to find system.img, flexrom.img and boot.img, for 05 they are linked in the thread below).
EDIT: The thread with the images for ACER_A500_1.016.05_COM_GEN1 is here:
http://forum.xda-developers.com/showthread.php?t=1086785
EDIT: You might pull this off for other flex versions as well, but you would need all the files (system.img, flexrom.img, boot.img AND update.zip) from those versions.
PLEASE NOTE THAT THIS ONLY WORKS IF YOU HAVE THE OFFICIAL UPDATE.ZIP FOR YOUR SPECIFIC FLEX VERSION
Wow, I was about to try that!!!
I'll do that now and see how it goes.
Thanks mate!
EDIT: Worked!
I would expect that the reason an update fails on the Chinese one is that it tries to patch the kernel (which is different from the one expected). The update is a bunch of diffs and patches, and almost no full files, so it cannot be applied over anything but the right files.
Yes that is true. The old kermel checksum check was failing.
huxflux2003 said:
EDIT: Worked!
Click to expand...
Click to collapse
Glad to hear it Take that, you sneaky Acer bastards!
adancau said:
As I posted in a different thread:
I managed to do it though, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
Take a look at the thread, get the 1.016 files, system, flexrom, and boot, and try it.
Click to expand...
Click to collapse
Ahhhh a true milestone, well done.........
Nice work! Two questions:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Thx
gingerbreak works
_motley said:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Click to expand...
Click to collapse
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
adancau said:
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Click to expand...
Click to collapse
Thanks guys, I did restore using the Chinese update.zip last week and I am currently sitting at kernel 2.6.36.3 with flashed system img=Acer_A500_1.104.05_COM_GEN1, but with recovered Chinese kernel modules for wifi etc. I also flashed a flexrom.img from this build as well. I didn't flash the boot.img from this build, but was thinking about it until huxflux2003 reported the check-sum failure.
So, I am trying to decide what I am going to do. It sounds easy enough to get back to stock now, but I may wait for the official update next month that has 3.1. At this point, I suppose we are assuming that it will be a full update.zip that will work on any tablet (god I hope so). It's about time they gave us a full recovery image...I will be beyond disappointed if they don't. Let's also just hope we can still gain root easily after this.
One more question, if I use all the images from ACER_A500_1.016.05_COM_GEN1 that were posted, does this have to match what I had originally had in any shape or form? It sounds like since all the pieces are from the same build, everything will be fine regardless of what you had to begin with. Is this right?
Thx
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
heyoh said:
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
Click to expand...
Click to collapse
To get back to stock you need the three images for your build - system, flexrom, and boot. If there is no online update available, you also need the update.zip for that build (extracted from an official acer update using the XOR 12 method - do a search).
Alternatively, I suppose you could switch to a new build for which you could find all the necessary files (but it hasn't been tried).
Flash system.img using dd. You might need to re-root. Reboot, flash flexrom.img. Reboot once more. Make sure your wifi works (you might need different kernel modules).
Look to see if there is an online update (Settings > About > Check for updates). If there is, cancel it. Flash boot.img on mmcblk0p2. DO NOT REBOOT.
If there was an online update available, now it's the time to perform it. After it's done you will get you back to stock 1.139.05.
If there isn't any update, make sure you have the update.zip on the root of your microSD. Turn off the tablet, then turn it back on holding the volume key closest to the power button. Do not let go of that button until you see some text in the corner. At that moment the update would begin. Once rebooted you will be back to stock.
Hope I've explained it better this time, and it works ok for you. If not, you need to go through the chinese update again. Good luck.
adancau said:
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
Click to expand...
Click to collapse
It worked for me too! Thanks again for the tip. I am now at the latest build and ahead of the US update schedule from what I can gather
It asked me to update after I flashed the ACER_A500_1.016.05_COM_GEN1 build system.img and flexrom.img. Even from the US it prompted just fine since I was on ACER_A500_1.016.05_COM_GEN1 build and not ACER_A500_1.104.05_COM_GEN1 as the former is what the differential patch targets.
I cancelled the update once I saw it presented and then blew on the boot.img from the ACER_A500_1.016.05_COM_GEN1 build. Then, without rebooting, I downloaded and applied the update (but with a little hiccup, see below). Now I am at Acer_A500_1.139.05_COM_GEN1 and didn't lose any user apps or settings etc.
Had a scary point though that I will share as it may help others. The first time I tried, the zip wouldn't downloadload and I was getting an HTTP 403 error. I cleared the systemupdater app and FWUpdateService data. I also killed the services and then I was stuck. Instead of conceding to reflashing the Chinese update.zip and starting over, I unzipped the Chinese update.zip and grabbed the boot.img from it. I then dd'ed that image back to the boot partition and rebooted again. It came back up and I this time I was able to do the system update successfully. Whew!
Followed instructions by OP and it worked perfectly! Back to stock and updated.
I think I'll be keeping these system images for next time I brick and have to flash the Chinese update.
Any chance of someone uploading the extracted update.zip for the new Acer_A500_1.139.05_COM_GEN1 so I can update manually using this method.
Thanks in advance
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
tianqi said:
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
Click to expand...
Click to collapse
If you directly flashed a 1.139.04 image your kernel has not been updated. You had to flash a 1.016.04 image, flexrom and boot, and then run the update.
You MIGHT have some luck regardless by running the update.zip now (I used it on mine one time when I updated like you did, and it seemed to work, but I have not noticed the kernel number). Be prepared to have to reflash if something goes wrong though.
I did reflash system, flexrom, and boot from 1.016.04...
Second time is still the same...
Kernel is still 2.6.36.3-00001-gf991e5d...
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Borman18 said:
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full nandroid backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
Are you using Iconia Root to root and unroot? Let's start there?
Off to bed, I'm sure one of the other "late nighters" will be able to help you.
My only question is that you stated you installed CWM, if so, why didn't you create a full backup with it instead of nandroid?
Yes, I used Iconia Root to do the deed, which has worked since I got the unit a week ago until today.
And thats what I mean in terms of backing up, my apologies (im just use to calling it Nandroid for whatever reason).
I have no idea how the recovery got wiped though.
Borman18 said:
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
I STRONGLY recommend you read the following thread.
http://forum.xda-developers.com/showthread.php?t=1129873
Looks like you flashed something and didn't run "itsmagic".
Ive tried that, and no go. As far as I can remember, I havent flashed anything in days, since updating to the latest update a few days ago. And its been fine since then, until today. I started downloading google music stuff, went to the bathroom, came back and my tablet was off. I can give it another go though.
If it wasn't clear, I can definitely boot, its just with all those errors
But you get a checksum error, right? Have you gone through the steps in that thread that detail how to fix the checksum error?
If so, I suggest you contact sc2k.
Correct, if I hold the volume - and power, it gives that error. Just ran through the steps for the "<CASE 1> SOS checksum error" again to be safe, and its the same. I PM'ed him earlier (maybe twice..), but I can only assume he's sleeping, so I was just trying to see if anyone has any ideas.
Edit: from my ADB Shell session, just to show that it seems to want to work anyway? But of course, the same old..
# /data/local/itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
# exit
Your best option is to wait until sc2k gets back to you, then. Don't worry. He's a fairly nice guy and has helped plenty of folks sort out similar issues on their tabs. Just remember to beer him afterwards!
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Borman18 said:
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Click to expand...
Click to collapse
AH, y'see, now you know what caused it in the first place! You tempted the fates! Never tempt the fates, for they are mean and sadistic beings that just LOVE to screw with folks right before they go camping.
I hope sc2k is able to help you out.
***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