Related
Looks like the boot.img on the WiFi only model is slightly different. Flashed the rooted boot.img file and now I'm stuck at the Dual Core technology screen. Anyone have this available. All help greatly appreciated!
UPDATE
See thread -> http://forum.xda-developers.com/showthread.php?p=12432218
Can someone post the stock xoom wifi dump of the boot.img, recovery.img, system.img, and userdata.img in case something happens?
Apparently it looks like its slightly different than the wifi+3g version. Also is the overclocked kernel file working posted by coolbho3000?
i need the answer too... i m comfused.
Alright I have a stock Xoom tablet now Just gotta figure out how to pull the boot.img file off. Any ideas and I'll do it ASAP.
No clue mate. From my knowledge you have to be rooted, or have the SDK on your pc. I think. Neither which are available as of now
So is the wifi only version able to be rooted as of now?
currently, yes. We need a new root method. Well I would not say a new "method" but their need to be some modifications done to the original rootboot img file. Shouldnt be hard for devs
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Issue 1: Don't currently have root
Issue 2: No SD card access
But I did try it and got an access denied.
onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
B Dizzle said:
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
It's actually a Permission issue.
/dev/block/platform/sdhci-tegra.3/by-name/boot: Permission denied
So someone with root needs to run it. Anyone wanna help out? Im not getting mine till tomorrow but by then I suppose you would have yours exchanged
Sent from my Nexus One using XDA Premium App
B Dizzle said:
So someone with root needs to run it.
Click to expand...
Click to collapse
That's actually the catch-22... can't get root because we don't have the right boot.img file. I think it's going to boil down to Motorola releasing a stock one.
If anyone is up for IRC chat - hop onto Freenode and room #Xoom
I can try if someone tells me what needs to be done. I tried copying it over to another folder in root explorer but no luck.
Update: Ran through the fastboot oem unlock in hopes that it would resolve the Permission Denied. It did not.
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
destroyerbmx said:
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
Click to expand...
Click to collapse
You'll end up with a (soft)brick
No luck
I also booted into fast boot, tried and still got no permission sometimes and no such directory some times... If some one will walk me through getting the img file I will gladly do so
how can I remove the softbrick, I saw this AFTER I tried to root and now I cannot even turn it off, just sitting on the Motorola Dual Core Technology screen.
ok I also now need to the stock boot.img from a wifi xoom. Can anyone help? I can flash it if someone can provide it please, if not I guess I will go exchange my xoom in the morning.
will the arc get root with zergrush oneclick have tried it but doesnt work, is it possible to get this to work with arc?
I'm interested too!
I followed the guide for the play, it worked flawlessly.
Sent via subspace beacon from my Arc.
Hi!
This works for ARC!!! 4.0.1.A.0.283 at least. Was able to remove bloat through adb. Wohoooo....no more worries of getting the 0% battery(if you don't need permanent root).
Works flawlessly on 4.0.2.A.0.42 Xperia Arc here. Just use the pdf guide, you can't go wrong
Works for Xperia Pro (MK16i) on 4.0.1.A.0.283 as well
Does it work with 4.0.A.2.368 ?
maciek51 said:
Does it work with 4.0.A.2.368 ?
Click to expand...
Click to collapse
It should do, seems to be fairly universal.
Thank you Lord Takyon
The pdf file is way detailled but as I'm not an expert of such commands, is there any risk of doing something wrong ?
As the root is temporary, I don't think so... right ?
maciek51 said:
Thank you Lord Takyon
The pdf file is way detailled but as I'm not an expert of such commands, is there any risk of doing something wrong ?
As the root is temporary, I don't think so... right ?
Click to expand...
Click to collapse
I think the danger of doing something harmful is quite minimal. if you do it wrong you just can't get rooted. The exploit itself is temporary(until reboot) and gives you
root over adb shell, but you can make it "permanent" by pushing the su binary and Superuser.apk to the phone. But I actually like that you have the option to just root until next reboot - so you can remove bloat via adb or modify system files and if you don't want to run any root apps that is exactly what you need.
thank you m2kk
Pushing su binary and superuser makes it permanent, you mean permanent until the next reboot, right ?
In any case, I reboot my phone very rarely (airplane, etc.) otherwise, neally never and the procedure seems to be short enough to be reproduce time to time.
I will try it in the evening and I will report
maciek51 said:
Pushing su binary and superuser makes it permanent, you mean permanent until the next reboot, right ?
Click to expand...
Click to collapse
Nope, if you do it by the book you will have a fully rooted phone and the root survives reboot.
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 9.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download: CF-Auto-Root-manta-mantaray-nexus10.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
From the OP... i marked in bold the important part.
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
fastboot oem unlock
I would suggest taking a look at mskip and wugfreshs toolkits located in the original development and development section of the nexus 10 forums respectively for a simple way to unlock your bootloader.
Sent from my SCH-I535 using xda premium
Good to see nexus 10 getting all this support from Android gurus here on xda ...but again it's a nexus device ...me glad I bought it ...extremely happy with my purchase thanks chainfire for this easy root method as usual it works
So if this doesn't unlock your device, why does the OP state:
Note that if your device had not been unlocked before, this procedure will wipe all your data !?
Does rooting/installing SU wipe this device?
His previous version didn't wipe the device, so I'm guessing this one doesn't either
Didn't need to unlock boot loader to root
shimp208 said:
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Are you sure? The script in the ZIP in OP has the following command:
Code:
tools\fastboot-windows.exe oem unlock
Does that not issue a unlock? Is it necessary to run this command?
hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help
d0nald01 said:
hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help
Click to expand...
Click to collapse
Please re-download, I've included the missing file in the new package.
now its stuck at waiting for device
when i plug in my n10 on bootloader screen, i hear the bad connection to usb sound, the 3 note sound, not the usual 2 note sound when i the connection is good.
but i am still able to see my n10 when i boot it up normally and can transfer files etc
am i missing something?
Thanks for this tool, works perfectly.
I'm also stuck on "waiting for device" also. any way around this?
Edit: Downloading and installing full drivers fixed it.
Big thanks, I was stuck in a bootloop, but this got me out of it!
Worked perfect (Debian)
Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks
idefix_sin said:
Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks
Click to expand...
Click to collapse
Sure, I used it again to root the device after taking the 4.2.1 update.
Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.
From the first post:
Chainfire said:
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Click to expand...
Click to collapse
mieszk3 said:
Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.
Click to expand...
Click to collapse
Seems pretty obvious to me. I didn't put it in bold red letters because it's irrelevant.
Hello, i am using LG optimus G E975. The phone information are as follows:
Android ver: 4.1.2
Baseband Ver: APQ8064/MSM9x15M
Kernel Ver: 3.4.0
Build Number: jZ054K
Software Ver: E97510e-525-05
Telco: Starhub(singapore)
Could anyone provide me with a foolproof guide to rooting? i previously managed to root a Samsung s2. However, after searching for very long, i am unable to find a root method specifically for the E97510e software. Could any kind person provide me with a guide & recovery method?
Thank you
*edit* before someone scolds me for noobness or not bothering to check, i have came across this
http://forum.xda-developers.com/showthread.php?t=2181103
and
http://forum.xda-developers.com/showthread.php?t=2050582
However, as stated in the guide, the version should be Settings>About phone>Software information..Software version - LS970ZV_ ?
My version is completely different, hence the request for help
The zvb method will work for you
Shelnutt2 said:
The zvb method will work for you
Click to expand...
Click to collapse
Thank you for your reply sir. Is this the one? Or this
As for recovery, in case i need to return it for warranty repairs, could you point me in the right direction?
Nuker22110 said:
Thank you for your reply sir. Is this the one? Or this
As for recovery, in case i need to return it for warranty repairs, could you point me in the right direction?
Click to expand...
Click to collapse
Either, but this one is just freshed up a bit:
http://forum.xda-developers.com/showthread.php?t=2181103
Shelnutt2 said:
Either, but this one is just freshed up a bit:
http://forum.xda-developers.com/showthread.php?t=2181103
Click to expand...
Click to collapse
My information:
Android ver: 4.1.2
Baseband Ver: APQ8064/MSM9x15M
Kernel Ver: 3.4.0
Build Number: jZ054K
Software Ver: E97510b-EUR-XX
I have tried rooting with the aforementioned root method, but it doesn't work while doing it from a mac og linux box. The last confirmation "if uid=0(root)...." It's never displayed, uid=2000 or something is always displayed. Could you help me troubleshoot?
I would post in the original thread but I haven't made enough replies to post in a dev thread yet.
a0peter said:
My information:
Android ver: 4.1.2
Baseband Ver: APQ8064/MSM9x15M
Kernel Ver: 3.4.0
Build Number: jZ054K
Software Ver: E97510b-EUR-XX
I have tried rooting with the aforementioned root method, but it doesn't work while doing it from a mac og linux box. The last confirmation "if uid=0(root)...." It's never displayed, uid=2000 or something is always displayed. Could you help me troubleshoot?
I would post in the original thread but I haven't made enough replies to post in a dev thread yet.
Click to expand...
Click to collapse
Remove G_security from the root of your sdcard and try again, if you have an g_security from an old method it messes it up.
wargreymon89 said:
Remove G_security from the root of your sdcard and try again, if you have an g_security from an old method it messes it up.
Click to expand...
Click to collapse
Thanks for responding!
I don't seem to have a folder, nor a file named G_security in the root of my sdcard. This is the output i get in the terminal on both my mac, and in Ubuntu 12.04:
Code:
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
If uid=0(root), gid=0(root) is displayed
EDIT: Found the file on the phone itself, but after deletion, it still fails with the same error.
a0peter said:
Thanks for responding!
I don't seem to have a folder, nor a file named G_security in the root of my sdcard. This is the output i get in the terminal on both my mac, and in Ubuntu 12.04:
Code:
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
If uid=0(root), gid=0(root) is displayed
EDIT: Found the file on the phone itself, but after deletion, it still fails with the same error.
Click to expand...
Click to collapse
I used the .bat version, and there is a slight difference in the Linux .sh one, it is missing the row "adb root".
So just for the sake of trial and error, add so it says:
adb root
echo.
adb shell id
EDIT: Also notied fiddy just updated the Linux script, be sure to delete the G_security on your phone before you do any tries. And download the script again from http://forum.xda-developers.com/showthread.php?t=2181103
wargreymon89 said:
I used the .bat version, and there is a slight difference in the Linux .sh one, it is missing the row "adb root".
So just for the sake of trial and error, add so it says:
adb root
echo.
adb shell id
EDIT: Also notied fiddy just updated the Linux script, be sure to delete the G_security on your phone before you do any tries. And download the script again from http://forum.xda-developers.com/showthread.php?t=2181103
Click to expand...
Click to collapse
Still no luck, now it won't even push anything to G_security. It won't recognize my device anymore.
Tool root cho E975e
a0peter said:
Still no luck, now it won't even push anything to G_security. It won't recognize my device anymore.
Click to expand...
Click to collapse
1/.Set driver + USB Debugging + Charge Mode Only
2/. Run CurrentRoot.bat file to root and follow the instructions
---------- Post added at 11:57 PM ---------- Previous post was at 11:53 PM ----------
a0peter said:
Still no luck, now it won't even push anything to G_security. It won't recognize my device anymore.
Click to expand...
Click to collapse
send mail to me, I transfer lin
[email protected]
lelong3010 said:
1/.Set driver + USB Debugging + Charge Mode Only
2/. Run CurrentRoot.bat file to root and follow the instructions
Click to expand...
Click to collapse
That is not an option on Linux. Currentroot.bat is not linux compatible.
Hello again. Last night my phone had a new push update labeled 10g. Upon attempting to update, it came back with an error saying that the phone cannot be updated due to root. My current firmware.is E97510f-525-05.
I have again attempted to research. Are these the proper steps to update?
Go to supersu and select full unroot, update to 10g and using the previous zv9-zv method to root?
Am I correct? Or is there an easier method to update the firmware without unrooting and rooting?
unroot with supersu doesn't work.
you have to install the latest KDZ to unroot
skdubg said:
unroot with supersu doesn't work.
you have to install the latest KDZ to unroot
Click to expand...
Click to collapse
Is there another way to update without unroot? And will the old root method work with the new 10g firmware?
you cannot install official upates with rooted phone.
this is the same like all android phones
you have to install KDZ to unroot and relock the bootloader
What is the change log for 10g? Is it worth the trouble to update?
there are no changelogs for official updates
lelong3010 said:
1/.Set driver + USB Debugging + Charge Mode Only
2/. Run CurrentRoot.bat file to root and follow the instructions
---------- Post added at 11:57 PM ---------- Previous post was at 11:53 PM ----------
send mail to me, I transfer lin
[email protected]
Click to expand...
Click to collapse
oh Vietnamese ^^
nice to meet u at here
When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I updated the firmware to 10.1.1.....253 then I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance
mahmoud.kunbaz said:
When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance
Click to expand...
Click to collapse
u already posted in Q & A the same thing
demonicjas said:
u already posted in Q & A the same thing
Click to expand...
Click to collapse
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again
mahmoud.kunbaz said:
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again
Click to expand...
Click to collapse
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again
mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Click to expand...
Click to collapse
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.
Linwood.Ferguson said:
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.
Click to expand...
Click to collapse
Thanks alot for your reply but I really don't understand why this device (ZL) is being ignored like that
I have opened a thread here about that http://forum.xda-developers.com/showthread.php?t=2293512
so many ZL users are complaining and unfortunately things are not going well
mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again
Click to expand...
Click to collapse
Yup, please read a lot and read the feedback. It will help you to gain ur confident.
Sent from my BlackBerry 9900 using Tapatalk
butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
tried rootkeeper - doesn't work. (currently on 434 with locked BL)
Thread closed, use the post linked by the op three posts above