Related
Viewpad 7 rooting
I tried to root with superoneclick 1.7 (rageagainstthecage)
but it remount the system with read only access? and i am not able to use busybox or rom manager to install clockmod, any advise please?
"SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1090 KB/s (1062992 bytes in 0.951s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
822 KB/s (26264 bytes in 0.031s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1366 KB/s (196521 bytes in 0.140s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!"
I can use adb shell to go into the device and do a SU, but when i do a chmod to system directory to do a clockmod, it wont work as it is read-only..
seeking advice on this one..
Thanks!
bump.. any help????
help???????
Dumb question: have you tried with:
Code:
adb remount
And then:
Code:
adb shell
chmod
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
HeeroYuy84 said:
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
Click to expand...
Click to collapse
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
brainmaster said:
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
Click to expand...
Click to collapse
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
This one works for my VPAD7 running Froyo 2.2.2 (which I believed is the newest OEM ROM) - http://android.modaco.com/topic/343143-rooting-and-installing-clockworkmod/
Add'l VPAD7 hardware/firmware info - 2.6.32.9 and 1008_3.350
Download & install ES File Explorer and copy the *.apk file in the link to your microSD card - restart phone, run the apk and then install cwrecovery, etc. Read & follow the directions in the modaco link carefully, and you should be fine.
A word of caution - the older ROMs written for VPAD7 are NOT compatible with the newest touchscreen ("ITE") hardware. FYI - the Clean Viewpad7 V1.0 ROM might or might work. Have a BACKUP of your original stock/oem first done before doing any custom ROM flashing.
Good luck !
HeeroYuy84 said:
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
Click to expand...
Click to collapse
Is busybox installed in the same subdirectory or folder as your adb and/or fastboot ?
From within the shell, do you see a $ at the beginning of the prompt line - indicating that SU is off. If you see a # at the beginning of the each prompt line - then SU is on and you are good to go.
Before running the su command, try running the mount command first. Give it a moment and between these 2 commands issued, if it switch to a # command without error messages, then you've been granted SU access, and, you should be good to CHMOD & flash, etc. etc.
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
Click to expand...
Click to collapse
Trying to recall how I did mine as DW has the VPAD7 now ....
Assuming you are connecting your unrooted, stock VPAD7 to a Windows-based PC for the first time, it should be recognized as a new USB / removable devices, etc. - and will auto-install a few drivers & go thru the setup sequences, and when it's done, you will seee "hardware installed & ready to use" - including PC Tools for synch. calendars & address book with MS Outlook.
Disconnect & reconnect the phone, and the upper status bar should indicate "USB connected" - open it & you are prompted to turn it "ON" and generally speaking, USB debugging mode box is checked. If not, click & bring up your device's settings, look in Application settings and then under Development, it should be the 1st. box.
Again, this is fairly basic so I suggest doing a bit more reading first and know what you are doing to root, or get someone with a bit more hands-on experience to help. If not done right, you COULD semi-brick your VPAD7 although the process to root to gain SU access is "relatively" safe - but it's tricky & took me a little while to get it done right.
The latest stock/OEM ROM running Froyo 2.2.2 is fairly good overall, has full access to Google Market for apps downloading, and only needs a few minor tweaks and add-ons as enhancement to make this tablet "fly" on the run - and the OS is stable with decent battery life (although I wouldn't mind seeing Gingerbread on it - my HTC Eris is running 2.3.5 now) Even after you gained root, you might want to leave the ROM as is and use it - I'm doing that now (rolled back from one of the few "working" custom ROM).
Good luck ! ------ and, BACKUP, BACKUP, and BACKUP
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
Click to expand...
Click to collapse
hi
for debugging mode go to
Settings>applications> development (here u chek the USB debugging ) that's all
for rooting i have used gingerbreak it worked for me
can also read the below two links
link 1 : http://forum.xda-developers.com/showthread.php?t=1015005
link 2: http://forum.xda-developers.com/showthread.php?t=1156034
hope it help goodluck
I finally succeed into rooting and installing Clockwork into the viewpad, that how I did :
1. GigerBreeak 1.2 (install apk)
2. Download BuxyBox instaler 1.19.2
3. Terminal :
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system 4. follow: android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
flash_image recovery /sdcard/cwrecovery.img
tricky one to remount the partition, but that was the missing link for me.
I have tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started.
Gil
GilViking said:
tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started
Click to expand...
Click to collapse
Are you running Vista, Win7 or XP SP3, try using a different PC and/or OS - uninstall any installed USB drivers for the device, reboot & try it again.
Also, are you using the provide micro-usb cable or using a generic one, try a different one.
Lastly, while "waiting for device" message is showing, quickly unplug & reconnect the micro-usb cable to the pad, and, wait - be patient.
If you still cannot do it (SOC 1.7 is proven to work best, newer ones are NOT) - use the GingerBreak apk instead.
Thank you!
I will try your recommendations later today (West Coast USA).
Successfully Rooted VPad7
I finally got it rooted. It appears that my problem was neglecting to run stuff as administrator on my Win7 Pro. I ended up using SuperOneClick v 1.7 which is not that easy to find.
Thanks to all who helped and wrote the software!
Gil
Hallo,
Im a newbee also in android rooting, i had some question and clarification about some terms and hope someone can share their knowledge.
Here are some of my questions:
Im confused with the img backup file of each partition. Does redirecting again to each partition mean restoring the individual img file to each partition ex"cat /sdcard/mtd3_recovery.img > /dev/mtd/mtd3"
or we need a tool like in linux which is DD or DDRESCUE or something else.
For instance my backup individual partition img file i created before i install costum rom. If im correct in restoring the individual image file to each mtd partition is possible does it means im
back to the state where i used the original stock or before i installed the costum rom. Its like in linux where if u restore a dd root image file to the partition you will back to the state where you created
the image backup.
Does NANDROID backup means using a CWR recovery to backup the original/stock+rooted rom and restoring it using the same process from a costum rom will means im back to the state of original/stock+rooted rom
Im still in the rooted state right now. i just want to understand a few things like restoring to original/stock+rooted before i procedd to installing costum rom and other tweeking on the device.
Hope someone can share some info.
Thanks in advance.
Here's a quick guide to general principles of flashing ROM's (and factory RUU) in the Wiki section of XDA, and there's another sub-section of FAQ, please refer to it as a newcomer (we all were at one point ...)
http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
It's best NOT to mess around with individual *.img until you move beyond beginner's level to a higher "comfort" zone - in general, we use the tools already built-in by CWM - which has a submenu with functions for Backup, Restore (and, advanced & selective Restore)
It will create and read from the sub/directory created on the mSD card, and use it to accordingly.
You are rooted at this point, it is VERY important to go into Recovery Mode with CWM already installed/working, and make a Backup of your stock/factory ROM in its current state, this is your baseline - and, save a copy to your computer (Windows preferred) Make sure you write down any settings as necessary for future reference ...
Then, you can explore and install custom ROM by flashing the Zip saved/moved to the mSD card - and go thru the initial Setup steps. When your new ROM is working & stable, running smooth - go back into Recovery & do a Backup (a new subfolder will be created with everything you need to Restore later on, if & when needed - it will be time/date stamped for easy reference.)
If something go wrong, boot into Recovery, then select Restore & highlight your last known working saved Rom, and it will prompt you to reboot/restart once it's done. **
After a while, it will become second nature - just remember ** to always do a full wipe (dalvik, cache & system) when changing custom ROMs (which you should & will learn along the way - to clean the device of any old, residual codes & settings, etc.)
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?
Firstly a big thank you macexplorer who again found the relevant links amongst much Japanese.
See the original thread on rooting the F-01D:
http://forum.xda-developers.com/showthread.php?t=1611484
Following are quick instructions on how to upgrade the device to ICS. All your data will remain intact, but the /system partition is completely wiped.
NB: YOU WILL LOSE ROOT IF YOU FOLLOW THESE INSTRUCTIONS. YOU WILL NOT GET ROOT BACK.
To be clear, at the present moment in time, you need to CHOOSE BETWEEN ICS OR ROOT, you can't have both. The official upgrade below completely reflashes the system partition, so tools like OTA RootKeeper will not help you. The new release is more secure than ever and at current we don't know a new way to get root. If anyone finds any new information, please speak up
DISCLAIMER: Following these instructions might brick your device, void your warranty, etc. This is unlikely since you're basically installing an official update, but to be clear, I disclaim any and all responsibility for any (permanent) damage that might be caused by these instructions. DO AT YOUR OWN RISK.
The original instructions are here (or see in Google Translate)
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
My instructions are slightly different, aimed at more advanced users, and serves the file direct from my server (I found the original server quite picky in terms of refer and user agent, and also slow. I'm also serving the unzipped version, since compression was 0% anyways).
PRE-REQUISITES
At least 50% battery (ideally more in case things go wrong...).
Settings -> About, make sure Android version is 3.2, and Build number is either V28R43A (as recommended on the official page) or V19R36D (what I had; it worked for me but YMMV).
Settings -> Storage, at least 1.5 GB free in "Built in storage" (try installing first to external SD card and let me know if it works.. it's a lot safer).
ICS UPGRADE FOR F-01D
Download F01D_TO_SP_ICS1.enc and put it in /sdcard (md5sum: 2014d0254568a4ef955b21476012a9b5)
Boot into recovery (power off, hold down both volume keys and power up), select "update firmware" and press the power button agin.
Pay attention... the first time I tried this, it rebooted back in to recovery part way.... if this happens, just repeat step 2 above and make sure the progress bar completes all the way.
After this, it will reboot a few times, don't worry. Boot 1 will do the "optimizing android apps" screen, Boot 2 will be "upgrading calendar, contacts, etc..." and Boot 3 will say "finishing upgrade" and let you use the system.
If anyone has any leads on re-rooting the device, speak up. From my initial observations security is tighter than ever, so this might be a problem... but there are clever people out there
Regarding root
No leads for now. We can create /data/local.prop using the ICS/JB restore technique, but unfortunately the new firmware is completely ignoring either this file or the ro.kernel.qemu property.
If I understood the google translated Japanese correctly, this guy got to the same conclusion, and is now looking for other solutions. I wish him luck because after spending the day on this I have to get back to my real work
http://blog.huhka.com/2012/09/arrows-tab-lte-f-01d-icsshell-root.html
Temporary Root
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
shame on the dandroids..
Post upgrade restart errors?
Hi, slightly off-topic but related - has anyone had issues after upgrading with google maps? Whenever I start google maps it will hang and then restart my tablet.
Essentially google maps is now unusable which is very annoying. Please let me know if anyone has experienced this too and if so if they have a solution to the problem.
Many thanks in advance!
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
longdau12 said:
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
Click to expand...
Click to collapse
Help me :crying:
macexplorer said:
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
Click to expand...
Click to collapse
FINALLY..ROOT on F-01D for V08R31A
I hope someone is still using the F-01D. So here's to you diehards.
After many many failed attempts, i finally managed to get a more permanent root.
Probably others have got this to root, but I havent seen anything come up via searches.
Main stumbling block has been in getting the address of 'ptmx_fops'. Finally got it thro, rootkitXperia_20131207.zip (get_root..this prints but fails in ptrace; ptrace is blocked in f01d)
I have just managed to get a permanent root. The steps maybe little approx. Do verify and let me know. Its non-destructive, so no harm done.
but do at your own risk..and other standard disclaimers apply
Steps:
1. do the temp root as per : http://forum.xda-developers.com/showpost.php?p=33071441&postcount=3
2. get the exploit source from https://github.com/fi01/unlock_security_module
(recursive download)
3. compile the source. this will generate a libs/armeabi/unlock_security_module binary
4. add the following recs to the device_database/device.db
these are kallsyms kern func addresses; most are avail direct from kallsyms, except for ptms_fops.
Code:
sqlite3 device_database/device.db
insert into supported_devices values(187,'F-01D','V08R31A');
insert into device_address values(187,'commit_creds',3221986012);
insert into device_address values(187,'prepare_kernel_cred',3221985196);
insert into device_address values(187,'ptmx_fops',3229222484);
insert into device_address values(187,'remap_pfn_range',3222251308);
insert into device_address values(187,'vmalloc_exec',3222293708);
5. push device.db and unlock_security_module to /data/local/tmp/
6. simply run from /data/local/tmp: ./unlock_security_module as the root obtained temp earlier.
7. after sometime, this will say LSM disabled!!
8. now remount /system as rw. carefully copy su binary to /system/xbin/ (pref use the latest version from SuperSu).
Also copy Superuser.apk to /system/app
>>carefully copy means: chown/chgrp /system/xbin/su to "0"; set perms: chmod 06755 /system/xbin/su.
9. copy busybox from /data/local/tmp to /system/xbin; and install (./busybox --install -s /system/xbin/
10. At this stage, su doesnt seem to work for newer shell connections (must do _su and then su). probably due to the exploit messing up the kernel.
11. reboot. and enjoy your newly permanent rooted status.
12. after reboot, still cannot do system remount as lsm is back to original. rerun the unlock_security_module should disable this.
maybe even move this to /system/xbin/;
But this seems to destabilise the system.
Its not possible to use a lsm disabler ko insmod. the kernel sec mech validates the module with path and hash.
So it has to be: unlock security; do your thing with /system etc., reboot.
(not sure yet if any changes to /system/buid.prop will help)
Do let me know how this works out and point out errors in the steps.
And as luck would have it there is a new ICS release out on 5-Feb.
https://www.nttdocomo.co.jp/support/utilization/product_update/list/f01d/index.html
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/data/download.html
(F01D_TO_SP_ICS2.zip)
This moves the version to V12R33B.
Do not hazard to update to this, if you want to keep this root. this release probably fixes many of the exploits.
the wifi model seems to have got 4.1..wonder is something will trickle down to f01d.
Hello all,
I've been looking around the forum (and elsewhere online) for anyone who was able somehow to root the
Prestigio PMP5770D Duo tablet. It has stock ICS 4.0.4.
I'm a complete newbie in regards to tablets but I've been playing around with the X10 for a long time.
I'm thinking of using Flashtool to try and root it somehow, instead of the ADB shell which zimmbadroid tried already.
The only issue i am facing now is:
Since it is not rooted, i cannot use Titanium backup (or any other tool) to fully backup it, in case anything will go wrong
while trying to root it.
Does anyone else here (which is much experienced with rooting tablets) have any other ideas?
I'm always open to new suggestions.
Primary concern is HOW to fully backup it, in order to restore it to its current state (if anything goes wrong).
Thanks in advance.
I have same tablet, and same problem
npantos said:
I have same tablet, and same problem
Click to expand...
Click to collapse
+1
Sent from my PMP5770D using xda app-developers app
I have rooted Prestigio PMP 5570C today
dta1eros said:
Hello all,
I've been looking around the forum (and elsewhere online) for anyone who was able somehow to root the
Prestigio PMP5770D Duo tablet. It has stock ICS 4.0.4.
I'm a complete newbie in regards to tablets but I've been playing around with the X10 for a long time.
I'm thinking of using Flashtool to try and root it somehow, instead of the ADB shell which zimmbadroid tried already.
The only issue i am facing now is:
Since it is not rooted, i cannot use Titanium backup (or any other tool) to fully backup it, in case anything will go wrong
while trying to root it.
Does anyone else here (which is much experienced with rooting tablets) have any other ideas?
I'm always open to new suggestions.
Primary concern is HOW to fully backup it, in order to restore it to its current state (if anything goes wrong).
Thanks in advance.
Click to expand...
Click to collapse
I have rooted Prestigio PMP 5570C today
It was difficult, because system filesystem hasn't free space to copy su and superuser binaries to it.
I decomposed update.img to system.img boot.img kernel.img etc.
Next I mounted system.img as ext4 partition and delete some unnecessary apk with reclaiming free space (rm -rf filename).
Next I copied su binaries and set permisions and owner to it.
Finally I have unmount system.img and flash it back to tablet by RK30update without creating update.img back.
5570C has fortunately firmware to flash it by Rockchip Batch tool - thus it is easy modify it and this kind of firmware is necessary to unbrick tablet in any case.
5770D hasn't those kind of firmware - it has only SD card based update image.
I would try upload firmware from 5770D to 5570C (it is safe, because I have Rockchip batch tool friendly image to flash original FW back)
by converting it to system.img kernel.img and system.img files and upload them by RK30update tool.
maras77 said:
I have rooted Prestigio PMP 5570C today
It was difficult, because system filesystem hasn't free space to copy su and superuser binaries to it.
I decomposed update.img to system.img boot.img kernel.img etc.
Next I mounted system.img as ext4 partition and delete some unnecessary apk with reclaiming free space (rm -rf filename).
Next I copied su binaries and set permisions and owner to it.
Finally I have unmount system.img and flash it back to tablet by RK30update without creating update.img back.
5570C has fortunately firmware to flash it by Rockchip Batch tool - thus it is easy modify it and this kind of firmware is necessary to unbrick tablet in any case.
5770D hasn't those kind of firmware - it has only SD card based update image.
I would try upload firmware from 5770D to 5570C (it is safe, because I have Rockchip batch tool friendly image to flash original FW back)
by converting it to system.img kernel.img and system.img files and upload them by RK30update tool.
Click to expand...
Click to collapse
Nice work
I hope pmp5770d gets root soon, because its really nice gadget.
Sent from my GT-I9001 using xda app-developers app
zimmbadroid said:
Nice work
I hope pmp5770d gets root soon, because its really nice gadget.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Nice work maras77.
Hope it works for the 5770D. I'll be waiting to hear for any news. Take your time with it.
Every other tool i've tried failed so far...
Cheers
Hello!
Did you try Root MANY ANDROID!? It worked for me.
Best regards,
tungdil
tungdil said:
Hello!
Did you try Root MANY ANDROID!? It worked for me.
Best regards,
tungdil
Click to expand...
Click to collapse
PMP5770D? Which rom version? I tried that method 2 times with no sucess.
Sent from my GT-I9001 using xda app-developers app
zimmbadroid said:
PMP5770D? Which rom version? I tried that method 2 times with no success.
Click to expand...
Click to collapse
Hello zimmbadroid!
In the settings I find the following (cut some lengthy entries to what i believe is essential):
Model: PMP5770D
Android-Version: 4.0.4
Kernel-Version: 3.0.8-ge04d3bb
Build number: PMP-5770D_20121109_V2.0.14
I flashed the device with a zip-File I downloaded from Prestigio's home-page. This version disappeared when the updated their site in December but I believe it is the same one as this one here (sorry I cannot yet post links) yf.value4it.com/Service_Files/TabletPC/PMP5770D/PMP5770D_20121109_V2.0.14.zip.
[Wrong]
As far as I remember I installed a terminal emulator APP before using root-Many and executed some commands in the terminal on the tablet when root-Many asked to do so in the terminal on the PC.
[/Wrong]
Edit: It seems I did not remember correctly . After looking at RunMe.sh, and at my tablet (found some left-over's from the rooting process) I believe I did in fact use the "Special Mode". I also installed the terminal emulator. But the special mode uses its own Term.apk.
Hope that helps somehow,
tungdil
tungdil said:
Hello zimmbadroid!
In the settings I find the following (cut some lengthy entries to what i believe is essential):
Model: PMP5770D
Android-Version: 4.0.4
Kernel-Version: 3.0.8-ge04d3bb
Build number: PMP-5770D_20121109_V2.0.14
I flashed the device with a zip-File I downloaded from Prestigio's home-page. This version disappeared when the updated their site in December but I believe it is the same one as this one here (sorry I cannot yet post links) yf.value4it.com/Service_Files/TabletPC/PMP5770D/PMP5770D_20121109_V2.0.14.zip.
As far as I remember I installed a terminal emulator APP before using root-Many and executed some commands in the terminal on the tablet when root-Many asked to do so in the terminal on the PC.
Hope that helps somehow,
tungdil
Click to expand...
Click to collapse
Thanks for your reply.
I also updated tablet with that update.zip but didnt try to root it since update. Im gonna try your method ASAP and report it here.
Cheers
Edit: Did you lose any of your data in root process?
Sent from my GT-I9001 using xda app-developers app
zimmbadroid said:
Thanks for your reply.
Edit: Did you lose any of your data in root process?
Click to expand...
Click to collapse
No, not that I am aware of. However, the number of apps installed while rooting was quite limited, and no private data such as e-mail addresses, etc. on the tab.
Hope it's gonna work for you as well...
tungdil
Hello guys,
Tried the root many android but it did not work for me.
I actually tried it in the past, but thought hey, whats one more time?
Does anybody have any news on this?
I'm seriously considering selling it and purchasing the 8' one which seems to be easily rootable.
The fact is that i am quite pleased with its performance.
BR,
Eros
dta1eros said:
Tried the root many android but it did not work for me.
Click to expand...
Click to collapse
Hello dta1eros,
did you try it using Windows or Linux? It seems I am the only one here who could successfully root the 5770D with rootMany (I used Linux); had ICS 4.0.4 installed. Very strange
Where in the process did you get stuck? What was the result?
Regards,
tungdil
P.S.: Maybe using the tool multiple times, as described in here (sorry still cannot post external links: rootzwiki.com/topic/34162-root-kindlefire-7hd-probably-the-other-2ndgen-kindlefire/#entry1054645) would help? The guy wrote:
... failed the first few times, but selecting normal mode and running the exploit 5-6 times finally got me root.
Click to expand...
Click to collapse
Note: I also checked the "qemu-method" described in the post, but right now think it won't work. However, after multiple reboots the behaviour of the tablet changed (didn't complete Android start-up until I removed /data/local.prop again). That's what makes me believe running the tool multiple times could help.
PMP5770D Duo rooted!
Hello all,
To any owners of PMP5770D DUO still looking to root their device, it has finally worked! Confirmed just now - 14/3/2013.
Its been a while now, so i thought to come back and see if there were any updates regarding this request i posted.
After going through this thread, i noticed also that the "Root MANY ANDROID! [Upd: 11.03.2013]" had been updated.
So, i downloaded the latest version "Root_with_Restore_by_Bin4ry_v21" from the respective thread.
Extracted contents to a folder easy to go to via command line, and run the batch file. (RunMe.bat)
My suggestion is it would be better to open a command prompt and execute the batch file (not double clicking it from explorer)
This way, if anything goes wrong or process gets stuck you may see whats happening.
Anyways, lets get on with it.
Before proceeding, make sure tablet has Debugging ON and ALL ADB drivers are installed on your computer.
I performed this on Win7 x64 just fine. The tablet info is exactly as i bought it:
Model number: PMP5770D
Android version: 4.0.4
Kernel version: 3.0.8-ge04d3bb [email protected] #98
Build number: PMP5770D_20121109_V2.0.14.IMM761.user.root.20121109 (this is dumb's prestigio latest release)
I will post the entire procedure here so this will be quite long. At certain points, you will see that there are sections starting and ending
with these {{ and }} . This is me explaining what actually is happening to the tablet so in case it happens to you as well, then don't worry.
At some points you may see errors like "FAILED_ALREADY_EXISTS". This is because i actually had run this process more than once
while trying different options etc until i got it working. So, if anything needs mentioning, it will be in {{ }}.
Also, in Bold text are the options i selected through out this batch file.
>RunMe.bat
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (11.03.2013) v21 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
1318 KB/s (314540 bytes in 0.233s)
pkg: /sdcard/tmp/Term.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
2603 KB/s (1085140 bytes in 0.407s)
2712 KB/s (380532 bytes in 0.137s)
2607 KB/s (1468798 bytes in 0.550s)
2454 KB/s (469980 bytes in 0.187s)
mkdevsh
onload.sh
onload2.sh
packages.xml.sed
remount.sh
VpnFaker.apk
_su
Please look at your device and click "Restore my data"
{{ At this point the tablet will pop up a window asking you to choose to Restore My Data or Not }}
{{ Simply click on Restore My Data option and continue }}
1st RESTORE OK, hit ENTER to continue.
Press any key to continue . . .
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click "Restore my data"
{{ click on Restore My Data again and continue }}
Achieved! hit ENTER to continue.
Press any key to continue . . .
cp: can't open '/data/system/sync/stats.bin': Permission denied
cp: can't open '/data/system/sync/status.bin': Permission denied
cp: can't open '/data/system/sync/accounts.xml': Permission denied
cp: can't open '/data/system/sync/pending.bin': Permission denied
cp: can't open '/data/system/netstats.bin': Permission denied
cp: can't open '/data/system/throttle/temp': Permission denied
cp: can't open '/data/system/called_pre_boots.dat': Permission denied
cp: can't open '/data/system/registered_services/android.content.SyncAdapter.xml': Permission denied
cp: can't open '/data/system/registered_services/android.accounts.AccountAuthenticator.xml': Permiss
ion denied
cp: can't open '/data/system/inputmethod/subtypes.xml': Permission denied
cp: can't open '/data/system/accounts.db-journal': Permission denied
cp: can't open '/data/system/netstats_xt.bin': Permission denied
cp: can't open '/data/system/netpolicy.xml': Permission denied
cp: can't open '/data/system/entropy.dat': Permission denied
cp: can't open '/data/system/users/0.xml': Permission denied
cp: can't open '/data/system/users/userlist.xml': Permission denied
cp: can't open '/data/system/wallpaper_info.xml': Permission denied
cp: can't open '/data/system/accounts.db': Permission denied
cp: can't open '/data/system/batterystats.bin': Permission denied
cp: can't open '/data/system/usagestats/usage-20130314': Permission denied
cp: can't open '/data/system/shared_prefs/log_files.xml': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission denied
cp: can't open '/data/system/appwidgets.xml': Permission denied
failed on '/data/system' - Permission denied
failed on '/data/app' - Permission denied
mkdir failed for /data/app, File exists
failed on '/data/local/tmp/VpnFaker.apk' - Permission denied
/system/bin/sh: cannot create /data/system/packages.xml: Permission denied
Need to reboot now!
Waiting for device to come up again....
{{ RIGHT AT THIS POINT, tablet did reboot but root process was stuck here}}
{{ what i did to resolve this issue, was simply to unplug the usb cable }}
{{ from the tablet and plug it back in - while this command window was open}}
{{ after that, the process proceeded as follows}}
Unlock your device, a Terminal will show now, type this 2 lines, after each line press ENTER
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
after this is done press a key here in this shell to continue!
If the shell on your device does not show please re-start the process!
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Press any key to continue . . .
{{ AT THIS POINT, a command shell opened up on the tablet and i did try to execute }}
{{ the above shell scripts mentioned. However when i tried to go to the /data/local/tmp }}
{{ directory, it seems that in my case /data/local/ was empty or inaccessible. }}
{{ I tried switching to root, even searched for any onload.sh files in the whole filesystem, }}
{{ but with no luck. Eventually, i simply hit Enter to continue the batch-file (here, not on the tablet }}
{{ Procedure procedeed as below - with one more reboot }}
403 KB/s (1241 bytes in 0.003s)
Almost complete! Reboot and cleanup.
Waiting for device to come up again....
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
{{ and here is where the batch file process ends }}
After the whole process was done, i didn't expect anything to happen, but in any case
i thought i'd check with Root Checker - to see if anything had changed.
To my suprise, it seems that this new updated version of Root many android worked.
So, download from the forum the "Root_with_Restore_by_Bin4ry_v21" from POST "Root MANY ANDROID! [Upd: 11.03.2013]"
To sum it up,
I would like to personally say THANK YOU to all contributors for this!
I know i speak on behalf of all PMP5770D DUO owners who have been waiting for this for a while.
To the forum Admins, you may now close this thread or POST somewhere a Sticky that this has been resolved.
Also, if you have a list, please update it --> PMP5770D DUO rooted successfully!
Thanks again and if anyone has trouble doing it, please PM me anytime for help.
Updated 5770 (New OS4.1 (V2.0.25) upgrade is available. Please check Downloads section) can’t be rooted
Process stuck in multiple stages, everything gives error/failure, terminal do not open after restart, second "Restore My Data" problem...
I tried Device type option 1 and 2, nothing works.
dzukela_bg said:
Updated 5770 (New OS4.1 (V2.0.25) upgrade is available. Please check Downloads section) can’t be rooted
Process stuck in multiple stages, everything gives error/failure, terminal do not open after restart, second "Restore My Data" problem...
I tried Device type option 1 and 2, nothing works.
Click to expand...
Click to collapse
Have you tried going back to ICs and then running the rooting tool?
I've also upgraded to Jelly Bean and its also failing to root, I'm going to go back to ICS and retry.
Gboss01 said:
Have you tried going back to ICs ...
Click to expand...
Click to collapse
That isn't an option.
No ROOT is 4.1 JB. HELP!!!
gamballl said:
No ROOT is 4.1 JB. HELP!!!
Click to expand...
Click to collapse
i also have JB and also failing to root i might have to downgrade to ics to root my device but JB has some extra features i need for e.g wifi sleep when in stand by, if anyone knows a way to root JB please post on this thread as it is needed
i was wondering if there is any flash recovery mods available for this device as i have rooted my HTC Sensation XL using the flash recovery and that worked fine, i know you have to unlock the bootloader and i have read in a post somewhere that the new sony tablets are already unlocked (i do not know if this device is unlocked) also is there a way to push/embed the root files needed into the update.zip file so you can update the device with the new firmware already rooted, i am going to look into this more as i only got my tablet yesterday and this is the only thread that i have seem to find anything about the PMP5770D
if anyone has trouble finding ADB drivers for this device i installed them using the google Nexus 7 drivers
Device: PMP 5770D
Android Ver: JB 4.1.1
FW ver: 2.0.25
JB root zip test
i have created an custom update with root enabled but not tested yet so idk if it works if you try this please report any problems/issues about this
the link to the download is in the text file named URL
install using this zip file and the two other files that come with the default update, put them on your sdcard boot into recovery and install
Jelly bean 4.1.1 update
Doesn't work downgrade using official firmware from prestigio and root using any root
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.