I got an update, 13.3.2.2. I'm confused, how do you stop updates for sure?
Also, I forgot to say that I found this website, which claims to be a rooting website, I checked the supported devices on it and the HDX appeared. I can't try it now, but if anyone else can, please do. Do not laugh if I'm wrong, though. Thanks for the support!
http://www.srsroot.com/supported
Here you can find the KFHTWI. Yay!
ferrouskid said:
http://www.srsroot.com/supported
Here you can find the KFHTWI. Yay!
Click to expand...
Click to collapse
I have the KF HDX 8.9 running 14.3.2.1_user_321093620. SRS found no vulnerabilities to exploit.
My RESULTS:
---= SRS One-Click-Root v4.7 =---
17:26:51 - Starting ADB Server..
17:26:56 - Manufacturer: Amazon
17:26:56 - Model: KFAPWI
17:26:56 - Android Version: 4.2.2
17:26:56 - Build ID: JDQ39
17:26:56 - Board ID: apollo
17:26:56 - Chipset Platform: msm8974
17:26:56 - Getting OffSets.. : 0x8003 0x8005 (False)
17:26:56 - Query Server for Best Method.. Not Found (SmartRoot not possible yet)
----= Start Rooting Process.. Please Wait =----
17:26:58 [+] Testing exploit: root1 (Please wait some minutes)....
17:26:58 [+] Executing root1 exploit Failed, Proceed next...
17:26:58 [+] Testing exploit: root2a (Please wait it can take some minutes)....
17:27:00 [+] Executing root2a exploit Failed, Proceed next...
17:27:00 [+] Installing exploit: root3c (Please wait...)
17:27:03 [+] Select 'FRODO' or 'ARAGORN' or 'LEGOLAS' on your device, then click OK
17:27:24 [+] Removing Exploit.. Please Wait..
17:27:32 [+] Analysing Results...
17:27:32 [+] Root Failed: Resume Exploit 4.
17:27:32 [+] Testing exploit: root4 (please wait..)
17:27:35 [+] Device Reboot #1 (Wait till it's started)
17:28:59 [+] Device Reboot #2 (Wait till it's started)
17:30:04 [+] Executing root4 exploit Failed. (Root Error: 0)
17:30:04 [+] Testing exploit: root4b (please wait..)
17:30:11 [+] Device Reboot #1 (Wait till it's started)
17:31:23 [+] Device Reboot #2 (Wait till it's started)
17:33:34 [+] Testing exploit: root5 (please wait..)
17:33:35 [+] Unlock your device screen, it should bring up restore mode.
17:33:49 [+] Press RESTORE button on device NOW! then wait...
17:34:21 [+] Device Reboot #1 (Wait till it's started)
17:36:40 [+] Executing root5 exploit Failed. (Root Error: 0)
17:36:40 Auto Root Failed on this device.
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
Worth a try, but it looks like they left a lot of space for the OS to work with...
"16GB (10.9GB available to user) or 32GB (25.1GB available to user), or 64 GB (53.7GB available to user) of internal storage"
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
Technically this should work, but I'm pretty sure there is a way to delete update files. I found a nifty application called "Android Commander" which a allows you to access the system files on the HDX from the pc. Unfortunately you can not modify anything without root, but I'm hoping someone can figure out a hack for that, if it is possible than maybe the boot loader could be unlocked. And you are probably thinking what I'm thinking, AOSP ROM here I come!
matt101 said:
I have the KF HDX 8.9 running 14.3.2.1_user_321093620. SRS found no vulnerabilities to exploit.
My RESULTS:
---= SRS One-Click-Root v4.7 =---
17:26:51 - Starting ADB Server..
17:26:56 - Manufacturer: Amazon
17:26:56 - Model: KFAPWI
17:26:56 - Android Version: 4.2.2
17:26:56 - Build ID: JDQ39
17:26:56 - Board ID: apollo
17:26:56 - Chipset Platform: msm8974
17:26:56 - Getting OffSets.. : 0x8003 0x8005 (False)
17:26:56 - Query Server for Best Method.. Not Found (SmartRoot not possible yet)
----= Start Rooting Process.. Please Wait =----
17:26:58 [+] Testing exploit: root1 (Please wait some minutes)....
17:26:58 [+] Executing root1 exploit Failed, Proceed next...
17:26:58 [+] Testing exploit: root2a (Please wait it can take some minutes)....
17:27:00 [+] Executing root2a exploit Failed, Proceed next...
17:27:00 [+] Installing exploit: root3c (Please wait...)
17:27:03 [+] Select 'FRODO' or 'ARAGORN' or 'LEGOLAS' on your device, then click OK
17:27:24 [+] Removing Exploit.. Please Wait..
17:27:32 [+] Analysing Results...
17:27:32 [+] Root Failed: Resume Exploit 4.
17:27:32 [+] Testing exploit: root4 (please wait..)
17:27:35 [+] Device Reboot #1 (Wait till it's started)
17:28:59 [+] Device Reboot #2 (Wait till it's started)
17:30:04 [+] Executing root4 exploit Failed. (Root Error: 0)
17:30:04 [+] Testing exploit: root4b (please wait..)
17:30:11 [+] Device Reboot #1 (Wait till it's started)
17:31:23 [+] Device Reboot #2 (Wait till it's started)
17:33:34 [+] Testing exploit: root5 (please wait..)
17:33:35 [+] Unlock your device screen, it should bring up restore mode.
17:33:49 [+] Press RESTORE button on device NOW! then wait...
17:34:21 [+] Device Reboot #1 (Wait till it's started)
17:36:40 [+] Executing root5 exploit Failed. (Root Error: 0)
17:36:40 Auto Root Failed on this device.
Click to expand...
Click to collapse
Thanks for the effort. Now as soon as I have the ability I will try the root on the 7". But thanks a lot for the effort. By the way check out Android Commander, I have been smacking a lot of fuss about it on XDA, because I see a lot of potential in it, I'll try my best to find a hack that will enable one to write things on to the HDX system files, which it is designed to see. I gave it a try before, seemed to work just fine. Now if the update file could be deleted and the 13.3.1 image could be forced on to the HDX we could root! However one can already copy files from the HDX, so my plan is to install the HDX mojito os on sub using unetbootin and boot up the computer from it, or my netbook which closely resembles it, and then try and find a way to modify things without actually bricking the HDX, so if you can, please give it a shot. But if I'm wrong, please do correct me! Thanks again.
Cevyn said:
It might be kind of extreme, but what if we filled the Kindle with MP3s or something to keep the free space below 800mb? The update BIN shouldn't be able to download because of insufficient space.
Click to expand...
Click to collapse
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, might sound stupid but I have a hunch that is what is checked during manual update (in case you didn't know you just drag and drop the update into internal storage, and then do it the usual way and it should appear there). Now all that has to be done is the .zip converted into a .bin, and ill give it a try as soon as it's done. Let's hope it works!
ferrouskid said:
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, might sound stupid but I have a hunch that is what is checked during manual update (in case you didn't know you just drag and drop the update into internal storage, and then do it the usual way and it should appear there). Now all that has to be done is the .zip converted into a .bin, and ill give it a try as soon as it's done. Let's hope it works!
Click to expand...
Click to collapse
I believe the BIN files are just renamed ZIP files. 7-Zip opens them just fine.
ferrouskid said:
On the topic of BIN files, I got my brother to edit the build prop on the old update 13.3.1, the rootable one. I asked him to change the build number in it, ...
Click to expand...
Click to collapse
What build number did you have your brother change it to?
How are you getting around signing the BIN file? This would be the major stumbling block to any mods to it...
Cevyn said:
I believe the BIN files are just renamed ZIP files. 7-Zip opens them just fine.
Click to expand...
Click to collapse
Yeah, thanks. I tried it and the kindle recognised is as an update ) but it said the file wasn't valid, so I should convert it to a .bin. Maybe then it'll work? After this I'll shut my WiFi off so it doesn't connect to the internet to verify the update. Ill be back at dad with results from PC.
Let's hope it works! A little bit to go!!!
tl3 said:
What build number did you have your brother change it to?
How are you getting around signing the BIN file? This would be the major stumbling block to any mods to it...
Click to expand...
Click to collapse
I got him to change it to 13.3.3.3 and let the user bit stay the same. Now I tried it in bin format, and here are the results so far (check image).
So far it doesn't recognise it as 13.3.3.3, maybe because it's a zip? I realise that bins and zips in effect are the same thing, but maybe converting will,help?
Will be back at xda after this.
Here is the url to dropbox
https://www.dropbox.com/s/v5eo7zu155773b0/Screenshot_2014-04-11-21-33-23_kindlephoto-9182708.png
Oh yeah, I need a little help with the signing. I have found a certificate installer app on the kindle, but I'm not sure it will do the job. Maybe if I installed it in an android environment and managed to certify it from my netbook using x-86 android website downloads...
But it might not work. Please correct me, I'm quite new to this all. And also isn't there like signtool.exe for windows? Ill look into that, and I'd be grateful if you could help.
Thanks!
ferrouskid said:
I got him to change it to 13.3.3.3 and let the user bit stay the same. Now I tried it in bin format, and here are the results so far (check image).
So far it doesn't recognise it as 13.3.3.3, maybe because it's a zip? I realise that bins and zips in effect are the same thing, but maybe converting will,help?
Will be back at xda after this.
Here is the url to dropped
https://www.dropbox.com/s/v5eo7zu155773b0/Screenshot_2014-04-11-21-33-23_kindlephoto-9182708.png
Click to expand...
Click to collapse
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
tl3 said:
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
Click to expand...
Click to collapse
Ill keep on at it, and see where it goes. I have read up some things about signing bin files, I think Android Commander has the option to do so and so does Signtool, but I don't know what to sign it with yet. Yeah, you were right, it did terminate the update unfortunately, but Ill see what I can do.
Here is a snapshot
https://www.dropbox.com/s/pp6txvavncuwvti/Screenshot_2014-04-12-09-11-33.png
tl3 said:
I believe that the Kindle only recognized that there is an update file with a higher version number, but if it is not signed properly, the modified BIN file will not pass authentication and the update process will terminate. This is the stumbling block I was referring to and asking you about... it's not something trivial that can be easily defeated or bypassed.
Click to expand...
Click to collapse
Yes, this truly is a stumbling block. I need someone's help to find a certificate that Amazon use for their updates, there are numerous certificate apps installed on the kindle, but I'm not 100% sure they serve this specific purpose. There are signing tools available for free on the internet, such as signtool and stuff like that. That's all good, but I have no idea in which way Amazon sign their updates. I have the original 13.3.1 .bin officially signed by Amazon, I will have a link to my dropbox. I wonder weather there is a way to find in which way it was signed and do the same for this "update"?
Ill be looking into that.
https://dl.dropboxusercontent.com/u/67795059/update-kindle-13.3.1.0_user_310079820.bin
Keeping root across updates may be possible with simple re-signing
Amazon uses SignApk to sign their updates.
(To confirm, just unzip the .bin file and look at the first few lines of CERT.SF (or MANIFEST.MF) in the META-INF directory.)
*IF* you have root today (unfortunately, I got updated before I had a chance to try this),
you should be able to take an official Amazon update, unpack it, strip the existing signature,
add whatever you like (supersu and your own otacerts comes to mind), and re-sign
the update with your own key following the procedure described in this blog post:
FIX THE URL ::: www .. londatiga .. net // it // how-to-sign-apk-zip-files
(including instructions on how to generate your own signing key and certificate).
What you need root access for is to swap the current /system/etc/security/otacerts.zip on your device to your own zipped certificate.
Once that piece is changed, you should be able to use Amazon's manual update procedure to apply your modified update.
FIX THE URL ::: www .. amazon .. com // gp // help // customer // display.html?nodeId=201390600
You may need to change the updater-script to set the right owner and permissions for /system/xbin/su.
And, don't forget to change /system/etc/security/otacerts.zip to your own stuff in the actual update as well!
Again, this _MAY_ (or may not) work. I'd appreciate feedback if you tried this (or: are willing to try, but need help).
Related
hy
how root the lg optimus pro ?
need a guide thanks
1 º Download this suite of applications that I use (I added the zip original drivers from LG, which, with no specific model for this, worked like a charm):
www.megaupload.com/?d=U3L199Z3
2 Reset the phone manufactures (who have data to backup, use the File maneger Astro, for example), to obtain a clean file system Settings \ Privacy \ Reset factory data;
3 Extract the zip to a folder on your desktop and install the USB drivers, which are in the zip, the folder "USB driver";
4 Connect the phone to pc cable and expect drivers to be installed;
5 º Go to the pc start \ programs \ accessories \ command line;
6 After you open the command line type:
cd \
cd Users
cd (user name in question)
cd Desktop
cd (name of which are powered uncompressed zip files)
cd ADB
and the result is something like: C: \ Users \ (user name) \ Desktop \ Root Maximo LG Pro \ ADB
then enter the following commands:
adb devices (pressenter)
adb shell (press enter, and then the letter of the command line will pass to $)
echo 1> / data / local / lge_adb.conf (press enter)
7 After these commands inserted, turn off and then turn on the phone (very important this step), always with the phone connected by USB;
8 After restarting the phone, go to the folder where the files are downloaded and run the SuperOneClick.exe;
9 Select the method GingerBreak and click "ROOT"
10 When the process finishes (VERY IMPORTANT) make sure you turn off and turn it on again and update the application through the superuser Market.
That's it. Phone with root access.
Credits go to: Bruno Pinto @ AndroidPT
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
That guide is so complicated for n00b like me who has never before used Android. The stock rom is awfull anyway, any hope for costum roms on this one?
Hi!!
After running the adb command line and restart the mobile, i've started the super one click, it started rooting and in the end in step 7 he says "Remounting /system with read-write access .... FAILED", what went wrong?
I have the latest drivers for this smart and the latest super one click v.2.1.1
My LG has the 2.3.4 version of android and it's from TMN
Regards
is it possible to unlock it? (for free preferably)
hugoafsilva said:
Hi,
I've tried as you say, and i jammed on the driver installation. Why? On the pack you've posted, there's only a shortcut to the driver file: LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2 - Atalho
and when clicking it its giving me a link to something that doesn't exist:
C:\Users\"username"\Desktop\LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.exe
Even so, i'd already had installed the LG software suite and so i've got the driver so i moved to the next steps.
when going to perform the adb shell command (error: device not found), i tried with mass storage mode on and off and msg is always the same.
can you please help me?
thanks for any answer
Click to expand...
Click to collapse
the drivers are here: http://www.mediafire.com/?85wvjkp5ytb816y
This is NOT complicated method and it works great. I have also tried this on Optimus Net and works fine
Help..! Help..!
I have an LG-C660 Android Gingerbread 2.3.4
1 - Does anyone has an Android version fot this device..?
2 - After Root the device, it boots but dont´s shows the Desktop. It´s stucks on Carrier Screen
3 - Please Help me..!
I tried as instructions but the adb driver can't be successfully installed. I've tried installing drivers many times but it doesn't work.
Done! I removed the SD card and it worked finally!
i have a lg C660 from TMN with v2.3.4 i've tried and tried and cant make it work. anyone got it to work?
Edit :: with superoneclick v2.1.1 i get this
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,10s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,14s
Waiting for device...
OK 0,08s
2.3.4
Getting manufacturer...
LGE
OK 0,02s
Getting model...
LG-C660
OK 0,03s
Getting version...
V10c-Aug-25-2011.2ED2FC6537
OK 0,03s
Checking if rooted...
False
OK 0,06s
Installing BusyBox (temporary)... - Step #1
2039 KB/s (1062992 bytes in 0.509s)
OK 0,59s
Installing BusyBox (temporary)... - Step #2
OK 0,03s
Rooting device... - Step #1
OK 0,02s
Rooting device... - Step #2
OK 0,03s
Rooting device... - Step #3
782 KB/s (16830 bytes in 0.021s)
OK 0,10s
Rooting device... - Step #4
OK 0,04s
Rooting device... - Step #5
OK 0,02s
Rooting device... - Step #6
[**] 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: 0x00014354
[+] Using device /devices/platform/msm_sdcc.1/mmc_host
[*] vold: 0000 GOT start: 0x00014354 GOT end: 0x00014394
OK 80,24s
Rooting device... - Step #7
OK 8,08s
Remounting /system with read-write access...
mount: Operation not permitted
FAILED ::
When you get the #6 step you have to disable and enable debug usb on the device..in this way it should work
Sent from my LG-C660 using Tapatalk
Sir i have tried the above procedure. But after "loading gingerbreak" nothing happens. i have waited for half hour.Please tell me what went wrong?
some body know how to get in recovery mode ´cuz i can root my c660 i have gingerbread 2.3.4
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Step 5 and Step 7 problem
EDIT:
Finally Done. I used SuperOneClick v2.2 and removed the SD card (only in settings) and on step five just disable and enable usb debugging. I feel like alchymist.
And now i am looking how i can custom default rom.
simmer14 said:
i have rooted my gf's phone and made a custom ROM for her i made it for her only !
Click to expand...
Click to collapse
sir kindly make one for us too.. we are sick of Stock ROM...
unabl to root every =time it gets strucked on step 7... somebody help me
Installed at last after 3 days hardwork :/ :/
I was really happy havin my ROOTED S.ony Tablet S, but unfortunately am not able to root again after a update.
Details:
S.ONY TABLET S 16GB (3G)
Country: India
Android Version: 3.2.1 (Release2)
Baseband Version: R3B01
Kernel Version: 2.6.36.3
Hop I have provided needed info.
Thanks for all the updates from "XDA"
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
kryddan said:
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
Click to expand...
Click to collapse
Thanks for replying bro:
Mine says :: [email protected] #1
And so i am unable to root right ???
So how can I root again ???
coolfire000 said:
Thanks for replying bro:
Mine says :: [email protected] #1
And so i am unable to root right ???
So how can I root again ???
Click to expand...
Click to collapse
That is correct. As of now you are not able to root your tablet, since you have build10. I guess all you can do now is wait and see if someone root the later builds or what for ICS and hope for root.
Not sure if you could try and flash an older rom with recovery, and therein get root?
kryddan said:
That is correct. As of now you are not able to root your tablet, since you have build10. I guess all you can do now is wait and see if someone root the later builds or what for ICS and hope for root.
Not sure if you could try and flash an older rom with recovery, and therein get root?
Click to expand...
Click to collapse
Ok thanks for the replies bro, will wait the things as am a newbie to all this things.
Hope to get ICS and rooted both.
Please . . . . .
Any idea about ICS ?
kryddan said:
Under "Kernel Version" mine says
2.6.36.3
[email protected] #1
What does it say on yours ?
If you have [email protected] #1 or above you are unable to root at this time.
Click to expand...
Click to collapse
I Have [email protected] #1 and I rooted my device following the instructions of the developers.
This will work on all build?
I have build 10. Thank you so much.
Can you provide me some link
rfreeman said:
I Have [email protected] #1 and I rooted my device following the instructions of the developers.
Click to expand...
Click to collapse
Hi can you please prove some link as am a bit newbie I hope you'll help
When I tried using Root 1.1, I got the following output
[*]
[*] Sony Tablet S root script v1.1 (Windows version)
[*] by Dan Rosenberg (@djrbliss).
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*] You've got to have proper MPT driver to root your tab!
[*] (MPT driver - wpdmtp.inf included).
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*] +small mods/optimizations by Konrad Plaszczykowski (@condi)+
[*]
[*] FULLY AUTOMATIC - ROOT SHOULD TAKE ABOUT ~ 3min 10s.
[*] Press enter to root your tablet...
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] MTP driver has been disabled.
[*] Device found.
[*] Pushing log flooder to device...
failed to copy 'flood' to '/log/flood': Permission denied
Unable to chmod /log/flood: No such file or directory
[*] Preparing to append to packages.list...
link failed File exists
[*] Rebooting device...
[*] Waiting for tablet to reboot...... (~20s)
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
[*] Attempting to move system package library directory...
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
[*] Rebooting device...
error: device not found
[*] Waiting for tablet to reboot...... (~40s)
[*] Attempting to insert fake local.prop entry...
link failed File exists
/log/flood: not found
[*] Rebooting device...
[*] Waiting for tablet to reboot...... (~40s)
[*] Attemping persistence...
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
failed on '/data/data/com.google.android.location/lib.bak' - No such file or dir
ectory
[*] Rebooting...... (~35s)
[*] MTP driver has been enabled back.
[*] Exploit complete!
[*] Press any key to exit.
Click to expand...
Click to collapse
coolfire000 said:
Hi can you please prove some link as am a bit newbie I hope you'll help
Click to expand...
Click to collapse
Use S.onlyTablet.S v1.1 it has builtin check if your device is rootable.
condi said:
Use S.onlyTablet.S v1.1 it has builtin check if your device is rootable.
Click to expand...
Click to collapse
Thanks for reply bro, but getting the following error:
[*] Sony Tablet S root script v1.1 (Windows version)
[*] by Dan Rosenberg (@djrbliss).
[*]
[*] Before continuing, ensure USB debugging is enabled, that ADB
[*] is working properly, and that your tablet is connected via USB.
[*] You've got to have proper MPT driver to root your tab!
[*] (MPT driver - wpdmtp.inf included).
[*]
[*] WARNING: This exploit may result in wiping your /data partition,
[*] causing you to lose any applications and data on your tablet.
[*] There should be no risk of permanent damage to your device, but
[*] by running this script you accept all responsibility.
[*]
[*] +small mods/optimizations by Konrad Plaszczykowski (@condi)+
[*]
[*] FULLY AUTOMATIC - ROOT SHOULD TAKE ABOUT ~ 3min 10s.
[*] Press enter to root your tablet...
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] It looks that your device is [for now] not rootable...
[*] In your kernel version exploit vulnerability has been locked down...
[*] You need to wait for DEVs to find another way...
[*] Press any key to exit.
Click to expand...
Click to collapse
Solution to all
Check if u hav enabled usb debugging ... n unknown sources ..in the setting... u cn use tis file ... whch ucn find in the Android development area too..... nt responsible for any damage to ure device ...
coolfire000 said:
Thanks for reply bro, but getting the following error:
[*] It looks that your device is [for now] not rootable...[*] In your kernel version exploit vulnerability has been locked down...[*] You need to wait for DEVs to find another way...
[*] Press any key to exit.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, exactly as it says. No solution for now. You need to wait
T0Tal_N00b said:
Check if u hav enabled usb debugging ... n unknown sources ..in the setting... u cn use tis file ... whch ucn find in the Android development area too..... nt responsible for any damage to ure device ...
Click to expand...
Click to collapse
No need to reupload tool, its available in official S.onyTablet.S thread.
br!
condi
Can build 9 be rooted?
Sent from my E16i using xda premium
mine says
Android Version: 3.2.1 (Release2)
2.6.36.3
[email protected] #1
it just hangs after daemon successful luanch... im using xp on vmware btw.
D00QLE said:
mine says
Android Version: 3.2.1 (Release2)
2.6.36.3
[email protected] #1
it just hangs after daemon successful luanch... im using xp on vmware btw.
Click to expand...
Click to collapse
does the XP on vmware detects ur tablet s?(like: adb devices (does this show u ur tablet? )) i was using Oracle VirtualMachine and i had to passthrough my USB devices to my guest OS. Perhaps u might want to check that(usb passthrough on vmware) out.
Maybe USB 1.1 only ?
I had to disable Oracle VirtualBox USB 2.0 support extension to get the tablet recognized by ADB in a Windows XP VM running under a Linux (Debian Squeeze) host...
Keep checking the build #
I purchased my Tablet S (refurbished) last week. It came with Build10. The first thing I did after turning it on was check to Build#.
However, after restarting a few times it reverted to Build5. I am not sure why that happened, but I was able to root using the All In One. I think someone else here had this happen also.
I *may* have run a Sony update on the previous restart. (It was late and I can't remember)
I guess you got it with FW 3.2 and Kernel build#10
Then you did a update to 3.2.1R2 with kernel build#5.
Could you remember?
zerod78 said:
does the XP on vmware detects ur tablet s?(like: adb devices (does this show u ur tablet? )) i was using Oracle VirtualMachine and i had to passthrough my USB devices to my guest OS. Perhaps u might want to check that(usb passthrough on vmware) out.
Click to expand...
Click to collapse
problem solved, it was the
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
Click to expand...
Click to collapse
i though i had to add echo but no
Does anybody knows if Condi tool S.onyTablet.S v4.1 [ALLinONE] works on Tablet P?
Is there something special needs to be done to get it to work?
I have Sony Tablet P. US(I assume )
Android 3.2.1
Kernel 2.6.36.3 [email protected] #1
Build number THMAAS0015400
When I run Root command I get error
[*] Attempting to move system package library directory...
[+] System package com.android.providers.media has uid 10035
[+] Flooding log...
run-as: Package 'com.pwn.me' is unknown
Any suggestions?
May be another method?
Thanks!
shlasasha said:
Does anybody knows if Condi tool S.onyTablet.S v4.1 [ALLinONE] works on Tablet P?
Is there something special needs to be done to get it to work?
I have Sony Tablet P. US(I assume )
Android 3.2.1
Kernel 2.6.36.3 [email protected] #1
Build number THMAAS0015400
When I run Root command I get error
[*] Attempting to move system package library directory...
[+] System package com.android.providers.media has uid 10035
[+] Flooding log...
run-as: Package 'com.pwn.me' is unknown
Any suggestions?
May be another method?
Thanks!
Click to expand...
Click to collapse
Tablet P are weird like that. Can you update to ICS? If you can you can root. Others with tab P have been able to root using adb restore method. Binary's semi-auto script should work.
Got it !!!
There is another setting under "Applications->Development" "Allow mock locations"
It is not mentioned in any guides.
After I set that one ALLinONE worked.
Thanks everyone!!!
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R180 Build2,846
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
SVN Revision: 169
CASUAL Build Number: 2,792
Problems known at release: none
Problems Identifed:
Kill Switch/update downloaded message contains no spaces.
SVN Revision 180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
just4sc said:
How long does it take to update? I have the "Script is out of date" message. Says updating...then the Youshouldseethismessagebecauseitsimportant message".....but so far no reboot...it's been about four minutes.
Here's the log -
Code:
Created Folder:C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
This is a test of CASUAL's new update system. Please leave feedback.
Deploying ADB
Searching for scripts
null
Picking Jar File:/D:/Download/CASUAL-Revision169b.jar
Found Windows Computer
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\Elevate.exe
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BDadb_usb.ini
File verified.
###executing: C:\Users\User\AppData\Local\Temp\UserTEMPCASUAL232BF7BD\adb.exe###
State Change Detected, The new state is: 1
State Connected
device
Device List:List of devices attached 014E5ABE06004016 device
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as Kill-Switched is running
Controls Enabled status: false
Script Kill-Switched returned #0Kill-Switched
Selected resourceKill-Switched
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Kill-Switched returned #0Kill-Switched
Script is out of date. See http://forum.xda-developers.com/search.php?do=finduser&u= for more information. Updating.
Youshouldseethismessagebecauseitsimportant--AdamOutler
Okay...re-read your instructions again...Chose "Kill Switch" and the above happens.
Chose "Update required" and it give the "Cool" message.
Chose "Update not required" and it rebooted.
I think those were the expected results, yes? FYI - I have a Mot. Razr Maxx....
Click to expand...
Click to collapse
I'm pushing out the kill switch now. http://code.google.com/p/android-casual/source/list
AdamOutler said:
Hey guys,
I need help testing CASUAL. I've been working on CASUAL for almost a year now. Currently I'm working on bringing real-time updates and a kill-switch in the event the GNote2 unlock starts bricking devices. I need tesing on the ability to push a new revision, and the "kill-switch".
Intent
I need help testing new features on your computer because they work on mine. The tests will do nothing except reboot your device. The update system is pretty critical and potentially show-stopping. It will be in every CASUAL, including the GNote2 Unlock (for safety reasons) as soon as this test is complete.
Scripts
Here is what I need tested:
1. Kill Switch -- If you are connected to the internet, it will shutdown CASUAL, display a message, then open a browser and take you somewhere where you can get more information.
2. Update Required -- Will download the latest versions of the "Update Required" script and files ONLY one time per run. These files come from the CASUAL Subversion repository located here, then your device will reboot.
3. Update Not Required -- Will reboot your device. This is the "control" subject.
Download CASUAL R169 Build2,792
Obtaining a log
If you see a problem, Click About>Show Log>Copy to Clipboard then paste it into a code box here on XDA. Or if you wish to copy the terminal output from "java -jar path_to/casual.jar" that's fine too.
Privacy
No information is sent from your computer. CASUAL determines if it needs an update by looking at the online version and pulling required files off the internet.
Click to expand...
Click to collapse
This is revolutionizing android and fast. i love you.
Everything appears to be working great Adam.
Thanks.
I've just relesed the following build. All previous scripts should be killswitched. Please test this and verify that there are no errors.
SVN R180
CASUAL Build Number:2846
Corrected killswitch/update messages, removed unused imports, cleaned up and relicensed code under GPL instead of MIT
Problems known at release: none
Problems Identifed: none
Sorry, I uploaded the wrong file. Correct file is up now. There should be no problems now.
Please let me know if this works and what OS you are using.
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
B-Mod said:
Windows 7 here, everything looks good, but it did not reboot after I got the "cool" message when doing the update required choice.
Click to expand...
Click to collapse
Could you please grab the log from about>show log>copy to clipboard.. Then paste it here in
Code:
tags?
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
Code:
Created Folder:C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\
Control Change requested but Statics.MasterLock is set.
OMFGWOOT
Testing CASUAL's ability to update
Deploying ADB
Searching for scripts
null
Found Windows Computer
Picking Jar File:/C:/Users/HTPC/Desktop/CASUAL-Revision180b(1).jar
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\Elevate.exe
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe
Found: Kill-Switched
Found: Update Not Required
Found: Update Required
Updating Scripts for UI
From Resource: true
--Kill-Switched--
Exiting comboBoxUpdate()
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\AdbWinUsbApi.dll
File verified.
Attempting to write C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb_usb.ini
File verified.
###executing: C:\Users\HTPC\AppData\Local\Temp\HTPCTEMPCASUAL59652B83\adb.exe###
State Change Detected, The new state is: 1
device
State Connected
Device List:List of devices attached 42f73b16cf4d9f95 device
Controls Enabled status: true
From Resource: true
--Update Required--
Exiting comboBoxUpdate()
StartButtonActionPerformed() Script Activated
Script known as Update Required is running
Controls Enabled status: false
Script Update Required returned #2Update Required
Selected resourceUpdate Required
Lines in Script 4
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script Update Required returned #2Update Required
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2105263 for more information. Updating.
CASUAL was updated to the latest greatest version of this script. Cool huh? --AdamOutler
Adam, did you figure out why the phone did not reboot?
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
Sorry, but I won't be able to test it till Thursday night, as I am working out of town and not near my PC.
AdamOutler said:
Try this one. This includes all my latest changes..
Added Fastboot support
Added Killswitch support
Added Automatic Downloads
Added MD5 integrity checks
--Also-- Added "double-click-enable" on status button. If you really want to use a fastboot-only script but your device isn't capable of adb reboot bootloader, double-click the "device status" and it will enable things as though a device were connected.
Download Here: http://d-h.st/JlJ
Click to expand...
Click to collapse
All seems to run well here.
--Test Script--
Testing Testing Revision 1
Script is out of date. See http://xda-developers.com for more information. Updating.
OMFG TESTING meta information
Downloading Updates
Test Script.scr...4kb Test Script.zip...1880kb Test Script.txt...4kb ... Update Sucessful! MD5s verified!
rebooting with ADB
rebooting with Fastboot
Running Windows 7.
I will test this tonight when I get home.
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
albertaz said:
Hello,
to cut a long story short I have my device with this configuration:
Smartphone: Motorola RAZR XT910
ROM: 982.124.14.XT910.Retail.en.EU
Kernel: 3.0.8-g7198280 [email protected] #1 SMP PREEMPT
The problems that I am experiencing:
1) Neither Mac, Win, nor Linux detect my RAZR when I connect it to the computer. Weird thing is that RSD (on Win) and Terminal (Linux) seem to detect the phone.
I tried switching ON/OFF USB debugging, Mass Storage, MTP but no luck at all.
2) I cannot root it! When I try to apply the Dan Rosenberg method all I get is:
[email protected]:/tmp/share$ sudo ./run.sh
[+] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[+] Device found.
[+] Pushing exploit...
3791 KB/s (366952 bytes in 0.094s)
4466 KB/s (1867568 bytes in 0.408s)
1559 KB/s (64498 bytes in 0.040s)
4031 KB/s (1578585 bytes in 0.382s)
pkg: /data/local/tmp/Superuser.apk
Success
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
/system/bin/sh: /storage/rfs0/pwn: not found
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] The device will vibrate when the exploit is complete.
[+] Press enter to continue once the device has vibrated.
Then it does not vibrate and no root is applied.
No luck either with this http://forum.xda-developers.com/showthread.php?t=2257137
3) I cannot boot into recovery! When I switch on pressing Power + VolUp + VolDown I get into the screen with robot & red ! triangle but even pressing buttons from there does not take me anywere! I don't know what to do.
4) Last but not least I would like to unlock the bootloader and change kernel. I got to know that this 982.124.14.XT910.Retail.en.EU appears to lock you yet I would like to ask if someone found some turnaround.
Can you help me?
Thanks a lot for the support!
Alberto
Click to expand...
Click to collapse
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Thanks for the reply.
Yes, I have the latest drivers installed both on Win and on Mac, as for Linux I guess they are not needed
Yet nothing happens... On Win I keep hearing that notifications sound but nothing shows up. On the RAZR screen I read something like "AT command service start", "AT command service stop" when I plus/unplug it to the PC USB. And that's it
As for the recovery: thanks a lot. It worked although I had to try a couple of times as the device sometimes freezes even during that boot stage.
AztekSoul said:
Have you installed the latest drivers? Sounds like that's you issue..
And to boot into recovery turn off your device then press power+volume up+volume down and select recovery,when you get to the android with red triangle press volume up+volume down for about 10 seconds I think then let go and you'll enter to the recovery mode.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
ersink said:
I got the same problem when updated to JB to root the phone. Just try to root again since phone couldnot root first time i tried. Then i run the script again and it was ok...
Click to expand...
Click to collapse
albertaz said:
After several attempts I used a linux computer and did step by step what Dan described in his root procedure.
I found out that there was a last problem which was that the phone was looking for "rfs1" while the "run.sh" on linux was using "rsf0" so I edite the "run.sh" file in the folder /tmp/share (you should find that at line 47):
echo "[+] Rooting phone..."
echo "[+] Your phone may appear to reboot. Please ignore this and continue with the exploit."
$adb shell /storage/rfs0/pwn 1 ---> I modified that into $adb shell /storage/rfs1/pwn
then I saved and re-applied the last part of the ROOT procedure and it worked smoothly.
2) USB connection reappeared!
Click to expand...
Click to collapse
That's useful info. I always try custom roms and smtimes razr got soft bricked so i flash the firmware again then root again. Every rooting process i stuck first then reroot the phone. This is the situation why at first try phone cannot rooted.