Related
Hello I am new to the u8650. Some information on how to put in root mode u8650? is the same way in other models Huawei?
thanks
Same question here.
Tried all the inger tools (Gingerbreak, Superoneclick etc...) but nothing happened :-(
Hey! I want to know it too! listening to the Masters...
Z4root should work. It used to be on the market but it's not there any more. It's just an app that you click one button and it roots your phone.
You can download from another site
EDIT: you might be able to download from these forums
Correct me if I'm wrong, but I think the z4root not work for the android version 2.3.3 GINGERBREAD
I am trying even with GingerBreak... and it is not working... (
same here, zRoot doen't works
Let me say the the stockromitself is GREAT, but I need root for Titanium -backupnadmaybe a bootroom for a nandroid backup
isn't there any news? ı have to root it.
It is my first Android Terminal... and everything it is so hard dificult! jajaja I am jsut want isntall App2sd+... please!!!
Becasue I am reading... and still dont understand if i can put any new room or not...
best regards!
sylord said:
Hello I am new to the u8650. Some information on how to put in root mode u8650? is the same way in other models Huawei?
thanks
Click to expand...
Click to collapse
Yes my dude, I have same problem. Is anybody help us?
naghtan said:
I am jsut want isntall App2sd+...
Click to expand...
Click to collapse
Actually you don't need to, since 2.3.3 let you move almost all NON-SERVICE apps to SD.Just be sure to choose "SD card" as primary instalation storage in menu and application settings.If you already installed some apps just go to the app manager and move them to SD.Remember that Apps on SD won't show their widget (as Facebook and so...)
Anyhow: U8650 is sold in Spain from Yoigo ONLY, and I heard it's sold in Tuskey maybe, that means no root or custom rom until someone from spain or turkey will work on it.
As far as I know nobody from turkey or spain use to works on android reverse-engeneering :-(((
Diomorgan said:
Actually you don't need to, since 2.3.3 let you move almost all NON-SERVICE apps to SD.Just be sure to choose "SD card" as primary instalation storage in menu and application settings.If you already installed some apps just go to the app manager and move them to SD.Remember that Apps on SD won't show their widget (as Facebook and so...)
Anyhow: U8650 is sold in Spain from Yoigo ONLY, and I heard it's sold in Tuskey maybe, that means no root or custom rom until someone from spain or turkey will work on it.
As far as I know nobody from turkey or spain use to works on android reverse-engeneering :-(((
Click to expand...
Click to collapse
Yes I know it... but I want to move the cache there... and extend the nand memory to i can use wigdet too... I am waiting a memory card class 10 of 16 gb... jejeje...
We will wait a new version of Gingerbreak could make open these pandora box...
thanks so much...
Hi.
I have a u8650 too. I hope someone get root this phone.
Thanks.
Bye.
naghtan said:
I am waiting a memory card class 10 of 16 gb... jejeje...
Click to expand...
Click to collapse
Wow, how much is it?
I'm looking for them, but it looks like they doesn't exist or have crazy prices!
Diomorgan said:
Wow, how much is it?
I'm looking for them, but it looks like they doesn't exist or have crazy prices!
Click to expand...
Click to collapse
It just arrive these morning... In a very famouse "Componentes" shop from Spain... Transcend MicroSDHC 16GB Class 10 Ultimate Tarjeta MicroSD for 32.95 €...
And the phone recognize it without any problem...
naghtan can you PM with the link to the shop?
I tried using GingerBreak by adb, but ends up giving me error.
Any ideas?
Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17ffd strcmp: 0xafd37455
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00016360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0084 GOT start: 0x00016360 GOT end: 0x000163a0
Unable to open log device '/dev/log/main': No such file or directory
Unable to open log device '/dev/log/main': No such file or directory
I try Gingerbreak 1.2 and Superoneclick 2.0beta and same...
The problem it is he not let me mount the folder. I supposed, perhaps, you need root power? If My phone it is not yet rooted!!! jajaja I dont know...
I am even try to make it under recovery mode... but it is the same...
" Remounting /system with read-write access…
mount: Operation not permitted
FAILED
"
How I get power to mount and unmount if my phone it is not yet rooted?
How I can make it under REcovery Mode? One time I am in recovery mode Superoneclick not detect the phone...
I try also Superoot... and nothing... I will try z4root but i think it is very old..
My log...
SuperOneClick v2.0.0.0
Checking drivers...
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
2.3.3
Getting manufacturer...
HUAWEI
OK
Getting model...
U8650
OK
Getting version...
C86B823SP05
OK
Checking if rooted...
False
OK
Rooting device... - Step #1
OK
Rooting device... - Step #2
OK
Rooting device... - Step #3
1051 KB/s (16830 bytes in 0.015s)
OK
Rooting device... - Step #4
OK
Rooting device... - Step #5
$ cd /data/local/tmp/
$ ./gingerbreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00016360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00016360 GOT end: 0x000163a0
Unable to open log device '/dev/log/main': No such file or directory
Unable to open log device '/dev/log/main': No such file or directory
OK
Rooting device... - Step #6
OK
Rooting device... - Step #7
OK
Installing BusyBox (temporary)... - Step #1
1703 KB/s (1062992 bytes in 0.609s)
OK
Installing BusyBox (temporary)... - Step #2
OK
Getting mount path...
/dev/block/mtdblock4
OK
Remounting /system with read-write access...
mount: Operation not permitted
FAILED
Click to expand...
Click to collapse
maybe the stock rom (not the yoigo one) can be rooted?
I can find in the forum a stock rom, but I wouldnt like to try till I got the yoigo rom too to recover the phone if the other room is bad :-(
Diomorgan said:
maybe the stock rom (not the yoigo one) can be rooted?
I can find in the forum a stock rom, but I wouldnt like to try till I got the yoigo rom too to recover the phone if the other room is bad :-(
Click to expand...
Click to collapse
here you can find another rom not belong to Yoigo... but it is fomr Australia Operator...
http://forum.xda-developers.com/showthread.php?t=1142381&highlight=Huawei
Important Update on Dec 2, 2011: Please do not update to Vizio Update 1.5. This will remove the root as well as disable this hack. According to user felixand in this Post.
I decided to start a new thread.
For those who would like to root, please see the instructions in the first post of this thread. This works for me.
http://forum.xda-developers.com/showthread.php?p=18805532
### Please use V3 version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip ###
Edited to add: If the above DooMLoRD method does not work you can use SuperOneClick. SuperOneClick can be found here: SuperOneClick. Download it and expand it. You will also need to download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip. Expand it as well. Copy the new zergRush binary from the files directory of DooMLord into the exploits directory of the SuperOneClick folder. Then run SuperOneClick to root. Thanks to those who tried this method. See post by marvin02 below.
ACKNOWLEDGEMENTS:
I am not the original developer. I just helped test it. Please thank the developer of zergRush who fixed this code on the Vizio. Post by Ch4lky here.
http://forum.xda-developers.com/showthread.php?p=19396835
For those interested in the original source code of this exploit it is here.
Source code: https://github.com/revolutionary/zergRush
Binary: https://github.com/revolutionary/zergRush/downloads
Edited: Info about Vizio update 1.5 on Dec 2, 2011.
so to read into what you are posting - we need to follow directions and use the http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
which is "DooMLoRD_v3_ROOT-zergRush-busybox-su.zip"
again, I am at work and can't download, but does above file contain the additional files called out in the script - namely busybox, su, and superuser.apk - if I were to guess from the filename, I would say yes...
to sum up:
place the 4 fileset(s) into a common directory under your adb setup - for consistency - we'll call this "files"
so we end up with
./files/zergRush
./files/busybox
./files/su
./files/Superuser.apk
is this about right?
Rich
Yes, that is correct.
okay - so the next step is the rewriting of the vold.fstab file to properly map the internal mount point and the external microSDHD card.
I remember seeing something on the Pandigital Novel forums that had suggestions on this topic...
Any ideas as to what the Vizio needs?
1) first so as not to break the current OS settings
2) then, to remap the mount point as needed so that software like APP2SD will behave correctly.
(looking forward to getting home tonight)
Rich
Wow, I was about ready to get rid of this thing. Will be giving this a go today and seeing about some dev support for roms and what not.
Kudos!
For me the doomlord script stuck waiting for the device.
I put the zergrush exploit into the exploits folder of SOC 2.2 (replace the one that is there) and it worked liked a charm.
Edit: SD Card mount point mod
If you are having issues rooting here is some troubleshooting:
To test your connection with adb:
After installing the drivers open a command prompt in the folder where the adb.exe is located at, make sure USB debugging is on and connect your VTAB to your computer.
Now type "adb devices" without the quotes and you should see:
D:\Android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your serial number here device
If this does not work then adb is not connecting to your VTAB.
For me the version of adb that is packaged with the doom script does not connect, but the version packaged with SOC 2.2 does. I copied the zergRush exploit from doom's script to the exploit folder on SOC 2.2 and used SOC. I am on WinXP Pro.
If you are using 64 bit windows make sure you install the drivers as an admin and run the doom script or SOC 2.2 as an admin.
Now...
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Maybe now that it has root, XDA should create a subforum for it?
blackcog said:
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Click to expand...
Click to collapse
This is great. Please post your progress. That will be very helpful.
majorpay said:
Maybe now that it has root, XDA should create a subforum for it?
Click to expand...
Click to collapse
We have to request it here.
http://forum.xda-developers.com/showthread.php?t=1301121
rprr said:
This is great. Please post your progress. That will be very helpful.
Click to expand...
Click to collapse
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
May I ask how you are trying to dump the boot img?
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
sigeltek said:
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
Click to expand...
Click to collapse
Thanks, I showed that to my DW and she burst out laughing But, the real credit should go to the devs of zergRush and Ch4lky in particular. Please see my OP for the link to Ch4lky's post if you wish to "Thank" his post.
Same problem here.
The doomlord rooting kit did not work for me either. However, the superoneclick 2.2 with zergrush exploit copied into the exploit folder did work.
---------- Post added at 09:13 PM ---------- Previous post was at 08:52 PM ----------
Do get my device rooted runnning ADB under Vista (32-bit) I did the following:
1) First the Vizio provided ADB driver would not install. I instead did the following.
2) After making sure that any previous drivers were uninstalled from Device Manager including the Android Composite ADB driver. This driver would install for my VTAB successully but I was unable to communicate to the tablet using ADB. I deleted this driver and clicked on "delete the driver software". I also deleted the USB mass storage device and USB composit device.
3) I did a clean boot of the VTAB and then enabled the USB debugging.
4) I connected the VTAB to the USB port and this enabled "installing new hardware"
5) On my machine, I allowed it to search for the device driver and the key was to ensure that it would fail and close.
6) Go into control panel, device manager and you should now have other device named VTAB1008 with yellow highlight.
7) Right mouse click and select "update driver software"
8) then select "browse my computer for driver software"
9) then select "let me pick from a list of device drivers"
10) Select "ADB interface" and then select "Android Sooner ADB testing interface".
11) Once this driver was installed, I was successful in seeing the VTAB through ADB.
12) Install SuperOneClick version 2.2
13) Download the doomlord V3 toolkit and copy the zergrush file under the /files directory to the exploit directory under SuperOneClick (replacing the existing zergrush file)
14) Once this was done, SuperOneClick was successful
rprr said:
May I ask how you are trying to dump the boot img?
Click to expand...
Click to collapse
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
blackcog said:
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
Click to expand...
Click to collapse
Sorry about your VTAB. May I ask again how you were trying to extract the boot.img?
marvin02 said:
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
Click to expand...
Click to collapse
Thanks. I did try that but still cannot get to the boot.img.
I've been spending a long 3~4 days working on an install process to make applying /system changes quick, easy, painless, and automated. It then occurred to me that I could wrap it into a rooting process, and automate nearly the whole thing, to ensure that people don't accidentally trip up somewhere, and send their Nook Tablet into a bootloop, or lockup, or something like that.
The process was because a number of binaries that are typically standard with CM7 are not included in any of the roots so far. Having them around helps out a lot during development. (Like parted, vim, bash, sqlite3.)
So, I present to you the culmination of my work so far: Snowball-mod (thanks to dj_segfault on IRC for coming up with the name)
This borrows heavily from Indirect's Nook&Zergy root process. He deserves a ton of thanks for setting it all up, and bringing things together, and figuring stuff out. 100 internets to Indirect. (Don't kill me for stealing so much of your process, and .BAT coding wizardry. ... I stand upon the shoulders of giants.)
BIG WARNING:
THIS IS A FULL MOD, IT WILL REMOVE ALL BARNES & NOBLE CONTENT, DO NOT APPLY IT TO SOMEONE ELSE'S NOOK, OR A SHARED NOOK WITHOUT PERMISSION!
They really probably will freak out that their Nook Tablet looks far more like a CyanogenMod7 tablet than a Nook Tablet anymore. Especially, when they can't access their B&N content anymore. Don't say I didn't warn you, the process even warns you itself!
First, install the ADB drivers on your machine as has been explained in various other posts. Snowball-mod will work with Windows, Linux, or Mac. (I have not tried the later two, but if NARS works for you, then Snowball-mod should as well.)
Features:
* Installs extra packages from CM7
* Installs extra commands from CM7
* Installs busybox, with links. (BusyBoxInstaller.apk is also installed so you can update the binaries later, it can also be uninstalled.)
* Installs revcompgeek's hack that makes the soft buttons to always stay on, and the n button works as home, without homecatcher, and without bringing up the bar.
* Uses kenblat's hack to mount into the 12GB data area so you can recover some of that space for your own use. (/data/usrdata hack) It shows up at /mnt/internal (NOTE! Most apps still don't recognize this mount's existence.)
* Optionally, using my own hack, the command "setup-sd-ext" will let you setup a card image that is FAT32 formated, and appears at /mnt/sd-ext, similar to a secondary SD Card. (NOTE! Most apps still don't recognize this mount's existence.)
* Fixes the invisible submenus with white text on a while background
* Automatically applies OTA blocking to change your Version to report as 9.9.9 No further action required on your part to apply this.
* Supports both Windows, Linux and Mac with nearly the same process.
* Sets your browser homepage to "about:blank", and deselects "Remember form data" and "Remember passwords". (I think these are way more sane values.)
Includes:
* ADWLauncher (You can replace it the same as any CM7 install.)
* Android Terminal Emulator
* Button Savior
Needed files for root:
You need drivers first:
http://dl.dropbox.com/u/15069134/usbdrivers.zip
Here is an app to pull up usb debugging menu
http://li362-167.members.linode.com/gapps/non_google/tgps_launcher.apk
Code:
<robertely> Also note, that while that box will remain checked, the setting is not persistant.
<robertely> So you have to flick the top 'Usb Development' box twice to get it working.
Download Link for rooting script:
http://dl.dropbox.com/u/54958574/snowball-mod.zip
Code:
MD5SUM: 7f0090051e6141d6bfeb280355a04b18 *snowball-mod.zip
Instructions to root:
0. Make sure that you have a 1.4.0 Nook Tablet. If you don't, then find one of the posts to recover to 1.4.0, and start from there. The less interference from Barnes & Noble involved the better... they've already done plenty enough.
1. Download the "usbdrivers" zip
2. Download the "snowball-mod.zip"
3. Extract both to a folder C:\ntroot\
4. Now you should see the following files and folders inside c:\ntroot:
5. Run "runmefirst.bat" and follow the instructions.
6a. When the batch file opens the device manager, If you don't see a broken device icon next to "NOOK Tablet" then you may have some other generic drivers taking over. Not sure how to remove them so you will have to move to another PC that has never had a tablet hooked up and start over.
6b. If you do see NOOK Tablet with a broken device icon.. then right click and choose "update driver". Choose "Let me specify where the driver is" and browse to the c:\ntroot\usbdriver folder and hit ok. It should install and you can click "OK" to the warning about unsigned drivers.
7. Run "snowball.bat" and follow the instructions
7a. If you see a long string of numbers/letters it's your device
8. After the rooting process is complete, your nook tablet will reboot, and should start up straight into ADW Launcher.
Want to install your own apps, too?
The rooting scripts will take care of all that needs to be done if you just put your .apk files into the "apks/" directory of the snowball-mod directory. They will be installed automatically at the end of the rooting process.
Should I install this?
I really wouldn't recommend this rooting process for anyone who wants to keep any Barnes and Noble apps on their Nook Tablet. Also, if you've been using your tablet for awhile already, then it might not be a good idea to install this root process as well. It is intended for a clean and fresh Nook Tablet, and I cannot take responsibility for it wiping out something important. You have been warned that this is a drastic full modification.
Instructions to update:
1. Download snowball-update.zip from http://dl.dropbox.com/u/54958574/snowball-update.zip
Code:
MD5SUM 572793e71a0715185e03de4248c09aa2 *snowball-update.zip
2. Extract onto your computer.
3. Plugin your Nook Tablet with USB debugging mode activated
4a. On Windows double click "update.bat"
4b. On Linux/Mac/Cygwin open up a Terminal, cd to the directory, and enter "sh ./update.sh"
5. If you see "INSTALLATION SUCCESSFUL", then it's all done, and updated.
Screenshot
Someone wanted to see a screenshot. Rather than reroot just to get it a silly picture of an empty stock ADW launcher, I just recreated the screen to the best of my ability. The background is weird, I don't think it's scaled right, and for some reason, it's showing up as purple here. But it's just the same blue background as your nook had at the first install.
INB4, this steals a lot from Indirect. I know this. You don't have to say it. His root is way better for a minimal rooting experience and keeping the B&N Nook Tablet much the way it is stock, for people who just want to protect sideloading, etc.
This is for people who would rather install a custom ROM. Until then, this is about as close as you will get.
BUGS:
* There seems to be a bug in setup-sd-ext right now. It is not taking into account the "M" in the count. This could be a problem of running the wrong dd. I'm investigating it now. *** RESOLVED WITH v2.0.2 ***
* Nook for Android app won't startup up, not even FCs, it just doesn't start up. This is possibly something to do with the B&N code preventing it from starting up. (internal app name: bn.ereader-1.apk)
* Get rid of the "book" button at the bottom in the status bar: Easy enough, just replace the graphics to get rid of it.
* Move the "adb push ___.zip" to move to /data/local/tmp rather than /mnt/media ... it seems some people are confused, and accidentally leave their device automounted while attempting to install. Moving the push to /data/local/tmp will allow itself to install even when this is done. *** RESOLVED WITH UPDATE TO INSTALL SCRIPTS ***
* adb shell "snowball-ver" seems to be reporting in DOS file format even on linux, which causes a spurious "\r" to end up in the file name. *** RESOLVED WITH UPDATE TO INSTALL SCRIPTS ***
* check to see if the user is already up-to-date, if they are, then report so, and exit out. *** RESOLVED WITH UPDATE TO INSTALL SCRIPTS ***
* detect if something went wrong with installation, and don't report "success" unless it actually did succeed! *** RESOLVED WITH UPDATE TO INSTALL SCRIPTS ***
* ensure that any local $adb in snowball scripts are a+x prior to using them.
* some /bin/sh implementations do not support $OSTYPE. Consider switching to the NARS script version of using "uname -o", as this will likely end up being more universally supported. (Rather than assuming everyone's /bin/sh is bash.)
CHANGELIST
2012-06-01: v2.1.1
* Install script updates to better detect the adb binary, and ensure that it is executable.
* ipctool and viewmem included from the "Basic Hacking Tools" thread
* Reduced snowball-mod size due to removing text-to-speech, wallpapers, and other spurious content. The update process will not remove these, but future versions will continue to not carry these files. This is intended to reduce the size of the binary to decrease the odds of another dropbox shut down for excessive traffic.
* This update is a trivial update and is predominantly only changes to the installer, and a reduction in package size. You do not have to apply this update for any real reason at all, which is good, because it won't be up for a couple days.
Very nice, what is the risk of using this on a already rooted and ota blocked tablet, would going back to stock be the best bet? It rooted using the zergy method as well. The instrucstions seem simialar up until running snowball.bat could I just pick it up from there?
Sent from my BNTV250 using xda premium
The risks are fairly minimal, but still kind of there. About the biggest one would be clobbering your Browser.apk preferences.
Plus, just like the Nook&Zergy root, you can't run it on a system that is already rooted.
The nook-update-package.zip however in the snowball-mod pack can be extracted, copied to your Nook and executed by hand with a simple "sh install", which will do all the heavy lifting of the process. If you don't want it to wipe your browser preferences then you could delete the "data/data/com.android.browser" directory as well.
It's really barebones, and relies upon the filesystem structure to take care of just about everything.
And the sh install is a terminal command correct? I've used Ubuntu so im somewhat familiar with doing things by hand lol
Sent from my BNTV250 using xda premium
Yes, indeed the "sh install" is a Terminal command. In fact, I suppose if I say "sh ./install" then it will make sure it only works in the proper directory as well, lol.
Actually, I had been using this method for the process up until yesterday, when I started working the rooting process around it.
Nice! What version does this work on?
Do you have any screen shots of this or even a video of how it looks after doing this? Also, just an assumption that the normal 1.4.0 file would take us completely back to stock if we so desired?
This only works on 1.4.0
The screen shot is basically just an empty ADW Launcher as if it were just a stock installed CM7, but with the nook status bar.
cfoesch said:
This only works on 1.4.0
Click to expand...
Click to collapse
May I suggest adding that somewhere in the first post?
Thanks for your work. I tried 3 times and every one looks the same:
Your device is a Nook Tablet meaning we can continue!
Now, just making sure you WANT to root it!
__THIS_WILL_WIPE_ALL_OF_BARNES_AND_NOBLES_STUFF_FROM_YOUR_NOOK_TABLET__
__DO_NOT_INSTALL_THIS_ON_SOMEONE_ELSES_NOOK_TABLET__
(Y/N)? Y
1441 KB/s (0 bytes in 23056.000s)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40119cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd193a3 0xafd3908f
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
Installing superuser and su...
1817 KB/s (0 bytes in 843503.000s)
1397 KB/s (0 bytes in 22364.000s)
1397 KB/s (0 bytes in 22364.000s)
Installing and setting up busybox...
1780 KB/s (0 bytes in 1994516.001s)
754 KB/s (0 bytes in 12066.000s)
Uploading nook-update-package...
2518 KB/s (0 bytes in 43198793.016s)
Extracting nook-update-package...
Installing nook-update-package...
Installing extra apps...
2868 KB/s (0 bytes in 413129.000s)
2772 KB/s (0 bytes in 1241892.000s)
2031 KB/s (0 bytes in 195032.000s)
Blocking OTAs...
1 KB/s (0 bytes in 1153.001s)
Setting up /data/usrdata...
Rebooting Nook Tablet...
Nothing happens / no reboot. After a manual reset nook stuck on boot.
Any idea?
Can you open up the log.txt and copy it to a pastebin? The log.txt has _WAY_ more information in it. (But it's a bit long to post here in the forums.) Alternatively, you could just upload the log.txt file somewhere, and give a link.
Hmmmm this is looking like a ten failed boots kind of day...
Nice work man. I thought I was going to be OK with home catcher and pretending the BN stuff wasn't there... this is going to make that cognitive dissonance a no-go.
Sent from my MB860 using xda premium
beatphreek said:
Hmmmm this is looking like a ten failed boots kind of day...
Click to expand...
Click to collapse
Is that a good thing or a bad thing?
Nice work man. I thought I was going to be OK with home catcher and pretending the BN stuff wasn't there... this is going to make that cognitive dissonance a no-go.
Click to expand...
Click to collapse
Yeah, I'm a perfectionist... I don't seem to do well with "good enough"... me and him don't get along...
* Fixes the invisible submenus with white text on a while background
Click to expand...
Click to collapse
What did you do to fix this? Did you modify framework images?
xdahgary said:
What did you do to fix this? Did you modify framework images?
Click to expand...
Click to collapse
Indeed. Also, this means hacking the bootanimation was trivial as well, so I included a custom bootanimation as well.
Works now. I got only the Google-Services-Framework FC
Yeah... who knows what is causing the Google Framework Services FC... I think it is in part related to the Android Market keeping track of what you have installed, and not. It seems like every time I install a new app though, it FCs.
I've been thinking about re-rooting my Nook.
Does the script install GAPPS, or does it give you the option to install? Do contacts work?
cfoesch said:
Yeah... who knows what is causing the Google Framework Services FC... I think it is in part related to the Android Market keeping track of what you have installed, and not. It seems like every time I install a new app though, it FCs.
Click to expand...
Click to collapse
You are correct. It doesn't FC if you don't log in to market.
So, I finally received my Samsung Galaxy Player 4.2 in the mail. I live in Canada so I had it shipped.
DEVICE DETAILS:
MODEL: YP-GI1
ANDROID: 2.3.6
KERNEL: 2.35.7-CL1076053 [email protected] #1
BUILD: GINGERBREAD.XXXX3
Now, it was only after I did some googling that I figured out that it's very hard to root 2.3.6, which is what is running on my device, the GINGERBREAD release.
I have already tried the DooMLoRD_v4_ROOT-zergRush-busybox-su release to try to ZergRush the device, but with no luck, following results:
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
608 KB/s (23060 bytes in 0.037s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2173 KB/s (1075144 bytes in 0.483s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
214 KB/s (439 bytes in 0.002s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 20844 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Of course, I did read a thread somewhere that it is hard to root 2.3.6.
Now a few questions,
1. Is it safe/Possible to downgrade to 2.3.5 or something lower that I could use to then root the device?
1a. If this is possible, then can I upgrade to a new ICS rom or 2.3.6 ROM, like a custom ROM; if so which would be the best for customizing, compatibility and overall goodness?
1b. If above is possible, which program should I use and where to get 2.3.5 or whichever?
Click to expand...
Click to collapse
I also found a thread with a prerooted 2.3.6 ROM, and I read that I need to use Odin to patch it, so if I used that then rooted it again
Generally I'm asking if it's possible to downgrade, how, with what program, where to get ROM, and if not able to downgrade, then are there currently any known ways to ROOT 2.3.6/4.0 (ICS)?
Thanks so sosososososo so much!
ph0t0r said:
So, I finally received my Samsung Galaxy Player 4.2 in the mail. I live in Canada so I had it shipped.
DEVICE DETAILS:
MODEL: YP-GI1
ANDROID: 2.3.6
KERNEL: 2.35.7-CL1076053 [email protected] #1
BUILD: GINGERBREAD.XXXX3
Now, it was only after I did some googling that I figured out that it's very hard to root 2.3.6, which is what is running on my device, the GINGERBREAD release.
I have already tried the DooMLoRD_v4_ROOT-zergRush-busybox-su release to try to ZergRush the device, but with no luck, following results:
Of course, I did read a thread somewhere that it is hard to root 2.3.6.
Now a few questions,
[/b]
I also found a thread with a prerooted 2.3.6 ROM, and I read that I need to use Odin to patch it, so if I used that then rooted it again
Generally I'm asking if it's possible to downgrade, how, with what program, where to get ROM, and if not able to downgrade, then are there currently any known ways to ROOT 2.3.6/4.0 (ICS)?
Thanks so sosososososo so much!
Click to expand...
Click to collapse
Could you share the link of the pre rooted rom?
Sent using Tapatalk
ph0t0r said:
So, I finally received my Samsung Galaxy Player 4.2 in the mail. I live in Canada so I had it shipped.
DEVICE DETAILS:
MODEL: YP-GI1
ANDROID: 2.3.6
KERNEL: 2.35.7-CL1076053 [email protected] #1
BUILD: GINGERBREAD.XXXX3
Now, it was only after I did some googling that I figured out that it's very hard to root 2.3.6, which is what is running on my device, the GINGERBREAD release.
I have already tried the DooMLoRD_v4_ROOT-zergRush-busybox-su release to try to ZergRush the device, but with no luck, following results:
Of course, I did read a thread somewhere that it is hard to root 2.3.6.
Now a few questions,
[/b]
I also found a thread with a prerooted 2.3.6 ROM, and I read that I need to use Odin to patch it, so if I used that then rooted it again
Generally I'm asking if it's possible to downgrade, how, with what program, where to get ROM, and if not able to downgrade, then are there currently any known ways to ROOT 2.3.6/4.0 (ICS)?
Thanks so sosososososo so much!
Click to expand...
Click to collapse
This may be out of subject but where did you buy it?
@zaclimon: http://www.bhphotovideo.com/bnh/con...&AID=10603278&PID=1796839&is=REG&A=details&Q=
Choose to pay the duties and stuff with the final purchase, not on delivery, makes things very easy. Ordered it Thursday, came Tuesday, came a day late because some sort of company mixup, so very fast.
@klin1344: http://forum.xda-developers.com/showthread.php?t=1517194
PS. Sorry, but I had to make a new account, I accidentally put in the wrong email and I forgot my password for the account ph0t0r, so if an admin would like to delete the account or something that would be fine, just not this thread thanks, please don't ban me for this, I am not trying to spam accounts, just a goof. Very very Sorry.
xninja23 said:
@zaclimon: http://www.bhphotovideo.com/bnh/con...&AID=10603278&PID=1796839&is=REG&A=details&Q=
Choose to pay the duties and stuff with the final purchase, not on delivery, makes things very easy. Ordered it Thursday, came Tuesday, came a day late because some sort of company mixup, so very fast.
@klin1344: http://forum.xda-developers.com/showthread.php?t=1517194
PS. Sorry, but I had to make a new account, I accidentally put in the wrong email and I forgot my password for the account ph0t0r, so if an admin would like to delete the account or something that would be fine, just not this thread thanks, please don't ban me for this, I am not trying to spam accounts, just a goof. Very very Sorry.
Click to expand...
Click to collapse
LOL that's my own rom.
It's only compatible with the 4.0, not the 4.2. Please don't flash it as it will brick your player.
Sent using Tapatalk
xninja23 said:
@zaclimon: http://www.bhphotovideo.com/bnh/con...&AID=10603278&PID=1796839&is=REG&A=details&Q=
Choose to pay the duties and stuff with the final purchase, not on delivery, makes things very easy. Ordered it Thursday, came Tuesday, came a day late because some sort of company mixup, so very fast.
@klin1344: http://forum.xda-developers.com/showthread.php?t=1517194
PS. Sorry, but I had to make a new account, I accidentally put in the wrong email and I forgot my password for the account ph0t0r, so if an admin would like to delete the account or something that would be fine, just not this thread thanks, please don't ban me for this, I am not trying to spam accounts, just a goof. Very very Sorry.
Click to expand...
Click to collapse
Yes I alreafy bought the asus keyboard from them as they were not in any store. It is better with this option. I hope other US stores will do so.
klin1344 said:
LOL that's my own rom.
It's only compatible with the 4.0, not the 4.2. Please don't flash it as it will brick your player.
Click to expand...
Click to collapse
Shouldn't it be compatible across 4.0 to 4.2?
This is seriously legit bummer...
Again, back on topic, any known methods/safe to downgrade using Odin, if yes how?
xninja23 said:
Shouldn't it be compatible across 4.0 to 4.2?
This is seriously legit bummer...
Again, back on topic, any known methods/safe to downgrade using Odin, if yes how?
Click to expand...
Click to collapse
You CANNOT EVER use a ROM for one device on another device EVER EVER, you will BRICK your player every Galaxy player (3.6, 4.0, 4.0 and 5.0) all have there own specific ROMs and Kernels they are NOT cross compatible. the only cross compatibility is between the International and US versions of the same model as the only thing needed to get the home button working is the proper kernel.
the 4.2 has virtually ZERO development for it at the moment, it will probably take some time as none of the devs own one, and they need one to use to work from.
daniel644 said:
You CANNOT EVER use a ROM for one device on another device EVER EVER, you will BRICK your player every Galaxy player (3.6, 4.0, 4.0 and 5.0) all have there own specific ROMs and Kernels they are NOT cross compatible. the only cross compatibility is between the International and US versions of the same model as the only thing needed to get the home button working is the proper kernel.
the 4.2 has virtually ZERO development for it at the moment, it will probably take some time as none of the devs own one, and they need one to use to work from.
Click to expand...
Click to collapse
I would love to start developement though, seeing as I have one, and I'm interested in coding and stuff. Is there any fast way for me to start screwing around with the 2.3.6 code/whatever code to SOMEHOW get my device rooted, or exploitable?
my concern is that I don't want to lose TA/DRM keys just to root. not sure exactly what Ill be missing out on without it or if i can get the functionality back. also not sure, but if i do unlock bootloader, install the custom kernal, am i free to update the device with normal updates or will that break something? sorry, i went through a lot of the threads, but the info is a bit confusing and lots of redirects thru all the different threads.
edit, if you do unlock bootloader, can you relock without those keys? just worried for warranty purposes, i.e. if i get screen creaking and then can't return it cause i wanted to root but now i cant set it back to stock
No, it's not confusing, it's only confusing for people who are a bit lazy to really read.
It has been very clearly stated numerous times that ATM root is only possible with unlocked bootloader and losing TA data, because for a locked-bootloader-root an exploit is needed. It's very unclear whether such an exploit will be found or whether it's even possible.
You should ask Sony - I can't imagine that the service would refuse warranty when your screen creaks, because that problem very obviously has NOTHING to do with software modifications!
The DRM keys and X-Reality engine are superfluous anyway, so losing TA data should not be a concern when unlocking.
hasenbein1966 said:
No, it's not confusing, it's only confusing for people who are a bit lazy to really read.
Click to expand...
Click to collapse
I also found different statements regarding that matter. BECAUSE I read.
You should ask Sony - I can't imagine that the service would refuse warranty when your screen creaks, because that problem very obviously has NOTHING to do with software modifications!
Click to expand...
Click to collapse
Right !
The DRM keys and X-Reality engine are superfluous anyway, so losing TA data should not be a concern when unlocking.
Click to expand...
Click to collapse
DRM keys are superfluous to people who don't use DRM protected services. If you don't use that services, it doesn't mean others do the same.
X-Reality is a great feature. I compared two Z2s with and without X-Reality: The benefits are real obvious, sometimes close to overwhelming.
Losing X-Reality is the one and only reason for me not to root my Z2, yet.
thanks for the clarification. i wasn't being lazy, there are several threads that redirect to several other threads each (some of which aren't even about the z2 tablet specifically) and the message tends to get blurred after digging through several pages of threads that may or may not even have bearing on what you're trying to do.
i am assuming that without drm keys it will be impossible to return to stock (at least with working bravia engine and other protected services) would this be true? is there any work around to get these services back after you root, or are they gone forever?
also, my main reasons for wanting root are for removing restrictions on SD card, is there any non-root work arounds for this? (also xposed)
My z2 tablet should be arriving today, I am going to try to use it without root for a while to see if i can mentally deal without having xposed and full access to sdcard, hopefully i can hang, cause i'm not crazy about losing functionality (superfluous or not) forever from a brand new device i just paid lots of money for
also still trying to find clarification on updates, once unlocked & rooted can i just use regular updates or will that break the modified kernal and cause issues? i'm not sure if the modded kernals out there are for the latest version on firmware and how that is handled, all of my rooting experience just comes from flashing new updates of ROMs to my device (like AHRD or Hyperdrive), so i've never dealt with system updates to stock firmware while being rooted and unlocked.
thecrunked said:
... and the message tends to get blurred after digging through several pages of threads that may or may not even have bearing on what you're trying to do.
Click to expand...
Click to collapse
Exactly.
i am assuming that without drm keys it will be impossible to return to stock (at least with working bravia engine and other protected services) would this be true? is there any work around to get these services back after you root, or are they gone forever?
Click to expand...
Click to collapse
No workaround, yet, keys and X-Reality seem to be gone forever.
I just don't understand why Sony doesn't provide a means for backing up that data...
also, my main reasons for wanting root are for removing restrictions on SD card, is there any non-root work arounds for this? (also xposed)
Click to expand...
Click to collapse
Nothing known at present. :/
also still trying to find clarification on updates, once unlocked & rooted can i just use regular updates or will that break the modified kernal and cause issues?
Click to expand...
Click to collapse
No regular updates, you need to flash new firmware manually.
Note: I did not root my Z2, yet - because I don't want to lose DRM keys and X-Reality, so my answers are not based on my own experience.
copy this into the search forums
Rooting Sony tablet z2 keeping warranty with locked bootloader
Just reading this thread and something caught my attention; you lose x reality when you root.. Now if I root and keep stock firmware, I would assume I still have x reality. Please correct me if I'm wrong
meteor999 said:
Just reading this thread and something caught my attention; you lose x reality when you root.. Now if I root and keep stock firmware, I would assume I still have x reality. Please correct me if I'm wrong
Click to expand...
Click to collapse
You don't need to unlock your bootloader anymore (for .402 firmware), so you won't lose anything except for a security measurement
thecrunked said:
my concern is that I don't want to lose TA/DRM keys just to root. not sure exactly what Ill be missing out on without it or if i can get the functionality back. also not sure, but if i do unlock bootloader, install the custom kernal, am i free to update the device with normal updates or will that break something? sorry, i went through a lot of the threads, but the info is a bit confusing and lots of redirects thru all the different threads.
edit, if you do unlock bootloader, can you relock without those keys? just worried for warranty purposes, i.e. if i get screen creaking and then can't return it cause i wanted to root but now i cant set it back to stock
Click to expand...
Click to collapse
search "Rooting Sony tablet z2 keeping warranty with locked bootloader" in the forum search bar
I've rooted mine with a locked bootloader.
Currently, probably the easiest way to root it is to just use Towelroot. You will need to download the APK (via clicking the red icon on the site), save the APK, and install it. root it (via the application you just installed, just click the button!), then go over to the Google Play Store and download SuperSU (or any other root manager, altough it seems that SuperSU stands the most supported to date). It will probably ask you to update your SU binary (if it gives you an error doing so, just reboot the device). Once your rooted, head over to the Sony TA Backup forum, download the program (as I know of it only works on MS Windows), run it, and backup your TA's. If you ever need to restore your TA's, just run the script again and follow the menu in the command prompt to restore it (if I am correct it relocks the bootloader too).
Last note, if you need to restore your TA's, whatever you do, DO NOT USE SOMEONE ELSES! This will brick your device as I have read from many.
Also, if you want to unlock the bootloader, you can head over to http://developer.sonymobile.com/unlockbootloader/ and unlock it, however I would use it for a few months just in case if you can't relock it. I would recommend that you do not unlock it until you back up your TA's.
Hope this will save a few hours for some! If anyone wants me to clear up on something too you can ask.
I tried using Towelroot on my Z2 Tablet (SGP561; Build: 17.1.D.0.417) and it said it was successful, but I couldn't get SuperSU or Superuser to work no matter what I tried (and I previously had success rooting other devices) so I am assuming at the moment that it gave me a false positive on success.
I tried a few other methods each without success. Cyanogenmod doesn't support it and neither does "Safe Root". I did appear to have some success with Motochopper n7, but when it failed to reboot the device (didn't give me an option to do it manually) and then cleaned up.
Manually rebooting the device after it finished resulted in no improvements, but trying the Motochopper exploit again indicated that it recognized a previous rooting and so it failed for that reason:
Code:
[*]
[*] Motochopper: Android root exploit (Windows version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well. ;)
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2109 KB/s (1283460 bytes in 0.594s)
[*] Pushing root tools...
1952 KB/s (91980 bytes in 0.046s)
2296 KB/s (1867568 bytes in 0.794s)
2446 KB/s (969701 bytes in 0.387s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .
Of course, root checkers say the device isn't rooted, but on my towelrooted phone it says that anyway unless it is given super user privileges, so I have no way of knowing if it is rooted or if it isn't. I am inclined to believe that it isn't though because TA backup fails:
Code:
[ ------------------------------------------------------------ ]
[ Backup TA v9.11 for Sony Xperia ]
[ ------------------------------------------------------------ ]
[ Initialization ]
[ ]
[ Make sure that you have USB Debugging enabled, you do ]
[ allow your computer ADB access by accepting its RSA key ]
[ (only needed for Android 4.2.2 or higher) and grant this ]
[ ADB process root permissions through superuser. ]
[ ------------------------------------------------------------ ]
Waiting for USB Debugging...OK
Pushing Backup TA Tools...OK
Checking for SU binary...FAILED
Requesting root permissions...FAILED
=======================================
CLEAN UP
=======================================
Deleted file - C:\Users\Elliander\Desktop\Backup-TA-9.11\Backup-TA-9.11\tmpbak\r
ootPermission
Deleted file - C:\Users\Elliander\Desktop\Backup-TA-9.11\Backup-TA-9.11\tmpbak\s
u
Removing Backup TA Tools...OK
Killing ADB Daemon...OK
Press any key to continue . . .
I actually do want to Unlock the boot loader, it's just that I want to back up the DRM keys first. My tablet it already unlocked to be used with any carrier, but I think it's ludicrous that these types of restrictions are allowed on such expensive hardware. At the very least Sony should officially have a tool to backup the keys when unlocking so that it can be restored to the same device.
EDIT: When I looked in:
About Tablet > Status
On the bottom under "Rooting Status" it says "Rooted"
So I'm guessing my only problem is in getting the Super User binaries to work?
EDIT 2: BusyBox Installed (from Play Store) also says my device is rooted, so something I did in the above worked. Unfortunately, the install of Busybox also failed.
I don't know why you've had to jump through hoops, but search for "easyroot"
I ran v5 on the older firmware and v11 on the latest firmware 17.1.2.A.0.314, works perfectly, installed supersu from play store immediately afterwards.
FWIW towelroot did not work for me either on .314 but I never tried it on the last firmware
wintermute000 said:
I don't know why you've had to jump through hoops, but search for "easyroot"
I ran v5 on the older firmware and v11 on the latest firmware 17.1.2.A.0.314, works perfectly, installed supersu from play store immediately afterwards.
FWIW towelroot did not work for me either on .314 but I never tried it on the last firmware
Click to expand...
Click to collapse
It's a nice idea, but it doesn't work. "operation not permitted". Here's the output from Easy Root:
Code:
==============================================
= =
= Easy Root Tool v11 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
tr.apk not found. Trying to download from
https://towelroot.com/tr.apk
=============================================
######################################################################## 100.0%
=============================================
Extracting libexploit.so using 7z
=============================================
OK
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is SGP561
Firmware is 17.1.D.0.417
=============================================
Sending files
=============================================
221 KB/s (1585 bytes in 0.007s)
3452 KB/s (657704 bytes in 0.186s)
368 KB/s (1133 bytes in 0.003s)
1854 KB/s (9496 bytes in 0.005s)
2670 KB/s (13672 bytes in 0.005s)
Copying kernel module...
2805 KB/s (34473 bytes in 0.012s)
249 KB/s (767 bytes in 0.003s)
1659 KB/s (13592 bytes in 0.008s)
Kernel version is 3.4.0-perf-g31245c3
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading towelzxperia
=============================================
2211 KB/s (13592 bytes in 0.006s)
3211 KB/s (197320 bytes in 0.060s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
mount: Operation not permitted
cleaning up
Also, as I said before, my firmware is 17.1.D.0.417. Yours can't be the latest firmware if my firmware is a higher number. I'm still stuck in this limbo where some apps think it's rooted and other apps don't.
EDIT: Despite the error it gave me, I tried installing SuperSU by chainfire again and I seemed to get farther at least, but it failed. Rebooting to try again.
EDIT 2: It also gave me this error on my computer when I rebooted the device:
Code:
Checking if device is rooted...
error: device not found
Error: device not rooted
Press any key to continue . . .
But when I went into SuperSU it didn't give me any errors. I went into Root Explorer and it actually asked me if I wanted to grant super user privileges, but I don't think it's fully rooted though. The root folder is empty, and although I can see the files of other directories, it fails to touch a few things. I kind of expected that would happen to bootanimation.zip, but I also can't edit Platform.XML to restore write permissions. I have done this before on other devices so I know I was doing it correctly, but it just failed to edit. I even tried an app to do so, but it also failed. It's rooted enough to see the files and open them. I can even copy files otherwise hidden and it appears to be able to mount as read/write. It's just that it always fails to do anything with it.
I then went and installed "Mount /system (rw / ro)" and although it appeared to work successfully after granting it super user privileges, it still didn't allow me to edit the files in root explorer, so I installed FX and and it's root add on module. I tried to edit the files, but it wasn't mounted as "Read/Write" as far as it's concerned and when I tried doing so within it's menu it just said "Error" The operation could not be completed"
So... am I rooted or not? Easy Root definitely helped me get farther, but not far enough to actually do what I needed the root to do.
EDIT 3: After a few minutes, for some unknown reason, Root Explorer allowed me to edit Platform.XML to add <group gid=”media_rw” /> under WRITE_EXTERNAL_STORAGE (still won't work in FX though) and of course I still can't edit bootanimation.zip, but as a test I successfully moved some files from the internal memory to the 128 GB micoSD so I'm at least rooted enough to restore access to the SD card so I will give it some time to see how much I can do with it.
P.S. - There is a forum bug. When I edit posts on a tablet there are no problems, but when I do so on a computer it tells me I have to wait 5 minutes before writing a new post to prevent spam - even though it's not a new post, it's an edit of an old post. Just like there is a weird thing where it will let me post links in a tablet, but not in a PC. Unfortunately, there doesn't appear to be any bug report form or moderator contact links so just putting it here.
well sorry no idea what state you're in. I notice you are SGP561 (whatever the heck that is!!! ), I am SGP511.
Can only say that for my device, easyroot worked 100%.
EDIT: I think you are Verizon user? well in that case good luck and get used to it lol. Verizon always have different firmware / build for their devices so you're always in the XDA development minority. Sometimes exploits and/or unlock bootloader is never available.