Related
NOTICE: Gingerbreak is an exploit that has been fixed in many of the latest Android versions and releases. If it does not work, it does not work. I can't "fix" the exploit, you will have to wait for a new exploit to come out, or root a different way!
About
The GingerBreak APK is a wrapper around the newly released GingerBreak exploit (credits to The Android Exploid Crew), which is meant to attain root access on GingerBread. This specific exploit may work on various Froyo and Honeycomb versions as well.
What the APK and exploit do is as follows:
- The APK puts the right files in the right place to run the exploit
- The APK runs the exploit
- The exploit attempts to attain root access
- If it succeeds, the exploit remounts /system as read-write and runs the installer script
- The installer script attempts to install the su binary and superuser APK, and reboots
Some important things to know:
- You must have USB debugging enabled on your device
- You need to have an SD card (formatted and) inserted - if it doesn't work, try formatting the SD card in your computer, or switching it with a different (or old, etc) SD card
- The APK must be installed to device, NOT SD card
- The exploit may take a while to run, but not more than 10 minutes, if it does, get me a logcat, and reboot the device. In rare occasions, even if the device does not reboot, you may still have root. So check that out after you manually pull battery after 15 minutes or so of being stuck.
- Always reboot between root attempts!
- While (temporary?) root access may be attained, due to locked bootloaders, efuses, S-ON, and whatnot this may still not work on your device. For temproot purposes, use the raw binary exploit (linked below), not this APK.
- The GingerBreak exploit should not be used to attain temproot and continue using the device. It fscks vold, you do not want to be running like that. You want to reboot! So if the root doesn't stick, you (still) have a problem.
Installation
- Optional: Press the Thanks button below this post
- Make sure USB debugging is enabled
- Make sure you have an SD card (formatted and) inserted
- Get the APK on the phone somehow, and install it
- Open the APK, press the root button
- Wait a few minutes. If there are no problems, the device will reboot (note that the reboot itself can take like 10 minutes due to cache wipe)
- Make sure the Superuser app is install and working
- Optional: Install BusyBox from Market (I personally prefer the stericsson installer)
- Optional: Uninstall GingerBreak, you don't need it on your phone anymore
- Optional: Make a donation
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) - often this works (a fix for both issues is being looked at)
NO IT DOES NOT WORK ON THE GALAXY ACE (yet ?)
WORKS ON A RARE SGS2, BUT NOT ON MOST (seems to be only pre-release devices that are rootable this way)
ACER A500 / ICONIA Look here (click). Will eventually be integrated, I guess
Donate
Donate to Chainfire by PayPal: click this link
Donate to The Android Exploid Crew by PayPal: [email protected]
Report!
Please report back if it does or doesn't work on specific devices. If it doesn't, don't forget to post your logcat as attachment, and mention your device details and GingerBreak version.
Credits
- I made the APK and did some slight modding to the exploit code to install from an APK
- The exploit ("GingerBreak") itself is made by The Android Exploid Crew. Original code can be found here: http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
Manual rooting
From v1.1 it is no longer possible to manually root the device over an ADB connection using the files from this APK. Please use the original binaries from the c-skills website to do this. There are several guides posted here on XDA about how to do this manually, some are mentioned/linked-to in the first few pages of this thread.
Note
GingerBreak is not specific to any device, but there is code in there that may not work on device X or Y. The exploit is generic, but that does not mean one size fits all, nor does it mean that there will be no firmwares out there that fix this exploit. A special version may need to be compiled for your device, ask your favorite hacker from your specific device's forum. This APK is meant to make the process easier, but also adds dependancies so that it may not work on your device.
AGAIN, THIS DOES NOT WORK ON S-ON DEVICES !
Changelog
26.04.2011: v1.2
- Removed some code that may break operation while the code itself isn't needed
- Added UnRoot option
- The APK now logs exploit output semi-live
22.04.2011: v1.1
- Modded exploit code to not need /data/local/tmp - this should fix the problem extracting assets as well as be more compatible with various devices (in theory). In case the APK notices that this cannot work, it will warn you about this.
- Added some warnings and errors to the APK
21.04.2011: v1.0
- First release of APK
- Slight mods to the exploit source to have it work better from APK
Sources
Attached archive contains the modified sources for the exploit part of this APK. I will publish new versions only when it changes; the APK may be updated to a newer version, this does not necessarily mean the exploit has changed
Also, apologies for the few days delay in posting the source.
Genius tool!
Congrats to C-Skills to for the exploit of course.
PS: if you want it to work on Galaxy S II: extract in /app-cache instead of /data/local/tmp
Finally this has come out
Sent from my a Vibrant using the xda premium app
Will this work on any phone
Sent from my a Vibrant using the xda premium app
supercurio said:
Genius tool!
PS: if you want it to work on Galaxy S II: extract in /app-cache instead of /data/local/tmp
Click to expand...
Click to collapse
Will be looked at! (I'm sure it'll need more modifications for other devices as well, hehe)
I get an error saying 'could not extract assets'. Is there a solution for this?
Running 2.3.3.
Sent from my GT-I9000 using XDA App
I am trying to root using adb.
Can anybody tell how long will it sleep/wait after displaying
[*] vold: 1965 GOT start: 0x00014344 GOT end: 0x00014384
to complete the root
(@robin2)
try:
adb shell mkdir /data/local/tmp
will it work on Nexus S? Anyone tried yet?
please see the steps below
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb push gingerbreak /da
ta/local/tmp
586 KB/s (16830 bytes in 0.028s)
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb shell chmod 777 /dat
a/local/tmp/gingerbreak
E:\Downloads\New folder\SuperOneClickv1\SuperOneClickv1>adb shell /data/local/tm
p/gingerbreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0x6fd17f09 strcmp: 0x6fd37c89
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014344
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 1965 GOT start: 0x00014344 GOT end: 0x00014384
That's not my modded version, so don't ask me.
why would you need on a nexus s ??
it is one of the most simple phone to root and get superuser ...
there are many guides in the development section for the nexus s look there
i would much prefer to use one of those as i know it will work !!
I cannot create/remove any directories/files in /data/local/ because I don't have root access.
I've tried...
Sent from my GT-I9000 using XDA App
For those that want to root manually, you can follow this: http://forum.xda-developers.com/showthread.php?t=1044582
It's for a Nexus One (tested), so if you want to use the step-by-step for a different device, you will have to change the partitions in the mounting commands.
Hi! I have Nexus One and is currently on an unrooted 2.3.3
I placed the APK file on my SD card and when I tried to launch it, all I got was "could not extract assets" what should I do?
curiousitykilledthepat said:
Hi! I have Nexus One and is currently on an unrooted 2.3.3
I placed the APK file on my SD card and when I tried to launch it, all I got was "could not extract assets" what should I do?
Click to expand...
Click to collapse
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
The above post worked for me. Thanks.
Been thinking a bit about how things are done in the v1.0, going to do some massive changes for the next release that should make it much more compatible.
:/
it doesn't root the Desire S, unfortunately
Hi,
I was following the article :
[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6
@ http://forum.xda-developers.com/showthread.php?t=905003
.
The cursor blinks after this line:
Code:
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
I have waited for almost an hour, but nothing happens, and I have to break using Ctrl+C.
My questions is, what am I doing wrong/ what needs to be done? Cause I see other posts where the output shows many more lines similar to the one above, and then the # (root) prompt, but I don't get it.
-- Phone: HTC Desire HD [Unlocked]
-- OS: Just received OTA Gingerbread: 2.3.3; s/w version: 2.37.720.3
-- Factory Reset Done
-- PC Connection is in : Charging mode and USB Debugging
Complete output:
Code:
G:\htc desire hd\Mod\Setups\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb push GingerBreak /data/local/tmp
1173 KB/s (16830 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
G:\htc desire hd\Mod\Setups\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
Thanks in advance,
Gautam
Downgrade Failed
I got the same result.. Needed help.. :sad:
Same here. Any help would be appreciated
Ok guys even I am stuck here too and I had posted about this, but no one replied, however I got down to googling tactics and the most statisfying reason that I have come up with (reasoning is based on the countless articles and websites about gingerbread and gingerbreak) is that the gingerbreak crack is for a different version of of gingerbread, a version which was launched before we Indians, got out version of gingerbread and thats why our DHDs are getting stuck at the same place over and over again. It's all because of different s/w version numbers.
I guess we all have to wait for a gingerbreak version that is applicable across all DHD ROMs, only then can we be able to downgrade. There might be other way(s), but I know none. This is my two bit about what all of us, are going through when following the downgrade guide. I may be wrong, I may not be. If you have a different thing to say about it, then by all means let all of us hear it.
Thanks Ruben for the clarification. I think you're right. The following two links suggest that as well.
Check out (Google them as I can't paste links due to the less # of posts that I have):
Google Patches GingerBreak Exploit, But Don’t Worry – We Still Have Root (For Now)
Change Iab98d71c: Detect Android devices vulnerable to CVE-2011-1823
I was trying to downgrade so that I could install Android Revolution HD 5.1.7 on my DHD. Any other way to achieve the same? I wish I knew this; just updated to Ginger a few days ago.
The pleasure was all mine Gautam, just trying to do my part to help other Indian DHD users. anyways check out this page http://forum.xda-developers.com/showthread.php?t=905003&page=149 and I believe jkoljo is already on the job.
Unfortunately there is no other way to downgrade the gingerbread 2.37 hoping for an exploit from, The Android Exploid Crew and jkoljo.
is it cuz we are indians?
Same exact problem. Spent more than 24hrs finding a solution. Really bored of the stock ROM and the gingerbread update does not even have enough visual changes. Zzz really wish someone does something about it
Once again Indians have a disadvantage.
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
ericjennings said:
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
Click to expand...
Click to collapse
1st you will need the following files
GingerBreak from http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
misc_version from http://www.multiupload.com/A9PNGVBWBE
Default rom http://forum.xda-developers.com/showthread.php?t=905003
and Android SDK http://developer.android.com/sdk/index.html
Also you will need a clean SD card 1 gig or more should be fine (smaller is better)
Unzip GingerBreak and misc_version into a folder say c:\Downgrade (I normally use 7Zip)
You should have:
c:\Downgrade\GingerBreak with 5 Files
c:\Downgrade\misc_version with 4 Files
Make sure you installed Android SDK's Platform tools and updated your path to reflect this
IE: run SDK Manager and install Android SDK Tools and Google USB Driver pack if you don t have HTC Sync driver running.
Format the SD card and copy the rom.zip into the base of the card, not a sub directory. (Do not unzip)
Now: Plug in the phone to the USB and make sure Debugging is on and the phone is set to charge only.
Then open Command prompt ie: run cmd.exe
Go to your Downgrade directory and test if your adb command is in the path. ie: run it and make sure it lists switches and not say file not found
Then run as follow
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
adb shell
./data/local/tmp/GingerBreak
if you fail to get root ie: prompt does not return to # or get a endless sendmsg() failed? Error, reboot the phone and repeat the commands above. The phone I used, took 3 tries to get this right.
at the # run the following
cd /data/local/tmp
./misc_version -s 1.31.405.6
When its done exit cmd and goto your phone, Reboot it while pressing volume down.
It will come up with a menu and follow the update instructions.
You should then be on Android version 2.2 when done.
Please note the rom that is supplied works with unbranded phone only if you have a branded phone you will need to make a goldcard. If you want to know how to make one, google is your friend sorry.
You must have htc sync installed!
**** I TAKE NO RESPONSIBILITY IF THE BELOW PROCESS DOES NOT WORK FOR YOU & IF YOU BRICK YOUR PHONE - DO THIS AT YOUR OWN RISK ****
What you need :
- MicroSD card with SD Adapter
Procedure :
1. You need to setup ADB on your PC and download the Android SDK, guide here:
How To: Set Up ADB/USB Drivers for Android Devices | The Unlockr
2. Create a GoldCard here (remember to open the SD Card as a PHYSICAL DISK) :
How To: Create a Goldcard | The Unlockr
3. Download the Generic Software here :
http://androidfiledepot.com/Storage...ravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
4. Insert the Goldcard into the Desire and connect it to your PC. Run the software downloaded in step 3.
5. This will flash your Desire with a generic HTC version of the OS.
6. Enjoy!
If you see error 131, you don't have htc sync!
Nilseby, thanks for the suggestion.
I tried your method, and the process starts; phone switches off and HTC in displayed in White. After a few minutes, it says, that it can't go through with this, and the program just hangs. I powered on the phone and it's back to the way it was. Flashing didn't go through. I created a gold card as well and formatted, still no luck.
2.37.720.3
Why, oh why did I upgrade to 2.37.720.3?
I actually wanted to root my DHD so that I could take screenshots of its screen. Now that it is being reporting that as of now 2.37.720.3 is not downgradable, is there any other way to take screenshots of my phone's screen? Other than, of course, taking pics with another camera.
Thank God!
I am using RCMIX HD Kingdom v 1.2 with Sense 3.0 on my DHD and when I saw I downgrade guide from Gingerbread to get root access, I decided to upgrade to the official 2.3.3 in India. I saw the initial posts in that thread say that the method worked really well.
I had almost made up my mind to try the official update knowing that I can downgrade using the guide, but just before doing that I thought I'd read the more recent posts and guess what I realized the Indian software number 2.37.720.3 cannot be downgraded! Which means no root access and no custom ROMs (at least for now). I immediately changed my mind and didn't upgrade.
Thank God!
Good decision av. Just wait till this issue gets sorted out and then dive in. I was too eager to see what was up with Mr.Ginger and curosity killed the cat.
Sent from my Desire HD using XDA App
We in Australia have the same problem regret upgrading.
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
guitarist7 said:
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
Click to expand...
Click to collapse
yeah..
now i cant do anything with it
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
DotNetRules said:
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
Click to expand...
Click to collapse
What do you mean by getting a GoldCard to work? Is the phone not mounting it or something?
i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled
anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing
update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market
is it even posible to root this phone?
i guess im not allowed to be helped or somthing.
i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun
Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/
My SE Xperia Pro MK16i was previously rooted using DooMLoRD's Easy Rooting Toolkit. The software has just been upgraded to version 4.0.2.A.0.62 which then resulted in the complete loss of Root Access. I tried to re-root using DooMLoRD v4, but without success. This resolved the problem after the last software upgrade, but this time it has not worked and now I am really stuck. Any help would be much appreciated.
The script reads as follows:-
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
866 KB/s (23060 bytes in 0.026s)
--- 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
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] 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
3511 KB/s (1075144 bytes in 0.299s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 156260 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 . . .
Thanks
to me it's the same
i don't find the form to root my phone mk16 with the new version, and i read in too much sites and i dont find anything.
Hi,
Sorry that you are having the same problem rooting version 4.0.2.A.0.62.
I have ended up using WotanClient to flash the software back down to version 4.0.2.A.0.58 to enable me to re-root my Xperia Pro with DooMLoRD v4. Flashing wiped the phone's settings as expected, and losing root meant that I could not make backups of everything before going down this path. It took me quite a while to reconfigure the phone even though all the apps were easy to re-download from my Google account at Android Market. I was hoping that OTA Rootkeeper could then be used to help upgrade to version 4.0.2.A.0.62, but the filesystem does not seem to support root protection. Creating a separate Ext3 partition on the SD card did not make any difference and I cannot find any other information on how to make it work. This is a real pain.
Anyway, at least I now have a rooted phone with the previous software and Titanium Backup is functioning once again. I have used Titanium to freeze the update service in order to stop the constant OTA notifications regarding the availability of the software version 4.0.2.A.0.62. There is no way that I shall upgrade unless somebody discovers a straightforward exploit to root the new version. I am now beginning to doubt whether this will happen anytime soon.
I downgraded my SE Xperia Pro to 4.0.2.A.0.58 and rooted it. Will I lose root if I update OTA? Also, will I lose my apps and settings?
I used to backup my rom data via ClockworkMod on my HTC Desire Z and restore it after an update, but there's no CWM for the Xperia Pro.
SE Xperia Pro OTA Software Update
My understanding is that you will not lose root or settings and apps with an OTA software update for the Xperia Pro. However, for some reason the update failed when I tried using this method to upgrade from version 4.0.2.A.0.58 to version 4.0.2.A.0.62. I am still looking for a solution to this problem. Please post here if you are successful.
I have flashed my phone over wotan server to. 42, after that I have rooted over the flash tool, and instaled titanium backap pro and uninstaled all necesery apps (facebook...moxier, fun and downloads and others) and try to upgrade to .62, and phone says me that is unable to upgrade software... Phone works great, but why I cant upgare software? Is it because I uninstaled some sistem apps which doesnt have any thing whit system works?
Sent from my MK16a using XDA
SE Xperia Pro OTA Software Update
I did exactly the same and had identical results. The fact that we have both uninstalled some unnecessary apps using Titanium and then been unable to upgrade using the OTA software update method could be the reason why it does not work. It probably counts as having modified the system folder. However, I am not prepared to go through all the trouble of re-flashing my phone in order to reinstall the missing apps and then try again.
The best solution would be if somebody could find an exploit to root version 4.0.2.A.0.62 directly. I would then simply upgrade the phone using SE PC Companion and avoid all the other problems.
Xperia pro software
Now i flashed again my phone to .42, roted, and upgradet sucsefuly to .62, root is still here, and now i will remove all necesery apps.
So, first flash than root, than upgrade, and make your phone like you want.
Hi guys, I have bought a new Xperia Pro MK16i with 4.0.2.A.0.58, not rooted yet. I get a notification about availability of OTA update to 4.0.2.A.0.62. What are the best steps to root my phone? Note: I want to uninstall some SE apps too.
muchotravka said:
Hi guys, I have bought a new Xperia Pro MK16i with 4.0.2.A.0.58, not rooted yet. I get a notification about availability of OTA update to 4.0.2.A.0.62. What are the best steps to root my phone? Note: I want to uninstall some SE apps too.
Click to expand...
Click to collapse
Hey! Don't update your phone until you root it (I'm sure you already know this). To root it, you can use this method: http://forum.xda-developers.com/showthread.php?t=1320350
It's very easy to follow.
Before you do it, though, you'll need to install the ADB (Android Debug Bridge) drivers, which you can find here, in Sony's website: http://developer.sonymobile.com/wportal/devworld/downloads/download/sonyericssonxperiaproxperiarayxperiarayso-03cdrivers?cc=gb&lc=en. Or you can also install it using a tool called SDK Manager (that's how I installed the driver). An easy tutorial: http://www.invialgo.com/2011/install-adb-for-android-phone/
After you root it and before you make any changes (unnistalling system apps...), update via OTA (not through PC Companion!) to firmware .62 and after that's done, you should still have root and will be able to do what you want with your XPro. It's very easy.
Is using the wotanclient the best way to downgrade to be able to root my phone, I have already upgraded the phone and it is not unlocked/modded in anyway at present.
Suition Shinobi said:
I downgraded my SE Xperia Pro to 4.0.2.A.0.58 and rooted it. Will I lose root if I update OTA? Also, will I lose my apps and settings?
I used to backup my rom data via ClockworkMod on my HTC Desire Z and restore it after an update, but there's no CWM for the Xperia Pro.
Click to expand...
Click to collapse
I just tried to downgrade my phone from .62 to .58 using WotanClient.
For some reason there was an error during firmware flashing
[SSL] Error 12152
Error: file header write failed!
CUST file write failed
and the whole process just stopped. I tried to restart but the WotanClient
said no credit which means the Euro1.99 i just bought was gone with the error
This is so disappointing. I tried to recover my phone which is now just a piece of brick by installing a new software (repair phone) via it SonyPCcompanion but it seems like the PCcompanion couldn't connect to
the phone.
Help please!!!
donno what to do now. if I try to flash it again with WotanClient, will it work? should I go to version .58 or .42?
Can you Please tell me how to do that?
MutleyB said:
My understanding is that you will not lose root or settings and apps with an OTA software update for the Xperia Pro. However, for some reason the update failed when I tried using this method to upgrade from version 4.0.2.A.0.58 to version 4.0.2.A.0.62. I am still looking for a solution to this problem. Please post here if you are successful.
Click to expand...
Click to collapse
Can you Please tell me how to Downgrade from 4.0.2.A.0.62 to 4.0.2.A.0.58?
Flash it with flashtools using a ftf image?
Sent from my MK16i using XDA
I know this is a very old post, but it describes exactly my problem.
I recently bought the Xperia Pro, and it has version MK16i 4.0.2.A.0.62
I tried to root it but it gave me the error as described in the first post.
I assume there is no real solution, so I am asking for advice if it is worth the trouble by downgrading, rooting and then upgrading again?
Currently the phone has locked boatloader.
Honestly, all I want to do is to get root access so I can disable some pre-installed apps from "Disable Service"
Any advice is appreciated:good:
The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Confirmed Working
Confirmed. Works as described.
Nice work!
Thank you for this information, works excellent.
Ron Overdrive said:
The Nextbook 8 (NX008HD8G) is a $99 tablet available from Walmart. It sports a AMLogic AML8726-MX SoC (1.5Ghz dualcore Cortex-A9 w/400mhz dualcore Malli400 GPU), 1 Gb of DDR3 RAM, 8" display, and 8Gb internal storage. Its a nice little budget tablet for those who don't need a Nexus 7 or greater performance rated tablet. Not too long ago I discovered how to root it and apparently I'm the first to do it as far as I can tell. Now here's how.
What you will need is Bin4ary's One Touch Root App. This app will get you only partial root via the ADB Shell. My guess is the ADB exploit he uses does work to get basic root access for ADB, but some incompatibility prevents proper installation of su & SuperUser.apk. What we're going to do is finish the job manually.
First run Bin4ary's app and use the Normal Method. Be sure to ignore all errors. After your tablet reboots move su and Superuser.apk from Bin4ry's app folder to the root of the Internal SDCard. Next you will need ADB. If you don't have it you can get it either from Bin4ary's app folder you found su & superuser.apk in or you can install the Android SDK. At the command prompt enter the following:
Code:
adb shell
su
At this point you should see a # sign indicating root privileges. If you do enter the following commands.
Code:
mv /system/xbin/su /system/xbin/osu
cp /sdcard/su /system/xbin
chmod 6755 /system/xbin/su
The use Astro or your favorite file manager to navigate to /sdcard and install SuperUser.apk then reboot your tablet. From here on you should have full root on your tablet. Credit should definitely goto Bin4ry for his work on his One Touch Root App for getting us half way there.
Click to expand...
Click to collapse
Did NOT work for me.
1-On first attempt, got pound sign....tried to push code resulting in cant find SD
2-On second attempts, would not let me be superuser su
3-Did a factory reset....same results as (2)
Im stomped!....please help
Amlogic Next8HD8G (NX008HD8G) Modified Recovery - Stock Rom - Root & Gapps
Modified recovery, stock rom, flashable root and flashable Gapps here: http://www.freaktab.com/showthread.php?7010-Amlogic-Next8HD8G-%28NX008HD8G%29-Modified-Recovery-Stock-Rom-amp-Flashable-Root
ShaunMT
Confirmed as well..
Ty... no fusses at all..
zenkillizen said:
Ty... no fusses at all..
Click to expand...
Click to collapse
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
andrew09 said:
I need someone to be more clear on rooting this device because I already bricked one using the method from tab freaks instructions aren't that clear and I don't want to brick another one ! Please thanks
Click to expand...
Click to collapse
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Aiko0923 said:
this guide is like the clearest root guide I've seen Just sit down and read it, take your time Rooting my seem hard at first, but you catch on
Click to expand...
Click to collapse
Parts are missing from the guide like how to install the adb drivers the computer needs to recognise the tablet first before u try and root it I have read through it and I've already bricked one also I noticed if you go to recovery on this tablet it erases the system and factory reset doesn't fix anything there's no factory ROMs or anything to fix it if it messes up. If someone can't a sure me that the method is correct I'll do it I'll try it.
Does this method work on the newer models say model number starting with YFG12 and up?
I bought this today.
I am having problems here:
I did what you said to do:
Normal Mode enabled!
Pushing busybox....
4806 KB/s (1165484 bytes in 0.236s)
Pushing su binary ....
7134 KB/s (104576 bytes in 0.014s)
Pushing Superuser app
6792 KB/s (2139595 bytes in 0.307s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
---
And then I copied the files su and the .apk to /sdcard
Then I try to run su, and it says:
su
/system/bin/sh: su: not found
so I do
[email protected]:/sdcard $ ./su
/system/bin/sh: ./su: can't execute: Permission denied
---
Other times, it just does this:
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
and it runs forever
what do I do?
http://www.cydiaimpactor.com/
Worked for me.
YES! use cydia impactor
H0wdy said:
http://www.cydiaimpactor.com/
Worked for me.
Click to expand...
Click to collapse
Yes, I used it also. worked for me too (my serial for the tablet is YF07... in case there is a problem with the newer versions)
Thanks, H0wdy
Steps to do it:
Download Cydia Impactor
Turn on USB debug in settings-> Developer options
Plug in tablet into PC (I used a 32 bit Windows 8.1)
Wait a while... a long while for me... for windows to download drivers, disconnect tablet, wait a few seconds, then reconnect.
you should see in the device manager (on the top) android phone and underneath Android Composite ADB interface
Unzip Cydia, run impactor.exe and just choose start for # drop SuperSU su to /system/xbin/su
Wait a bit, then you're done. (no reboot or anything else necessary).
Install supersu (or I guess any other superuser app) from the android market. It will tell you that you can update the su binary... your choice, I updated without a problem.
I had supersu installed beforehand, but I guess it has nothing to do with it, it wasn't working anyway)
Ranting, but maybe someone has this issue also:
One ( -- BIG --) problem I had was getting the connection between the tablet and my computer, and Not because I can't plug-in a cable
the tablet said it was connected, but on the computer, nothing showed up in device manager and the list of devices kept refreshing.
The PC was beep-ing just like it found a device. the device list would refresh once or twice, then again beep, all this till the end of my patience.
At first I thought it was the USB 3.0 port, then the cable, then the ESXi USB redirection (my desktop is actually a VM), then the windows version, then the architecture,
Then I switched to a laptop, nothing.. same story.
I can BET it's Sony's F***ed up drivers
So, I used a clean system (no other adb or phone drivers installed) and worked as a charm
I think I hat this much trouble because I had a lot of other drivers (for sony, samsung, universal adb, etc etc.)
So on the computer I had all this stuff installed, it looked like the tablet was connected, then disconnected in the space of 10-15 seconds, then repeat forever.
If this happens to you, use a clean windows.