Related
Hello,
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version, or should I downgrade. If I need to downgrade, can anyone tell me which software version I need to downgrade to in order to root, and a thread linking to a guide to downgrade?
forum.xda-developers.com/showthread.php?t=847993
this should do it
I think you can root this version, search around... if it possible you will find a post regarding it.
If you plan to downgrade, I would recommend .5 and then root using regaw's method - you should find all the details on the CDMA hero wiki page.
xlectik67 said:
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version [?]
Click to expand...
Click to collapse
HERE is the link to the post i wrote (in the thread which guided me) to get root in this stock-rom... so, yes, it can be done...
as far as dowgrading, im not sure i would recommend it - but as mentioned earlier, the wiki has a guide which i believe is based on a ...31...5 version you could use...
gl, h.
Root Sprint 2.32.651.2 OTA Permanently (in 10 steps)
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
ccrosno said:
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
Click to expand...
Click to collapse
Sorry I forgot to mention that there were a couple times that the phone locked up durring the reboot to recovery stage. I do not know why. I beleive that it was due to forgetting to install the recover before rebooting. If this happens, pull the battery, replace the battery and start over.
Thanks
tailsthecat3 said:
forum.xda-developers.com/showthread.php?t=847993
this should do it
Click to expand...
Click to collapse
my WiFi worked fine after rooting the ota update by following the linked method. ^
Go ahead and root using the method mentioned above, if anything goes wrong... you can always RUU and reroot.
BTW, I have downgraded using .5 RUU and rooted my phone, so based on my experience I can say, it works well. I had initially rooted my .7 and was running CM 6.0 stable, had some issues, got my recovery screwed up, so had to go all the way... ;-).
tailsthecat3 said:
my WiFi worked fine after rooting the ota update by following the linked method. ^
Click to expand...
Click to collapse
Ya I tried that one. Couldn't get it to take. Mine is sort of the non-syntax method.
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!
how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...
hitlab1 said:
how to fix at&t 4.4 update on my note 3....it makes it to 27% and stops...
Click to expand...
Click to collapse
I hate to say this since I'm not a moderator, questions need to go into the Question/Help thread.
Also, you need to read the post (located in this General thread) and do a little search and research to help you. I'm even nice enough to provide you a link (http://forum.xda-developers.com/showthread.php?t=2686652) which is the Official - the 4.4.2 update - discussion thread.
However,
To begin, you must be on NB4 (the small update that happened a few weeks ago. Also, if you have NOT installed the 4.4 leak, and didn't really do anything to your phone but only rooted.
or
You didn't even root your phone, just can't get passed the 27% of the OTA update, please follow these instructions:
USER BEWARE, THESE INSTRUCTIONS WILL ROOT YOUR PHONE. I'M NOT RESPONSIBLE FOR ANY DAMAGES YOU CAN CAUSE. THIS IS (please forgive me, my caps lock was on) to help you get the update.
1 ) On you Windows computer, go to http://www.kingoapp.com/
2) Download Kingo and install.
3 ) Make sure you have the required Samsung drivers installed also so your phone can communicate with your computer (use the USB 3.0 cable that came with you phone).
4 ) before you connect with the computer:
A ) go into setting (in your phone) and turn on USB debugging. If you don't know how to turn that on, there is instructions within the Kingo software itself.
B ) Set your screen timeout option for 10 minutes.
C ) Also remove your lock screen to none.
5 ) With your phone on, attach the USB cable. It should connect (you'll hear multiple sounds)
6 ) The Kingo software should recognize your phone and give you the option to Root. Please do so (this will not trip your KNOX flag).
7 ) Pay close attention to your phone's screen while going through the rooting process, popups will happen and you will be asked to click approve various functions that is required for root.
8 ) After root is successful, detach you phone. Go to the Google Play store and download Root Explorer. I have the premium version (it worth the few dollars, plus it helps out the programmers).
9 ) Open Root Explorer (or any file manager with root access) and go to /system/csc/
10 ) Look for feature.xml.bak. If this exists, delete feature.xml and rename feature.xml.bak to feature.xml
11 ) See if dexdump is in /system/xbin/ if not down Download dexdump from Jakman85 - http://forum.xda-developers.com/showpost.php?p=51440984&postcount=313
12 ) Copy dexdump to /system/xbin and set correct permissions. Root Explorer will request the directory to be made r/w temporarily while the file is inserted then put it back r/o, however you still need to set the correct permissions for that individual file. The best way is tap and hold another file already in that directory and select permissions and see how to properly set the dexdump permissions. Make sure the permissions match the other files.
13 ) Check for Update and let it do it's thing, or you can sideload the 2400258.zip file (you can download this from a link earlier in another thread) and install it from stock recovery from your sccard.
Note : on first startup after upgrade I did not have touch screen access but the S-PEN did work. However, you can simply restart the phone to get the screen working with touch.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Hello to all,
I just bought an Acer Iconia One 8 B1-810 and I have a few questions.
First of all, is there already a way to root this device, or else is the root under way?
Secondly, is there another way than rooting the tablet if I want to get rid of the bloatware? There are many pre-installed Google, Acer and Amazon apps I'd like to get rid of.
Now, am I right to assume that to get rid of the bloatware, I can simply stop and deactivate the apps I don't want, and then erase the corresponding .apk and .odes files in the appropriate folder? Or is there something else that I must do?
Thanks for helping; the Iconia One 8 B1-810 is a fine tab, but this bloatware is driving me insane!
Best Regards and a Happy New Year from the South of France.
Root acer ionica one 8
Credits @social-design-concepts for his great work and exploit for Intel Tab Devices and @Shreps for this detailed tutorial
Download
IntelAndroid-FBRL.7z available at http://click.xda-developers.com/api...t #2375 - XDA Forums&txt=IntelAndroid-FBRL.7z thx to @social-design-concepts
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip IntelAndroid-FBRL.7z
Plug your Tab with USB Cable and start launcher.bat
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
Type ACCEPT ont the cmd screen, press enter
On your deskop, the script should auto detect the Tab like this (device status online + color blue) :
Type "T3", press enter
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Dead link and a few questions
[email protected]Hi,
Thanks for your reply. I've got a few questions/comments:
- The first link doesn't work, unfortunately.
- Will this root work for all Intel-based Android tabs?
- I wen t to Acer's website. There are no USB drivers to download for the Iconia One 8 B-810. I already connected my tab to my laptop, though, and it was recognised by Windows 8.1. Does this mean that the USB drivers might already be installed by default on the laptop?
Thanks for helping,
Best Regards.
vbdx66 said:
[email protected]Hi,
Thanks for your reply. I've got a few questions/comments:
- The first link doesn't work, unfortunately.
- Will this root work for all Intel-based Android tabs?
- I wen t to Acer's website. There are no USB drivers to download for the Iconia One 8 B-810. I already connected my tab to my laptop, though, and it was recognised by Windows 8.1. Does this mean that the USB drivers might already be installed by default on the laptop?
Thanks for helping,
Best Regards.
Click to expand...
Click to collapse
The link is now fixed, sorry for that.
-it works on several acer/levorno models, inclusive Acer Ionica One 8 B1-810, I just rooted my yesterday.
-About the drivers no, you have to install ADB drivers, to do that download Cydia Impactor extract the downloaded files to your desktop run the app under USB chose Driver Scan and install the driver and you are ready to start .
Root
Hello,
Thank you for all this information. I will try to root my Iconian One 8 B1-810 over the weekend and tell you whether I succeeded or not.
Best Regards
Error Message!
Hi again,
I downloaded Cydia Impactor and tried to upload the drivers to my device as you said but it doesn't work. I connect the tablet to the computer with an USB cable, launch Cydia Impactor, choose USB then Driver Scan but all I get an error message stating No such device. Any idea about what I am doing wrong?
Since you have already rooted your tablet, could you possibly attach the drivers here or send them in a private message? This would really help me.
Best Regards.
vbdx66 said:
Hi again,
I downloaded Cydia Impactor and tried to upload the drivers to my device as you said but it doesn't work. I connect the tablet to the computer with an USB cable, launch Cydia Impactor, choose USB then Driver Scan but all I get an error message stating No such device. Any idea about what I am doing wrong?
Since you have already rooted your tablet, could you possibly attach the drivers here or send them in a private message? This would really help me.
Best Regards.
Click to expand...
Click to collapse
hi, in order to install the drivers, you have to activate the "USB debugging" option under the "developer options" on you device.
then run Impactor.
if that fails, tomorrow I will leave you a backup of my drivers on attch.
Did not work for me
Hi guys, thanks for the post but this does not work on my B1-810. When my tablet reboots it does not boot into CWM. Can anybody tell me what the message in the attached screenshot means?
These were the driver I used.
This video show you ,how i done it.
USB Debug enabled but unable to root
alexys77 said:
These were the driver I used.
This video show you ,how i done it.
Click to expand...
Click to collapse
Hello Alexys77
I have got the same problem as Slithertooth and i get exatly the same screenshots on my B1-810 when I start launcher.bat on the computer.
Many thanks for uploading your drivers here. I downloaded the .zip file on my computer but I don't know where to start.
Could you please tell us which files we need and how we must install them on the computer after dezipping?
Sorry if I ask silly questions, but this is the first time I am atempting to do this (I rooted a Galaxy Tab 2 7.0 a long time ago, but it was a one-click root-thing).
Thanks again for helping,
vbdx66.
hi slithertooth and vbdx66 thats easy to resolve .
This screenshots mean that the ADB drivers are not correctly installed.
To resolve this, with your tablet in Droidboot mode and connected, go to device management on your PC and find driver with a "yellow ?" click properties click on update navigate to unzipped drivers and click ok.
Then execute launcher.bat file again.
alexys77 said:
hi slithertooth and vbdx66 thats easy to resolve .
This screenshots mean that the ADB drivers are not correctly installed.
To resolve this, with your tablet in Droidboot mode and connected, go to device management on your PC and find driver with a "yellow ?" click properties click on update navigate to unzipped drivers and click ok.
Then execute launcher.bat file again.
Click to expand...
Click to collapse
Hello Alex:
About the MTP driver yellow mark
How to solve this ? Could you help to provide the MTP driver for me install?
Thanks
droidboot mode
Hello Alex,
I have a question, too. What do you mean by Droidboot Mode exactly?
Thanks.
Kelly5119 said:
Hello Alex:
About the MTP driver yellow mark
How to solve this ? Could you help to provide the MTP driver for me install?
Thanks
Click to expand...
Click to collapse
The MTP driver is inclued on the folder "Dispositivo USB MTP"
---------- Post added at 11:59 AM ---------- Previous post was at 11:44 AM ----------
vbdx66 said:
Hello Alex,
I have a question, too. What do you mean by Droidboot Mode exactly?
Thanks.
Click to expand...
Click to collapse
i mean Fastboot mode, Acer call it Droidboot.
-power off your tablet , then press V+ and Power, old it for a few seconds and release it when Acer logo pops up.
it worked!
I booted into "droidboot" and then connected to my laptop with usb debugging enabled. Then i downloaded Cydia impactor and using the USB drop down menu in this small program I was able to successfully instal the needed drivers. CWM then came up following the previous instructions.
Now can we flash ROMs on this tablet???
Success!
Well guys, I went through the whole process again, which was very tedious to say the least, and apparently it worked, SU is now flashed on my B1-810!
I now have Root Access in ES explorer, so this is simply brilliant. I can now access the external SD card or without restrictions again, which is just what I was looking for
Something strange, though: I installed Root Checker and it says me my tab is not rooted... Can it come from the B1-80 running an 'exotic' Intel Bay Trail processor?
I would be very interested to know what results you guys get from Root Checker after the whole rooting process is completed. Does Root Checker also tell you your B1-810 is not rooted even though it is? Is there another way to check that the tab is properly rooted, or can it be 'half-rooted' or something of the kind?
Best Regards to all and many thanks to Alex for the great job done
Update - Tablet Rooted
Hi again guys,
According to another root checking programming, my tab is properly root. Screen capture in attach. This time I used the Root Checker programming from Free Android Tools.
Update - I checked properly again, and now the other progrwm, Root Checker Basic developed by joeykrim, also tells me my tab has full root access. Cheers!
And Now That B1-810 is rooted, what?
My main concern to root this tab was to get full access to the external SD card again (done) and to definitely get rid of the bloatware, which comes unfortunately in quantities on the Acer B1-810. I already deactivated many apps I won't I use, like Email and Gmail (I use Aquamail) and Acer Docs, Acer Music, etc.
Now that the device is rooted, can someone who's already done this can tell we whether, under root, there is a safe and efficient way to completely uninstall these unwanted apps, like any 'normal' app downloaded from Google Play? Should I just suppress the relevant apk's with ES explorer or could this make the system unstable?
Furthermore, is there a way to control which apps the tab will start when booting?
And lastly, is there any way to tell the KitKat Camera app that it should store the pictures on the external SD card by default?
Any other things you guys are willing to do now that your tab is rooted? I am curious.
Best Regards.
vbdx66 said:
My main concern to root this tab was to get full access to the external SD card again (done) and to definitely get rid of the bloatware, which comes unfortunately in quantities on the Acer B1-810. I already deactivated many apps I won't I use, like Email and Gmail (I use Aquamail) and Acer Docs, Acer Music, etc.
Now that the device is rooted, can someone who's already done this can tell we whether, under root, there is a safe and efficient way to completely uninstall these unwanted apps, like any 'normal' app downloaded from Google Play? Should I just suppress the relevant apk's with ES explorer or could this make the system unstable?
Furthermore, is there a way to control which apps the tab will start when booting?
And lastly, is there any way to tell the KitKat Camera app that it should store the pictures on the external SD card by default?
Any other things you guys are willing to do now that your tab is rooted? I am curious.
Best Regards.
Click to expand...
Click to collapse
I deleted anything I didn't want using es file explorer. Navigate to the system app list from the dropdown menu and delete all the bloat you want. I deleted quite a bit and just disabled anything I was unsure of and I've run into no problems yet.
Which system apps to delete?
@slitertooth: Could you please be more specific? This is the first time I am doing this and I am afraid of damaging the device. If you don't mind, which apps did you deactivate and which did you completely uninstall?
Thanks.