[ROOT][ICS] Root Razr ICS 4.0.3 and 4.0.4 [updated]
This is first post for Razr Root ICS 4.0.4 on XDA Developers
Tested on my Razr xt910 no errors...
This method run in CDMA and GSM Razr...
This method run in all versions ICS 4.0.4 for Razr
This method run in all versions ICS BRAZIL and ICS Leaks
This method run in all versions ICS CHINA / 4.0.3 and 4.0.4
This method run and confirmed on ICS Leaks english.en.Eu 4.0.4
Credit to Rick#2 for this great post and Exploit
Credit to miloj for this new technique on ASUS Transformer
Only Run the script and wait end process
Remenber this method has been fully tested on my Razr and i succeeded
[REQUIREMENTS]
Check if your USB computer connection is "Mass Storage".
It shouldn't be. Change it to "media device" MTP mode.
Check if your configuration of android is set to "debug mode".
[AUTOMATIC]
1. Download exploits or scripts
2. Unpack files on any folder
3. Install motorola drivers
4. Connect your Razr with USB cable
5. Check if your configuration of android is set to "debug mode".
6. Check your Usb connection and change to "media device"
7. Run the exploit in the bottom of the page
[SCRIPT] Fully tested only run in prompt and wait process
Mod Edit:Removed links
[MANUAL]
1. Download the following files: su and debugfs
2. Save the two files on /sdcard
(ie: mount your sdcard in windows and copy them over, or "adb push" them to /sdcard).
3. In a linux terminal/Windows command prompt:
commands at the prompt is started after the symbol #
4. Run all commands and if reboot not run open new prompt and enter adb "reboot"
5. Run sequence commands and reboot with "adb reboot" or with shutdown
6. Install superuser.apk from market or google play
7. Install OTA ROOT KEEPER and backup your ROOT
8. Install ROOT CHECKER BASIC and test your ROOT access
9. if fails one first test, reboot and restart ...
10. Run all commands and no reboot... yes run all comands again...
11. Reboot only with finish all commands...
12. if fails with second test run script on the end of this page
[COMMANDS]
Code:
adb shell
[email protected]_maserati:/ # cd /sdcard
[email protected]_maserati:/ # cp su /data/local/12m/
[email protected]_maserati:/ # cp debugfs /data/local/12m/
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # chmod 755 su
[email protected]_maserati:/ # chmod 755 debugfs
[email protected]_maserati:/ # mv batch batch.bak
[email protected]_maserati:/ # ln -s /dev/block/mmcblk1p20 batch
[email protected]_maserati:/ # exit
adb reboot
The Razor reboots, after restart enter new commands...=>
Code:
adb wait-for-device shell
Wait android shell:
Code:
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # rm batch
[email protected]_maserati:/ # mv batch.bak batch
[email protected]_maserati:/ # /data/local/12m/debugfs -w /dev/block/mmcblk1p20
(Enter this commands at the "debugfs:" prompt)
debugfs: # cd xbin
debugfs: # write /data/local/12m/su su
debugfs: # set_inode_field su mode 0104755
debugfs: # set_inode_field su uid 0
debugfs: # set_inode_field su gid 0
debugfs: # quit
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # rm su
[email protected]_maserati:/ # rm debugfs
[email protected]_maserati:/ # cd /
[email protected]_maserati:/ # reboot
[email protected]_maserati:/ # exit
adb reboot
if fails one first test, reboot and restart ...
run all commands and no reboot... yes run all comands again...
reboot only with finish all commands...
After install - open market and Download superuser.apk
https://play.google.com/store/apps/...wsMSwyLDEsImNvbS5ub3NodWZvdS5hbmRyb2lkLnN1Il0.
Download the Superuser app from the google play and install.
[THANKS]
If this post help you click Thanks
[SCRIPT] Exploit Script Updated
I rooted my razr with commands only ok... and I succeeded
[EXPLOIT]
ICS.4.0.4.ROOT.zip - [ROOT-ICS] (1.133 KB, 50.898.976 views)
Mod Edit:Removed links
[FILES]
Mod Edit:Removed links
[ABOUT THIS PAGE]
I'm here to help people around the world
is not what you do that makes you extraordinary
but it is the way that we give that says who we are
it can not be measured with thanks or views
Jesus is the Lord
About this Root method - Thank You XDA for this page
http://www.xda-developers.com/androi...razr/#comments
About this Root method - Thank You Droid Life for this page
http://www.droid-life.com/2012/06/1...rooted-before-official-release/#disqus_thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
amazing, thanks for this i will try it out tomorrow morning and post root confirmation on my latam ota 404.
Sent from my XT910 using XDA
drolgnir said:
amazing, thanks for this i will try it out tomorrow morning and post root confirmation on my latam ota 404.
Sent from my XT910 using XDA
Click to expand...
Click to collapse
FrAsErTaG Thank you
Thanks for confirmation drolgnir
i´m happy for you... and for all my friends on XDA
The secret of my success is Jesus
I strongly recommend you to send this file to Mediafire
4shared cannot download anything without its account
shiwuye12 said:
I strongly recommend you to send this file to Mediafire
4shared cannot download anything without its account
Click to expand...
Click to collapse
Ok, thanks for sugestion...
I have not tested this script...
I rooted my razr with commands only ok...
[SCRIPT] Exploit with script by Hacker812c
http://www.4shared.com/rar/0BKsZ-Uw/ROOTICS404_2.html
http://www.mediafire.com/download.php?cbh4kpdeeizjc8j
First correction...
in the line 6 i insert new command [chmod]
[email protected]_maserati:/ # chmod 755 su
the commands failed on mine.(rom is 651.167.26.XT910.Retail.en.EU OTA 672.180.17.XT910.Retail.en.EU )
i tried it for many times.
i got error just on this lines:
Code:
[email protected]_spyder:/data/local/12m $ /data/local/12m/debugfs -w /dev/block/mmcblk
1p20
fs -w /dev/block/mmcblk1p20 <
debugfs 1.42 (29-Nov-2011)
/dev/block/mmcblk1p20: Permission denied while opening filesystem
debugfs: cd xbin
cd xbin
cd: Filesystem not open
debugfs: write /data/local/12m/su su
write /data/local/12m/su su
write: Filesystem not open
debugfs: set_inode_field su mode 0104755
set_inode_field su mode 0104755
set_inode_field: Filesystem not open
debugfs: set_inode_field su uid 0
set_inode_field su uid 0
set_inode_field: Filesystem not open
debugfs: set_inode_field su gid 0
set_inode_field su gid 0
set_inode_field: Filesystem not open
solved:
device needs reboot while process.
even it fail on first time
in manual command i have this message:
cp su /data/local/12m/
cp: su: No such file or directory
1|[email protected]_spyder:/sdcard $
pls help me
thanks
Everything's cool! Everything is working. Thank you very much. (RAZR GSM, Blur_Version.651.167.3370.XT910.Brasil.en.BR)
i just did everything manually without errors and nothing
the only issue i saw was the reboot command was not allowed. i had to do that manually, problem?
markceri2000 said:
in manual command i have this message:
cp su /data/local/12m/
cp: su: No such file or directory
1|[email protected]_spyder:/sdcard $
pls help me
thanks
Click to expand...
Click to collapse
ok, found my mistake: the 2 files are copied into internal memory. I was copying them into the external sd.
I did the manual procedure and everything went well!! Now I again have the root on my razr!
4.0.4 ICS 672.180.17 en eu
Thanks to those who have allowed this!!!!!!!
you are great at helping us "earthlings"
bye
This method/idea is almost the same as how to root the Transformer TF300T. @Rooting the TF300T
Thanks to @miloj who found this technique
works perfectly with manual method on my razr on 4.0.4 ICS 672.180.17!THANKS!
GREAT!!!!
Worked flawlessly on my LATAM GSM RAZR, Blur_Version.651.167.3370.XT910.Brasil.en.BR, only tip, if you do the "rebooot" line and get a "not permitted operation" just shut down the phone and turn it back on, it won't affect nothing.
Thank you a lot OP
This is great! Much better than our root method which needs to wipe and restore the CID partition. It wasn't published because many users would have to boot via BP Tools because they would have tried it without having a p18 backup. Thx!
Gesendet von meinem XT910 mit Tapatalk 2
Rooted!
I've nearly bricked my Razr when trying to fastboot back to 2.3.6 just for rooting my phone (I'm currently on "official" ICS leak 651.167.26.XT910.Retail.en.EU OTA 2.180.17.XT910.Retail.en.EU, it cannot be fastboot back)
Thank you very much!
By the way, the 2 reboot lines should be "adb reboot" right? I wasn't able to reboot directly (permission denied) so I exit and type adb reboot instead.
But ... I need backup root with ota rootkeeper ... Right?
I dont open shell from terminal without root permissions ...
Enviado desde mi XT910 usando Tapatalk 2
build: 6.7.2-180_SPU-19-TA-5 (updated from t-mobile to this one http://forum.xda-developers.com/showthread.php?t=1688241 , lost root
worked flawlessly! thanks
p.s. in manual mode
whirleyes said:
This method/idea is almost the same as how to root the Transformer TF300T. @Rooting the TF300T
Thanks to @miloj who found this technique
Click to expand...
Click to collapse
It's a copy n paste work http://forum.xda-developers.com/showthread.php?t=1707214
P.S. And why didn't you wait releasing it until the official ICS will be released? Now Moto is able to patch it...
Gesendet von meinem XT910 mit Tapatalk 2
dtrail1 said:
P.S. And why didn't you wait releasing it until the official ICS will be released? Now Moto is able to patch it...
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
I think we should save ours in case this happen. meanwhile, lets spread the root @Rick made work.
Related
I'm using the adb.exe command directly from the Android SDK to connect to my Xperia X10's file system. Here are the commands I issued:
D:\android_sdk\tools>adb shell
$ cd data/app-private
cd data/app-private
$ ls
ls
opendir failed, Permission denied
$ su
su
pwd
pwd
ls -l
ls -l
Permission denied
$ /data/app-private
$ opendir failed, Permission denied
$ exit
exit
D:\android_sdk\tools>
Two questions: 1) Why is it commands entered after typing "su" are echoed? 2) How come I can't browse the app-private directory even after entering su?
Thanks.
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
mattiL said:
Have you rooted your X10 ? (think not)
A # prompt indicates superuser privileges, you did not get to be a superuser.
Why you get an echo I don't know.
Click to expand...
Click to collapse
Yes the phone is rooted. I have the AT&T branding, but used the one-click exploid to root the phone, and it works as Titanium Backup when running tells me it gained Superuser priviledges. I don't know what I'm doing wrong. This is from an MS-DOS prompt in Windows.
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
naplesbill said:
When you use SU for the first time, you need to have the phone screen on and unlocked. It will ask for superuser permissions. Then it will work.
Click to expand...
Click to collapse
Ha, thanks, it worked. The key was typing SU just before I unlock the phone, then it asks me on the phone that "Unknown" wants superuser access. Thanks again.
I was finally able to apply the 'Enable Non-Market apps' fix via adb thanks to this little tip
I'm learning- slowly...
How exactly do I run scripts on this phone when connected to a PC?
Code:
C:\android_sdk\tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# cd sdcard
cd sdcard
# ls -l testscript.sh
ls -l testscript.sh
----rwxr-x system sdcard_rw 54 2010-10-06 10:52 testscript.sh
# sh testscript.sh
sh testscript.sh
: not foundsh: ■#!/bin/sh
: not foundsh: /sh
: not found
mkdir <target>
#
Any ideas?
If anyone told me "You should save your files in UNIX format where each text line ends in 0x0A, and not 0x0D 0x0A as in Windows, it will work" ... you'd be right. UNIX doesn't like carriage return & line feed pairs when trying to run a shell script.
Ok I have tried many times to root my Epad with no luck. It is a Epad with 512 ram 4gb internal flash and Zt-180 processor. Thing that I have tried z4 root failed trys but then when pushing root it stops and reboots. Universal root it says that the device is rooted and installs super user app, but i go to root explorer and it will not let me rw mount. And I have tried to use adb to push but I get the error can not connect please help thanks
this is what it says everytime I try
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Im still stuck does anybody have an idea what im doing wrong?
gtpdjw said:
Im still stuck does anybody have an idea what im doing wrong?
Click to expand...
Click to collapse
Try installing busy box thru titanium backup.
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Thanks a lot, i followed your instruction and my zt-180 2 is finally root
Thank you RogerClark so much!
Many thanks, this is the first 'su' topic that made sense, easy to read and worked!
One question, just to confirm, in doing this java code can now run stuff as super user making my system open to attack?
It's only a play development system so not that bothered.
this worked for me too, many thanks
Something to watch out for which may well stall some who try this - if at some point during the process of entering the commands via ADB shell you receive a failure message 'no such file or directory' - just ignore and persist to the end. Took me some time and googling to discover this.
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
I dont seem to be able to get root explorer permissions even after completing these steps successfully :-( Ive tried reflashing with latest flash "10inch_DDR512MB_android+2.2" running above script -> installed root explorer but w/r button wont toggle and stays on r/o. I can install all root apps ok like busybox & others so not sure what you did or full steps you took to get root explorer w/r to work.. i also tried installing z4root 1st then above script and no go, same with androot... managed to get w/r working once before reflashing but noticed it only let me r/w on root and not in subfolders and files in those subfolders so couldnt edit my wifi config.. Any ideas?
EDIT: I reflashed unit again-> followed this manual root guide for V2 zt-180 ( cant show url cause im new here.. that sucks xda!! ) grant root access, tested in terminal that root access ok using su command (usually i would get "file link error: following process above!?) still root explorer fails to detect device is rooted even though i can install all root apps ok..lol.. I wanted to edit my wireless TX to be 20 instead of 100 to save power/improve reception(well known tweak for zt ) so then i mounted system in adb (mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system) loaded Android commander in windows -> pulled RT2870STA.dat to my windows box, mad the edit to 20 and saved -> used root explorer on zt to delete RT2870STA.dat ->pushed edited RT2870STA.dat back into zt RT2870STA folder -> remounted read only in adb (
mount -o ro,remount -t yaffs2 /dev/block/mtdblock1 /system ) -> rebooted zt and tested modified wireless ok.
So I guess i can at least follow this process for any other file edits that require root access in subfolders of root drive(\).. until someone suggests an easier solution..
When you run the console on the ePad and type su what message do you get? If it's rooted you can run the su prog, if not will say you don't have access.
RogerClark, I followed your steps. And my results are kind of mixed.
Please help if you can.
I am running the ZT-180v2 512mb 4GB
I also did the 2/25/11 Flash upgrade
When I run the "Root Check v2.1" by joeykrim from the Android market it now says that I have root access and busybox installed.
However, Root Explorer 2.13.4 says "Root access coould not be obtained su failed with the following message: Make sure you granted root permission when requested by SuperUser"
Titanium Backup seems to have root rights.?
Any input??
I have the same pad and the same problem. I have root access, only root-explorer version 2.13.4 says I don't. I'm seeing it I can get an older version of it and see if it works. The first time I rooted my pad I had an older version of root-explorer that did work.
Will update my post if I get it to work...
update SDK
be sure after installing that you update all installed packages in the SDK Manager. i could not connect until i updated all a few times.
great post. Got root. Thanks a lot.
Now my 10" V1 zt-180 is rooted I can run su from an application and so do root stuff, but what I need to do is elevate my running app to root user. Any ideas?
P.s. I rooted my device a 2nd time after installing 2.2 with no problems.
Thanks.
Is there any way to back the rom before it is rooted?. So if anything goes wrong I can return it to the original state.
SoundGuy_025 said:
Is there any way to back the rom before it is rooted?. So if anything goes wrong I can return it to the original state.
Click to expand...
Click to collapse
Download the 5-3-11 rom, if anything goes wrong, just flash that and start over with the newest rom. 5-3-11 fixes most of the issues.
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
ok I get - no such file or directory after "busybox cp /udisk......." finished the process and tried to start over. then after mv /system/bin/su ......" I get "No such file or directory.
my luck of course cause everyone else it works any way. what should I do? from here?
usb stick
RogerClark said:
Hi I have the same ZT-180 , 512k - 4Gb... Running Android 2.2
I have been able to root it, but had to use the Android SDK - ADB, and I needed to download the ARM6 version of busybox and a version of SU I found on this forum.
I've attached a zip of the files I used.
Unzip the zip files onto a USB memory stick.
Put the memory stick into the ZT-180
Make sure your ZT-180 is connected via Wifi or the network cable
On the PC, open a command prompt
CD to your android SDK tools or platform-tools folder
use the next 2 ADB commands
ADB connect (the ip address of your ZT-80):5555
ADB shell
then run each of the following commands in the ADB shell (cut and paste them into the ADB shell, and press return)
After the reboot, the ZT-180 should be rooted.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /system/xbin/su /system/xbin/su_original
mv /system/bin/su /system/bin/su_original
busybox cp /udisk/su /system/xbin/su
busybox cp /udisk/su /system/bin/su
chmod 6755 /system/xbin/su
chmod 6755 /system/bin/su
reboot
Click to expand...
Click to collapse
Hi. What should happen when I put in the USB stick? Did exactly what you wrote but still not rooted.also get no file or directory.
All the informations displayed here are from different users on this thread.
I am not responsible for any damage your phone might suffer.
I am not responsibile for bricked phone, annoying people asking for video tutorials (If you need so, Root IS NOT FOR YOU), death of Steve job, bad weather, etc.
How to Manually Root the Alcatel OT-990 (complicated way.. Linux/MacOSX/Windows)
http://forum.xda-developers.com/showpost.php?p=17307501&postcount=15
How to Root the Alcatel OT-990 (Windows only)
http://forum.xda-developers.com/showpost.php?p=18529393&postcount=55
How to Manually Install custom recovery (ClockwordMod)
http://forum.xda-developers.com/showpost.php?p=18440726&postcount=48
Stock ROMs for Alcatel one touch 990
http://blog.podtwo.com/android/rom/Alcatel ot990 Stock ROMs.html
Drivers for Windows
http://forum.xda-developers.com/showpost.php?p=17990459&postcount=28
How to Manually UN-Root the Alcatel OT-990
http://forum.xda-developers.com/showpost.php?p=18438681&postcount=47
My girlfriend saw this phone and was in love with the stylish red color, therefore I got it as a present for her. I myself am using Xperia Arc and Desire Z
Yeah I'm interested in having some rom development on this unit as well, preferrably CM7/MIUI, if not, at least root access
Bumping this up, I am a new convert to Alcatel androids with this model and I eagerly await serious development on this model - I think its worth it.
I think there's a showstopper here - those root procedures require at least usb debugging to be active. On this phone even though I tick the option on, there is NO notification when plugged in to toggle usb debugging.
Exactly like some chinese devices and Archos tablets. There is a workaround for that!
Here's where I am now:
* z4root, universal androot all fail - z4root puts the phone into full 100% cpu load, needs a reboot to normalize, androot just fails.
* superoneclikc doesnt works since ...
* usb debugging doesnt really work - I have the toogle turned on under development but no notification is ever shown;
* setup an adb sdk install in a pc, used the OT-980 drivers instead since there is none yet at alcatel website and it was compatible with the OT-990;
* "adb devices" show this:
List of devices attached
1234567890ABCDEF device
which means ... i dunno, fake or spoofed ID since the adb on the phone is disable/ crippled?
* "adb reboot" shut downs the phone, other ad commands show a:
C:\Documents and Settings\Administrator>adb shell ls -l
error: protocol fault (status 64 72 77 78?!)
the status numbers change depending on the command issued.
The above looks like other errors I see on the web that refer to an incorrect adb driver. I dunno.
So, hopefully someon can followup on this. I'm guessing the capability to flash the firmware with adb properly working is a must before moving on to rooting and other stuff.
Hello all,
Some anonymous helper just pointed me the drivers that may help a little bit, I hope.
This anonymous helper also want me to say again that the warranty is gone when rooting the device.
Those are the same drivers that I used - all from the alcatel website for the ot-980.
We need something like this:
http://forum.xda-developers.com/showpost.php?p=16364149&postcount=195
for the OT-990 before we can hope to root.
Weeee....
Achieved manual root on the ot-990, refer here for a how-to:
http://blog.mx17.net/2011/08/howto-root-your-xperia-x10-mini-pro.html
Adjust as needed. I think its noteworthy I did this under ubuntu - although windows should work also.
Now to see what to do now.
Hats off to u ..kenshinta
i have been looking for your new post since from i plan to purchase alcatel ot 990.
finally u have done it.
could you make a tutorial for , how to root ot 990 , because it would help beginners
like me .
thanks in advance ...
sudh.
I think I fail in the beginning:
Check you can write in this specific directory:
$ cd /sqlite_stmt_journals
$ touch testfile
Click to expand...
Click to collapse
And the result is:
Code:
$ touch testfile
touch: permission denied
:-(
profete162 said:
I think I fail in the beginning:
And the result is:
Code:
$ touch testfile
touch: permission denied
:-(
Click to expand...
Click to collapse
Try:
busybox touch testfile
under adb shell
sudh said:
i have been looking for your new post since from i plan to purchase alcatel ot 990.
finally u have done it.
could you make a tutorial for , how to root ot 990 , because it would help beginners
like me .
thanks in advance ...
sudh.
Click to expand...
Click to collapse
I will try but I think the link i put is already a good starting point to do so.
Draft2: How to Manually Root the Alcatel OT-990
How to Manually Root the Alcatel OT-990
WARNING: usual caveats apply - I am not responsible for any damage that may highly be possible in following this guide.
This guide is a mixture of many valuable resources on the web that I refered to to root my phone. So kudos to the following for sharing:
http://blog.mx17.net/2011/08/howto-root-your-xperia-x10-mini-pro.html
http://www.androidpolice.com/2011/0...bolt-instructions-by-team-andirc-v1-20110318/
http://forum.xda-developers.com/showthread.php?t=1128223
http://forum.xda-developers.com/showthread.php?t=803682
Pre-requisites:
working adb sdk installation
extracted files from SuperOneClick v.2.1.1
We will start the process with the assumption you are at least able to do a
adb devices
Click to expand...
Click to collapse
and get a response of
List of devices attached
1234567890ABCDEF device
Click to expand...
Click to collapse
That means you have a proper adb sdk environment that sees the OT-990.
Here we go!
1. From the extracted files of Superoneclick, get and collect the following files into a single folder for neatness (i.e. "ot990root"):
psneuter (from Exploits folder)
busybox (from Dependencies folder)
Superuser.apk (from Root folder)
su-v2 (from Root folder)
Click to expand...
Click to collapse
1.1.update
I've now prepared an update Superuser pack you can use instead of the older versions in the above superoneclick package. The zip contains Superuser.apk version 3.0.4 (Superuser_3.0.4.apk) plus an updated su binary. Use them for the rest of the guide.
Here's a download link: DOWNLOAD superuser-v3.04-update-pack
2. Open a Terminal Window/ Command Prompt inside the folder we made previously;
3. adb push all the files into the /sqlite_stmt_journals or /data/local folder on the phone;
adb push psneuter /sqlite_stmt_journals >>>> or /data/local, adjust as needed in the ff steps;
adb push busybox /sqlite_stmt_journals
adb push Superuser.apk /sqlite_stmt_journals
adb push su-v2 /sqlite_stmt_journals
Click to expand...
Click to collapse
3.a. Fix permissions of the executables;
adb shell chmod 777 /sqlite_stmt_journals/psneuter
adb shell chmod 777 /sqlite_stmt_journals/busybox
Click to expand...
Click to collapse
4. Open an adb shell to prepare for temp rooting;
adb shell
$ mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock5 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock6 on /custpack type yaffs2 (rw,relatime)
/dev/block/mtdblock7 on /data type yaffs2 (rw,nosuid,nodev,relatime)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock1 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
Click to expand...
Click to collapse
Take note that /system is already mounted as rw;
4.a begin temp root;
$ /sqlite_stmt_journals/psneuter
Click to expand...
Click to collapse
4.b at this point the original adb shell will be killed, you will need to restart adb shell;
adb shell
#
Click to expand...
Click to collapse
4.c the prompt for the adb shell is now for root, to check
# busybox whoami
root
Click to expand...
Click to collapse
or type id
# id
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
5. now to install the permanent root;
# mkdir /system/xbin
# chmod 755 /system/xbin
# /sqlite_stmt_journals/busybox cp /sqlite_stmt_journals/su-v2 /system/xbin/su
# chmod 06755 /system/xbin/su
# /sqlite_stmt_journals/busybox cp /sqlite_stmt_journals/Superuser.apk /system/app/
# chmod 777 /system/app/Superuser.apk
Click to expand...
Click to collapse
5.1 reboot to verify;
#reboot
Click to expand...
Click to collapse
I suggest before doing the above to install from the market Root Checker by joeykrim as your verifier of root before and after the process - just to get empirical evidence of your success ^__^.
Congrats you should have permanent root. Now go destroy those silly apps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
updated 2011-10-3 : added chmod correction for su (as first suggested by henrigolo)
provided superuser.apk (v3.0.4) + su binary updated package
Sorry, my English is not very good)))
how to publish a file for root? Is there an easy way to get it
Hey there!
Is there any easier way to root this device? Or this manual root is the only method? Somebody tried overclock the cpu? Thanks for the replies!
Hi There,
To Kenshinta, very good job however in step 5 you made a mistake in the procedure, it is:
chmod 6755 /system/xbin/su
you need to do.
It took me 2 days to figure out since I'm no linux veteran. This is apparent in the first link you give (sources of your procedure) though.
With your proc and this modification, rooting the OT-990 is now easy.
also in case of usb driver issues (in my case noway using the OT-980 drivers on XP and WIN7-64), I got it "magically" fixed using the pdanet software that's also a good utility by itself. Install the software and it's driver and voila! adb recognizes the device and so on.
Good work again, this is the only procedure available on the whole inetrnet today for this very good value android terminal.
Could someone make a video tutorial on how to do this as im a noob and don understand anything in this method or even how to begin
Hi , hello
thanks for your great work !
Does with this "root-god mod" i can flash a nand rom ? and does it possible te free unlock it ?
have a good day
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self. REMEMBER I DO THIS FOR FUN, please respect the thread as well as others opinions
OLD UPDATES AT THE END OF THIS POST.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
Also you should look at the http://www.nooktabletdev.orgfor information on the Nook Tablet Development process. - Thanks to dj_segfault
Rooting ScriptsWindows: Root, OTA block, De-bloat, Gapps Thanks to Indirect
Mac/Linux: Rooting script Thanks to t-r-i-c-k
Mac/Linux: Root,OTA Block, Gapps
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox:COMPLETE
permanent root: COMPLETE BY INDIRECT
GApps and Market: COMPLETE BY INDIRECT & Anlog
recovery mode: COMPLETE BY nemith
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS TO NEMITH
bootloader: Locked and Signed Irrelevant
uboot: CRACKED BY BAUWKS
THANKS TO BAUWKS
Loglud said:
bauwks method uses the flashing_boot.img to his advantage, and since it is not checked by security, effectively he has made an insecure uboot. While this is not an unlocked bootloader, it is a way to get around the security, and enable custom recovery and higher level processes to be run.
I have been looking at this line of code for a long time, and as im sure hkvc and bauwks saw it is a large (but 100% necessary) flaw:
distro/u-boot/board/omap4430sdp/mmc.c: 559 : setenv ("bootcmd", "setenv setbootargs setenv bootargs ${sdbootargs}; run setbootargs; mmcinit 0; fatload mmc 0:1 0x81000000 flashing_boot.img; booti 0x81000000");
Without this line of code, it would be impossible for any one but the factory whom could JTAG flash (but since it is secured, most likely they also have to make a flashing_boot.img).
Click to expand...
Click to collapse
12/9/11:
UBUNTU is here, thanks to ADAMOUTLER
http://www.youtube.com/watch?v=PwUg17pVWBs&hd=1
Keep in mind this is only an overlay verson but it is prof that one day we might be able to push roms and kernels over existing ones, then hijack then (next work) and then use them.
Please PM me or post if you know anything else, and or want to add anything.
Usefull threads
Usefull threads:
ROOTING:
Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!] Thanks to indirect
Noot Tablet - Easy root & Market on MAC (1 download, 1 script to run) Thanks to t-r-i-c-k
[Windows/Linux] Unroot and uninstall gApps for the nook tablet [Scripts] Thanks to indirect
MODS to Default Rom:
[Full Mod + Root + OTA block] Snowball-mod: Full Modification Root [1/6/2012] Thanks to cfoesch
[DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! Thanks to [DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! 1 Attachment(s) (Multi-page thread 1 2 3 ... Last Page)
Originally Posted By: diamond_lover
Kernels:Coming Soon
ROMS:Coming Soon
APPS:
[Tutorial][WIP] Installing alternative Keyboards on the NT. Thanks to robertely
[DEV] - HomeCatcher Redirect n Button to any Launcher Thanks to gojimi
Hidden Settings App Updated 12/30/11 Thanks to brianf21
Replacement SystemUI.apk v2: Permanent back and menu buttons, n as Home button Thanks to revcompgeek
DEVELOPMENT:
[Dev]Files of interest in the system Thanks to indirect
[REF] Nook Tablet Source Code Thanks to diamond_lover
BHT Installer (Basic Hacking Tools) Thanks to AdamOutler
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard Thanks to AdamOutler
Guides
Table of Contents
Enableing adb Connection (eab1)
Rooting using zergRush (rug2)
Installing busyboxy (ibb3)
Permanent root (pr4) THANKS TO INDIRECT
Installing GApps (aga5) THANKS TO ANLOG
Full system restore/wipe (fsr6) THANKS TO INDIRECT
Enableing adb Connection (eab1)
Install the andriod SDK that is required for your Operating system.
NOTE: This will requries the SDK, and JDK both of which can be downloaded by clicking the links, downloading and installing it.
Run the andriod SDK Manager and Install "Andriod SDK Platform-tools"
[*]Modify your adb_usb.ini file to read such as the following:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
This will be in your /home/{username}/.andriod/ folder for mac and linux
This will be in your C:/Users/{username}/.andriod folder for Windows.
ADB is now enabled for your device, however it is not ON your device. YOU MUST DO THIS EVERY TIME YOU WISH TO ADB INTO YOUR DEVICE.
[*]To do this you will need to download any app, and attempt to install it.
You can use this app if you need.
[*]Click on the Package Installer, and then a prompt will pop up asking if you want change the settings to allow 3rd party apps.
*DO NOT ENABLE IF YOU WISH TO ACCESS ADB*
I am working on a way to have it enabled by default.
[*]In the settings page you should see *2* USB Debuggin modes.
[*]Press them both and accept the prompt.
[*]PLUG IN YOUR DEVICE.
Note* You should see the Android Development icon on the bottom of the screen.
ADB will now be able to see your device. How ever you will need to restart the server before it sees it.
Rooting using zergRush (rug2)
This is for the poeople whom have access to adb. You will also need this file. Unzip the file.
Type in the following command (while in the folder with the zergRush Binary):
Code:
adb push ./zergRush /data/local
[*]Once thats installed run this:
Code:
adb shell chmod 777 /data/local/tmp
[*]And lastly:
Code:
adb shell /data/local/zergRush
[*]You are now rooted (only for this reboot)
Installing busyboxy (ibb3)
You will need root and the following busybox file.
Type in the following command while in the location where busy box was downloaded to:
Code:
adb push ./busybox /data/local
[*]Busybox works by calling binaries from a file outside of /system/bin/. We must make this file by issuing the following command:
Code:
adb shell mkdir /data/busybox
[*]Lets make sure we can install busybox without permission probles:
Code:
adb shell chmod 777 /data/local/busybox
[*]Next install busybox in the folder:
Code:
adb shell /data/local/busybox --install
[*]We now need to take the /system/folder, and mount it as a writeable folder:
Code:
adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
[*]Link it into bin:
Code:
adb shell ln -s /data/local/busybox /system/bin/busybox
You now have busybox installed
Permanent root (pr4)
THANKS TO INDIRECT for Files and Scripts
We will need SU and Superuser.apk
First we need to install the Superuser.apk:
Code:
adb wait-for-device install Superuser.apk
adb remount
[*]Next lets go ahead and push the su application up to the /data/local/ folder
Code:
adb push su /data/local/
[*]Next we will need to change the permissions and cp su from the /data/local/ folder to the /system/bin/
Code:
adb shell chmod 4755 /data/local/su;mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system;busybox cp /data/local/su /system/bin
Installing GApps (eab1)
THANKS TO ANALOG and INDIRECT for Scripts
First things first we need to download the GAPPS. The most reacent one is this one or get the most recent one here.
[*] Unzip and navigate to the most root folder of that package in your shell.
[*]We need to verify that adb is booting into root. To do this we can issue the command:
Code:
adb shell id
If id doesn't return root then you will need to re-zergRush your device
[*]Now it is time for us to export the apps to the directories.
Code:
adb shell mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system
adb push system/app/CarHomeGoogle.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/app/FOTAKill.apk /system/app/
adb shell chmod 644 /system/app/FOTAKill.apk
adb push system/app/GenieWidget.apk /system/app/
adb shell chmod 644 /system/app/GenieWidget.apk
adb push system/app/GoogleBackupTransport.apk /system/app/
adb shell chmod 644 /system/app/GoogleBackupTransport.apk
adb push system/app/GoogleCalendarSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleCalendarSyncAdapter.apk
adb push system/app/GoogleContactsSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
adb push system/app/GoogleFeedback.apk /system/app/
adb shell chmod 644 /system/app/GoogleFeedback.apk
adb push system/app/GooglePartnerSetup.apk /system/app/
adb shell chmod 644 /system/app/GooglePartnerSetup.apk
adb push system/app/GoogleQuickSearchBox.apk /system/app/
adb shell chmod 644 /system/app/GoogleQuickSearchBox.apk
adb push system/app/GoogleServicesFramework.apk /system/app/
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb push system/app/LatinImeTutorial.apk /system/app/
adb shell chmod 644 /system/app/LatinImeTutorial.apk
adb push system/app/MarketUpdater.apk /system/app/
adb shell chmod 644 /system/app/MarketUpdater.apk
adb push system/app/MediaUploader.apk /system/app/
adb shell chmod 644 /system/app/MediaUploader.apk
adb push system/app/NetworkLocation.apk /system/app/
adb shell chmod 644 /system/app/NetworkLocation.apk
adb push system/app/OneTimeInitializer.apk /system/app/
adb shell chmod 644 /system/app/OneTimeInitializer.apk
adb push system/app/Talk.apk /system/app/
adb shell chmod 644 /system/app/Talk.apk
adb push system/app/Vending.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions/
adb push system/etc/permissions/features.xml /system/etc/permissions/
adb push system/framework/com.google.android.maps.jar /system/framework/
adb push system/lib/libvoicesearch.so /system/lib/
Now you have GApps installed from Anlog's. All Credits go to him and Indirect
Full system restore/wipe (fsr6)
THANKS TO INDIRECT
WARNING THIS WILL WIPE YOUR ENTIRE FILESYSTEM!!!
Go into adb shell or terminal emulator.
Issue command:
Code:
echo -n '0000' > /bootloader/BootCnt
Next reboot your device by conventional methods or issue:
Code:
reboot
Your nook will now restart and tell you it is resetting.
You now have a clean slate!
Got some links for howto's on the adb connection/root.
Yeah - if someone has details on how to adb connect and root, it'd be helpful to include links. I've yet to see specifics for either.
Reserved
Sent from Tapatalk, NOOK Color CM7 Nightly's!
I aplogize im still typing them up
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
The Droid 2 and Droid X had locked bootloaders with the 'e-fuse' and Koush got around them and installed CWM with this...
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
What do you guys think? I don't have a NT yet to try anything (probably won't get one until sometime around x-mas).
l
Indirect said:
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
Click to expand...
Click to collapse
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Superoneclick...love!
Sent from my Nook Tablet using Tapatalk
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Not at all so long as you give proper credits.
Loglud said:
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox: COMPLETE
permanent root: IN PROGRESS
bootloader: Locked and Signed
By the bootloader being locked and signed it is very difficult to design anything that will boot besides nook roms. In order to solve this some of the Devs have suggested the following:
kexec: RESEARCHING
2nd init: RESEARCHING
CWM: NOT STARTED
Please PM me or post if you know anything else, and or want to add anything.
Click to expand...
Click to collapse
hopefully it is cracked soon cause i dont want to buy this if i can't have a full custom rom, all of the verizon motorola phones run roms off of 2nd init and it just isnt the same to be honest. you can never run a full custom rom with second init(well you can but you have to build the rom to fit the kernel) and honestly i want my device to be mine
you should tweet cvpcs or someone who makes and maintains 2nd init roms to get more info on it though
Can't get busybox installed
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
kgingeri said:
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Still some glitches installing busybox...
Loglud said:
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Click to expand...
Click to collapse
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
kgingeri said:
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
Click to expand...
Click to collapse
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Loglud said:
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Click to expand...
Click to collapse
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
kgingeri said:
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
Click to expand...
Click to collapse
re run zergRush exploit. your adb shell is defaulting to the shell username. by rerunning the zergy you will allow for yourself to use the adb shell as root. make sure you dont run it as the root user though. you are also more then welcome to hop in irc and ask questions.
Any one having difficulty rooting or see anything that needs to be updated?
What do we have here?
EternityProject EasyRoot for ICS is a 1 click root method to your Motorola RAZR, Droid RAZR and RAZR MAXX running Android Ice Cream Sandwich using miloj's exploit.
What does it do?
EternityProject's EasyRootICS package contains a batch script for Windows and Linux made by me and kholk to automate the root process using miloj's exploit on the current Motorola's ICS devices (it may work on Droid4, too).
NEW: EternityProject EasyRootICS now installs a working version of Adobe Flash Player to your Razr / Maxx runninc ICS 4.0.4
How to use it:
1. Download and unzip the package (hint: save it to your PC Desktop)
2. Install Motorola Drivers - Get it here (hint: uninstall others android devices drivers from PC)
3. Enable Unknown Sources (Config > Security > Unknown Sources)
4. Enable USB Debug (Config > Developer Options > USB debug)
5. Enable Mock Locations (Config > Developer Options > Mock Location)
6. Connect the phone to your PC as Media Sync - MTP (Change it after connect you phone to PC in Config > Storage > Media Sync)
7. Run the script (Double click on .bat file from PC)
8. Enjoy!
We proudly presents to you a 100% Working build of EternityProject EasyRootICS v1.5 *Updated* 02/09/2012
Direct Download Link:
http://dlhg.eternityproject.eu/mtspyder/eprj/pedro/EPRJ_EasyRootICS_MultiOS_v1.5.zip
----> Please, respect us! Do not post direct download links and do not reupload this file on other filehosters. If you want to share it, redirect to this thread! <----
What's new?
V1.0
- EternityProject EasyRootICS works for any ICS 4.0.4 builds:
- Devices Tested: HTC One X and Motorola Razr and Droid 4! It may work to more devices!
- su binary updated
- Superuser app: switched to SuperSU by Chainfire
- Correct installation of Busybox
- su binary now goes to correct path with correct permissions
V1.1
su binary updated
Fixed Linux build.
V1.2
su binary updated (Run SuperSU after root to su binary update be applied)
SuperSU updated v0.94
V1.3
SuperSU updated v0.95
V1.4
SuperSU updated v0.96
su binary updated
Exploit fix
V1.5
Installs a working version of Adobe Flash Player for ICS to your Razr.
Note: If you get a 'su/superuser' already exist message, use the alternate root method created by Dan Rosemberg with su binaries and superuser app updated by me. Get it here
Notice: This is an alternate root method, don't use it as primary root tool there's a reason for that.
How do I unroot from this?
Just run the SuperSU and press 'Full unroot' (if you have superuser app installed uninstall it first with an app like Titanium Backup)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You might also like to watch this video tutorial by Hrishi21007
Liked it? Press thanks button. You can alsoBuy me a Cold Beer!
Remember: To get rooted you need an ADB connection. Check if ADB is enable in Device Manager:
Thanks to EternityProject Main Developer kholk for the patience! lol
Thanks to all the @XDA users that provide us logs and feedback!
Thanks to FrAsErTaG for the tip on the batch: headache killer man! :good:
Any chance anyone can come up with a Linux version of this script?
aryonoco said:
Any chance anyone can come up with a Linux version of this script?
Click to expand...
Click to collapse
We may have a linux version by tomorrow.
Thanks
Very nice pedro and eternity team, I will definitely use this when ICS arrives!
eyriiii said:
Very nice pedro and eternity team, I will definitely use this when ICS arrives!
Click to expand...
Click to collapse
Thank you, hope you get ICS soon.
Claro Brasil is already releasing it OTA.
Cheers
pedrotorresfilho said:
Thank you, hope you get ICS soon.
Claro Brasil is already releasing it OTA.
Cheers
Click to expand...
Click to collapse
To bad I dont live in brasil then
Awasome thanks pedro
Getting stuck on this
Tried this but it takes me to shell prompt...am i missing something?
######################################
# EternityProject's easyROOT #
# for Motorola RAZR #
# #
# #
# By pedrotorresfilho and kholk #
# Exploit binary by miloj #
# #
# If you wanna support us donate to: #
# kholk -- [email protected] #
#pedrotorresfi. -- [email protected]#
# #
# or come on our Website! #
# http://www.eternityproject.eu #
# #
# Happy Rooting! #
######################################
Press any key to continue . . .
----------------------------------------------
--- Please, connect your Motorola RAZR ---
--- and make sure that ADB mode is enabled ---
--- prior continuing. ---
----------------------------------------------
Press any key to continue . . .
.
[Step 1] Rooting...
2033 KB/s (22364 bytes in 0.010s)
2869 KB/s (1862336 bytes in 0.633s)
40 KB/s (123 bytes in 0.002s)
[email protected]_spyder:/ $
eyriiii said:
To bad I dont live in brasil then
Click to expand...
Click to collapse
Move to Brasil!
Pzyduck said:
Awasome thanks pedro
Click to expand...
Click to collapse
You're welcome!
droidier said:
Tried this but it takes me to shell prompt...am i missing something?
Sorry for the missed line, Script has been fixed to v0.2
And Thanks for the log!
Click to expand...
Click to collapse
Thanks Pedro & kholk, well done guys.
Haven't tried it but seen pre-alpha-version With typing cmd lines I understood more clearly how it works, lol.
Anyway I think that I will need it someday cause my experiments don't seem to end in the near future xD
The Windows script has been fixed and released as v0.2.
Cheers!
The EternityProject Team Manager & Main Developer,
--kholk
Still not working for me , error i get is
step 1 rebooting
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
[Step 2] knocking at the door ....
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
and yes I have drivers installed and ADB is indeed running
running Windows 7 x64
[Step 1] Rebooting...
.
.
.
[Step 2] Knocking at the door...
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
debugfs: write /data/local/12m/su su
Allocated inode: 22802
debugfs: set_inode_field su mode 0104755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
stuck in this step..
Ramdanih said:
[Step 1] Rebooting...
.
.
.
[Step 2] Knocking at the door...
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
debugfs: write /data/local/12m/su su
Allocated inode: 22802
debugfs: set_inode_field su mode 0104755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
stuck in this step..
Click to expand...
Click to collapse
Same here.
672.180.17.XT910.Retail.EU
maniAK- said:
Still not working for me , error i get is
step 1 rebooting
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
[Step 2] knocking at the door ....
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
'adb' is not recognized as an internal or external,
operable program or batch file.
and yes I have drivers installed and ADB is indeed running
running Windows 7 x64
Click to expand...
Click to collapse
You need to connect your razr as MTD and make sure USB debug is enable.
Ramdanih said:
[Step 1] Rebooting...
.
.
.
[Step 2] Knocking at the door...
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
debugfs: write /data/local/12m/su su
Allocated inode: 22802
debugfs: set_inode_field su mode 0104755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
stuck in this step..
Click to expand...
Click to collapse
Reazy64 said:
Same here.
672.180.17.XT910.Retail.EU
Click to expand...
Click to collapse
Thank you very much for the logs.
You were a step ahead to get rooted. Just wait it reboots.
Cheers
pedrotorresfilho said:
You need to connect your razr as MTD and make sure USB debug is enable.
I forgot to add
device is connected is MTD and USB debug is enabled
is there any other things i could try besides the obvious
T
Click to expand...
Click to collapse
maniAK- said:
pedrotorresfilho said:
You need to connect your razr as MTD and make sure USB debug is enable.
I forgot to add
device is connected is MTD and USB debug is enabled
is there any other things i could try besides the obvious
T
Click to expand...
Click to collapse
Your adb seems not be in the same package you have extracted it.
Check it
Code:
adb devices
If don't connect your Razr to another USB port.
Cheers
Click to expand...
Click to collapse
pedrotorresfilho said:
You need to connect your razr as MTD and make sure USB debug is enable.
Thank you very much for the logs guys.
Please, download EasyROOTICS again and let me know about root.
Script has been updated with Win/Linux v0.4
Cheers
Click to expand...
Click to collapse
got past that first error now i get same error as other guy above
[Step 1] Rebooting...
.
.
.
[Step 2] Knocking at the door...
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
debugfs: write /data/local/12m/su su
Allocated inode: 22802
debugfs: set_inode_field su mode 0104755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
stuck in this step..
maniAK- said:
got past that first error now i get same error as other guy above
[Step 1] Rebooting...
.
.
.
[Step 2] Knocking at the door...
debugfs 1.42 (29-Nov-2011)
debugfs: cd xbin
debugfs: write /data/local/12m/su su
Allocated inode: 22802
debugfs: set_inode_field su mode 0104755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
stuck in this step..
Click to expand...
Click to collapse
Sent you a PM, please read your in box.
Thanks a lot for the feedback! We have actually 2 Razrs. Eu and Latam both sucessfully rooted.
BTW, Go to google play and update your superuser. AFAIK you've done!
Just reboot it and check root with Root Checker
Cheers
cheers Pedro sir
got it working now
seems rooted with all superuser fuctions
your da man
What i did was change the USB ports after Pc reboot as Windows 7 x64 needs that now and again
and then i read up on your thread which i should have done in first place and grabbed latest version EPRJRAZR_EasyRootICS_MultiOS_v0.4
after rooting with EPRJRAZR_EasyRootICS_MultiOS_v0.4 i installed Superuser.apk and then installed Rootchecker from market just to confirm
Superuser now full root access
Thanks again