This is only for use on the X10 Mini Pro.
Credits go to nobodyAtall & D4rKn3sSyS for the actual CWM files. Other credits in the README.txt file.
Both version currently use CWM v3.x r5
Windows
Requirements:
Windows PC
USB Cable
Phone driver installed
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode.
Connect your phone to your computer
Open up install.bat and follow the instructions inside that.
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
21-03-2012 v5
Updated Superuser apk and su to version 3.0.7
Replaced SuperOneClick with alternative method
Prefixed relative paths with %~dp0 to complete full paths. This is to combat over zealous group policies. Thanks go to satanselbow
Linux
Requires your phone to be ROOTed but there is now a ROOTer for Linux that can ROOT your phone if not already done. Can be found in this forum.
Requirements:
*nix PC/Laptop
USB Cable
Android Version 2.1 Stock ROM (2.1.1.A.0.6) (May work on Froyo and Gingerbread ROM's but any custom ROM should have a recovery already installed)
Usage:
You need to set your phone in Debugging Mode
Connect your phone to your computer
Open up terminal
Go to the directory it is extracted to
Start the installer by typing "sh cwm-x10minipro.sh"
CWM Usage:
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CWM recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Last Update:
23-Sept-2011 (v4)
Fixed question about USB Debugging
Fixed permissions on ADB
Links:
Original X10 Mini CWM Thread: http://forum.xda-developers.com/showthread.php?t=1105745
Original X10 Mini Pro CWM Thread: http://forum.xda-developers.com/showthread.php?t=1106146
Changes:
The changes for the latest version are included in the relevant sections above. A more detailed list of changes across all versions is in the CHANGES.txt file that is in the archive file.
Download:
Windows: Download
Linux: Download
Please do not re-host or re-release without permission.
Don't forget if you found this helpful please push the "Thanks" button
copy failed read only file system
is this basically a batch file?
because if so i could port it to linux for you
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
...
..
Для продолжения нажмите любую клавишу . . .
Starting ADB Server if not started.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Getting ROOT rights.
rootsh: permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Enter the mtdblock number listed "/dev/block/mtdblock? on /system"
Enter mtdblock number: 0
Mount system as R/W.
mount: Operation not permitted
Do you already have a recovery installed? (Y/N):n
Pushing recovery tar file.
failed to copy 'recovery\recovery.tar' to '/system/bin/recovery.tar': Read-only
file system
Pushing chargemon.
failed to copy 'recovery\chargemon' to '/system/bin/chargemon': Read-only file s
ystem
Setting permissions for recovery tar file.
Unable to chmod /system/bin/recovery.tar: Read-only file system
Setting permissions for chargemon.
Unable to chmod /system/bin/chargemon: Read-only file system
Stopping ADB Server.
* server not running *
..
i always rooted
Ok, Currently working on a new version which hopefully fixes your issues.
Thanks I will dl it and take a look later and post the result here
Sent from my U20i using XDA App
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Finnaly! Thank you! Would love to see cwm being imported in the slades kernel, that way we never have to deal with broken files!
Snoopo said:
how did you root your phone? I also don't have a script called "rootsh". also you can check if you are rooted with "id". many ppl like me are just rooted after entering the shell
also it's better to use "su" when calling commands that have to be done by root: "su - -c 'mount xyz' "
also don't forget the "*" if you check for keyboard inputs (there are people that may miss the key they wanted to push .D)
good luck.
Click to expand...
Click to collapse
Yeah I just noticed that i left rootsh in there. Was just something I was playing with.
One thing I hate is Permission Denied error's with adb... Oh fun.
damn. i just did the port and managed to delete the files. DAMN windows temp file thingys anyway tommorow it will be done
TY man u awesome!!!!! thx u all work fine!!!!
rect2409 said:
mopgawka - Did you get the correct mtdblock number. The file would set the system dir as r/w to enable you. The mtdblock number is the number directly after the text mtdblock, in the image below it is 0.
Another question was there an error after the "Getting ROOT rights" text? This was the bit that caused me the most issues.
x10man - Yes it is just basically a batch file. If you want to port to linux then go ahead
Click to expand...
Click to collapse
In linux we used to set the mount point to a variable and then issuing the r/w command. I don't know how you can do this trick in windows.
Code:
mtd=mount | grep system | awk '{print $1}'
echo "Mounting /system rw"
mount -o remount,rw -t yaffs2 $mtd /system
The question about the mount point isnt in the newer version. It just assumes that the system mtdblock is 0.
If it causes a problem in the future I may change it back to selecting the mtdblock number but from all the times I have tried the mtdblock on the x10 mini pro has always been 0.
In windows the answer is just saved as a variable that you assign to the question.
Sent from my X10 Mini Pro using XDA App
Updated with v3.
Just added new way of gaining ROOT access and another check to make sure phone is ROOTed.
EDIT: Oops forgot I had posted last :/ Sorry
3.2.0.0-r3 is old newest is 3.2.0.0-r5
I tried to fix permissions but it's been doing that for almost an hour now... Is that normal, to take that long? Should I remove the battery?
EDIT: Forget it, after looong time waiting, it's finished
EDIT 2: It erased all my preferences! Is that supposed to happen?
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
rect2409 said:
I have never had to fix permissions myself so I don't know the process it uses. You could try in the CWM thread where they should be able to help you. Link is http://forum.xda-developers.com/showthread.php?t=1106146
Sorry
quangnhut123 - I don't have that version of CWM and the CWM thread only has r3. If you have r5 then could you give me the files please and will update it.
Click to expand...
Click to collapse
r5 is the one with multiboot i believe
x10man said:
r5 is the one with multiboot i believe
Click to expand...
Click to collapse
Ahhh. Okay didn't realise that.
Have uploaded a version that includes r5 for the people that have to have the latest... Also kept v3 up as all that has changed is the CWM version.
Related
Hello everyone!
You may or may not know me, however I have secretly been working behind the scenes with ChiefzReloaded to learn how Android works. Together we have been trying to develop new ways to root the Slide, primarily because we both landed in a sticky situation that left us both without root and without a way to revert to root.
After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
To get started, please see the bottom of this post for the link and download it. You will want to download it to your computer and not your phone's SD card. Also, you will need the tools from the Android SDK. I would suggest extracting the file from my zip at the bottom of this page into the Android SDK's tools directory.
Extract the zip
Make sure your phone is in USB debugging mode AND you are in "Charge Only" mode.
Connect your phone to your computer.
Make sure you're in the same directory as where exploid is extracted before continuing to the next step.
Issue the following command: adb push exploid /sqlite_stmt_journals. Note: It MUST be in that directory - NO exceptions.
Run: adb shell
Run: cd /sqlite_stmt_journals
Run: chmod 0755 exploid
Run: ./exploid
Toggle your phone's Wifi (on or off, however you wish to do that).
Now (again) run: ./exploid (if prompted for a password enter: secretlol)
The next line should now begin with a pound (#) - if not, then something isn't setup right. Make sure to follow the directions verbatim. If you suspect you did follow them correctly, please reply to this post letting me know.
You should now be root! At this point you can do many things, but if you're looking to flash a custom ROM, continue to these instructions:
[NEW 10/18/2010:]
Steps 1-12 are intended to get you the ability to flash mtd0.img (which previously required using the SimpleRoot method) by gaining root inside of Android. By following the instructions in the rest of this section, it will allow you to flash a ROM or S-OFF your device:
The files you need are at: http://forum.xda-developers.com/showthread.php?t=703076- download both files linked in there (ESPRIMG.zip and SlideEng-package.zip)
Extract the contents of SlideEng-package.zip to a place of your choosing on your computer.
Place the entire (unextracted) ESPRIMG.zip on your SDcard.
Now push the files 'flash_image' and 'mtd0.img' that you just extracted from SlideEng-package.zip to /data/local using 'adb push'. (Noob? Instead of using 'adb push', install Droid Explorer and, using that utility, copy the 'flash_image' and 'mtd0.img' files to /data/local on your Slide)
Now I'm going to assume your phone is at root prompt (#) using steps 1-12. So now do (without typing the '#' symbols in front of both lines - they're just there to remind you that you need to be at a '#' prompt):
Code:
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Before you reboot make sure that the ESPRIMG.zip is on your SDcard!
Now turn off the phone.
Then press Volume-Down + Power.
The phone will power on and after about 5 minutes of verifying ESPRIMG.zip it will ask you if you want to flash it.
Press Volume-Up for 'YES' and wait until it finishes (ABSOLUTELY DO NOT POWER DOWN WHILE IT'S STILL FLASHING!!!).
Now when you go into recovery it should allow you to 'Apply update.zip from sdcard' (booting into Clockwork). If you don't have the Clockwork update.zip, here it is: http://www.4shared.com/file/OTRU7T3y/update_2.html (rename to update.zip after downloading since it's currently update_2.zip, then place it on your sdcard).
[/NEW 10/18/2010]
[NEW 12/30/2010]
Optional: Now that you're rooted you might want to disable all flash memory protections so you can permanently flash Clockworkmod (recovery - no more using an update.zip!) as well as other random things. Check here for details: http://forum.xda-developers.com/showthread.php?t=798168
[/NEW 12/30/2010]
CREDIT GOES TO:
[*] ChiefzReloaded! (For helping me learn the intricacies of Android and patiently answering all of my questions)
[*] 743C (For developing the original exploit)
Source code: (Yes, it's hackish. I was just trying to figure out why the system kept rebooting and haven't cleaned up the code since) download
DOWNLOAD:
http://www.4shared.com/file/CZsxSq-f/exploid.html
DONATE:
(Anything helps!)
(Some people may wonder why this is special compared to the One Click Root application. What's important is that One Click Root doesn't work on Slides running production/retail software, likely the same problem I had to fix to get exploid to work in my version.)
Thats whats up!!
If you be trollin then YOU BES TRAWLLIN
But if not then good job nb!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
Sure, I was getting around to that - and I understand your concern. I'll post it in a second.
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Sent from my T-Mobile myTouch 3G Slide using XDA App
r0man said:
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Click to expand...
Click to collapse
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
nbetcher said:
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Click to expand...
Click to collapse
Ill take a look at it when I get home.
ilostchild said:
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
Click to expand...
Click to collapse
I actually had to do a lot of work on it. It doesn't quite work the same as the original exploid simply because the original exploid crashes the entire system and reboots. This causes the rootshell to never be committed to NAND and thus you get no where. I had to keep playing with things until I found a different method that works. It took several hours of me being upset with it, but watched the latest Burn Notice, came back to it, and BAM I had a stroke of genius.
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Armyjon88 said:
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Click to expand...
Click to collapse
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Sweet
Sent from my T-Mobile myTouch 3G Slide using XDA App
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
statuzz said:
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
Click to expand...
Click to collapse
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
nbetcher said:
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Click to expand...
Click to collapse
Let me know if you want to work together on some kind of one-click root app for the Slide. If the commands work through the terminal on the phone itself rather than via adb, I could probably make this into an app already, but since you're working on a more non-developer-friendly version, I'll just wait until that's out
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
I'm delaying the release of my non-developer program for another couple hours.
As far as what you said above, all you need to do after gaining the # prompt is (in a separate window):
adb push flash_image /data/local
adb push mtd0.img /data/local
(switch back to your # adb shell, then type
cd /data/local
chmod 04755 flash_image
./flash_image misc mtd0.img
Then reboot and apply the ESPRIMG.zip. All of these files are found on the same post that I referenced in my OP. These instructions are all in that same page.
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
Im also stuck since im not sure if you can update to eng from the ota..But first i want to personally thank the OP & CR for providing this.
This would be great for a One Click method
this would be nice to work into a one click root!
And This did work for me!
Does this root method gets /system moumted when android running?In short do we finaly get metamorph and root explorer working?
Let me first say that I have read every post I could find on this subject and tried them all with no success. I rooted my Aria using the Ubuntu Live CD so I could use Titanium backup and eventually try different roms. My phone is still using the stock rom. I then installed Titanium backup which reports "your system settings will prevent you from restoring applications. to correct this go to your phone's settings, then in "applications" and tick the "unknown sources" check box."
The unknown sources check box is of course not there because I have not been able to successfully run the code for allowing non-market apps.
From terminal in the Ubuntu Live CD with USB cable connected and set to charge only. I tried and got "remount failed: operation not permitted." at the adb remount step.
Linux Code:
sudo su
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
I downloaded the android-sdk_r07 and extracted it to my C drive. From a Windows command prompt, I changed to the sdk\tools folder. Adb devices sees the phone but adb remount fails with "remount failed: operation not permitted."
Windows Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
I found a post from attn1 that I have not tried that said:
"Put your phone in recovery mode. Go to advanced>mount system and mount data. Follow steps in post #13 (using the windows or linux code above) in cmd screen and you'll be fine." I am not comfortable in trying this approach as there are not enough specific step details and I don't want brick my phone.
I would really appreciate the correct detailed steps to enable non-market apps using the supplied code either from Windows or the Ubuntu Live CD. Thank you in advance.
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
winsettr said:
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
Click to expand...
Click to collapse
Thank you winsettr for your post. It looks like running the commands from recovery did indeed work. Titanium backup no longer reports the "your system settings will prevent you from restoring applications. To correct this go to your phone's settings, then in "applications" error.
However, I expected to see the settings\applications unknown sources check box check box and it is not there. I guess I will have to try side-loading an app to confirm that it will work.
I think that gui option would be part of the rom, a part that AT&T has removed... So yeah, see if side- loading works now.
Sent from my Liberty using XDA App
FYI, I am indeed able to side load now from an .apk copied to the sd card. However, I am not able to install from an internet link. Trying to do so generates a "your phone is not authorized" error message.
Until you get a custom rom running, I wouldn't worry too much. Sounds like you can get any app you want (just download internet apps to sd then install). There may be an additional setting in settings.db but that's beyond my knowledge...
Sent from my Liberty using XDA App
Viewpad 7 rooting
I tried to root with superoneclick 1.7 (rageagainstthecage)
but it remount the system with read only access? and i am not able to use busybox or rom manager to install clockmod, any advise please?
"SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 KB/s (5392 bytes in 0.015s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1090 KB/s (1062992 bytes in 0.951s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
822 KB/s (26264 bytes in 0.031s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1366 KB/s (196521 bytes in 0.140s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!"
I can use adb shell to go into the device and do a SU, but when i do a chmod to system directory to do a clockmod, it wont work as it is read-only..
seeking advice on this one..
Thanks!
bump.. any help????
help???????
Dumb question: have you tried with:
Code:
adb remount
And then:
Code:
adb shell
chmod
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
HeeroYuy84 said:
C:\Users\Aniki\Desktop\SuperOneClickv1.7-ShortFuse>adb remount
remount failed: Operation not permitted
any ideas?
Click to expand...
Click to collapse
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
brainmaster said:
Yes, either you didn't activated the USB Debugging in the Settings > Apps > Development. Or you don't have root on your phone.
Click to expand...
Click to collapse
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
This one works for my VPAD7 running Froyo 2.2.2 (which I believed is the newest OEM ROM) - http://android.modaco.com/topic/343143-rooting-and-installing-clockworkmod/
Add'l VPAD7 hardware/firmware info - 2.6.32.9 and 1008_3.350
Download & install ES File Explorer and copy the *.apk file in the link to your microSD card - restart phone, run the apk and then install cwrecovery, etc. Read & follow the directions in the modaco link carefully, and you should be fine.
A word of caution - the older ROMs written for VPAD7 are NOT compatible with the newest touchscreen ("ITE") hardware. FYI - the Clean Viewpad7 V1.0 ROM might or might work. Have a BACKUP of your original stock/oem first done before doing any custom ROM flashing.
Good luck !
HeeroYuy84 said:
i did, i have got superuser in my viewpad, and the logs say success in rooting
i can do a adb shell but there is no prompt when i do a su
Click to expand...
Click to collapse
Is busybox installed in the same subdirectory or folder as your adb and/or fastboot ?
From within the shell, do you see a $ at the beginning of the prompt line - indicating that SU is off. If you see a # at the beginning of the each prompt line - then SU is on and you are good to go.
Before running the su command, try running the mount command first. Give it a moment and between these 2 commands issued, if it switch to a # command without error messages, then you've been granted SU access, and, you should be good to CHMOD & flash, etc. etc.
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
Click to expand...
Click to collapse
Trying to recall how I did mine as DW has the VPAD7 now ....
Assuming you are connecting your unrooted, stock VPAD7 to a Windows-based PC for the first time, it should be recognized as a new USB / removable devices, etc. - and will auto-install a few drivers & go thru the setup sequences, and when it's done, you will seee "hardware installed & ready to use" - including PC Tools for synch. calendars & address book with MS Outlook.
Disconnect & reconnect the phone, and the upper status bar should indicate "USB connected" - open it & you are prompted to turn it "ON" and generally speaking, USB debugging mode box is checked. If not, click & bring up your device's settings, look in Application settings and then under Development, it should be the 1st. box.
Again, this is fairly basic so I suggest doing a bit more reading first and know what you are doing to root, or get someone with a bit more hands-on experience to help. If not done right, you COULD semi-brick your VPAD7 although the process to root to gain SU access is "relatively" safe - but it's tricky & took me a little while to get it done right.
The latest stock/OEM ROM running Froyo 2.2.2 is fairly good overall, has full access to Google Market for apps downloading, and only needs a few minor tweaks and add-ons as enhancement to make this tablet "fly" on the run - and the OS is stable with decent battery life (although I wouldn't mind seeing Gingerbread on it - my HTC Eris is running 2.3.5 now) Even after you gained root, you might want to leave the ROM as is and use it - I'm doing that now (rolled back from one of the few "working" custom ROM).
Good luck ! ------ and, BACKUP, BACKUP, and BACKUP
taospirit said:
hello, i want to root mine, but i don't know how to Place my device into debugging mode can u tell me please?
edit: i found another way, i used Gingerbreack method. it's all right.
Click to expand...
Click to collapse
hi
for debugging mode go to
Settings>applications> development (here u chek the USB debugging ) that's all
for rooting i have used gingerbreak it worked for me
can also read the below two links
link 1 : http://forum.xda-developers.com/showthread.php?t=1015005
link 2: http://forum.xda-developers.com/showthread.php?t=1156034
hope it help goodluck
I finally succeed into rooting and installing Clockwork into the viewpad, that how I did :
1. GigerBreeak 1.2 (install apk)
2. Download BuxyBox instaler 1.19.2
3. Terminal :
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system 4. follow: android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
cat /dev/mtd/mtd3 > /sdcard/orirecovery.img
flash_image recovery /sdcard/cwrecovery.img
tricky one to remount the partition, but that was the missing link for me.
I have tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started.
Gil
GilViking said:
tried many times to root with Superoneclick 1.7, 2.1, 2.2 all I ever get is "Waiting for device" after ADB killed and restarted and deamon started
Click to expand...
Click to collapse
Are you running Vista, Win7 or XP SP3, try using a different PC and/or OS - uninstall any installed USB drivers for the device, reboot & try it again.
Also, are you using the provide micro-usb cable or using a generic one, try a different one.
Lastly, while "waiting for device" message is showing, quickly unplug & reconnect the micro-usb cable to the pad, and, wait - be patient.
If you still cannot do it (SOC 1.7 is proven to work best, newer ones are NOT) - use the GingerBreak apk instead.
Thank you!
I will try your recommendations later today (West Coast USA).
Successfully Rooted VPad7
I finally got it rooted. It appears that my problem was neglecting to run stuff as administrator on my Win7 Pro. I ended up using SuperOneClick v 1.7 which is not that easy to find.
Thanks to all who helped and wrote the software!
Gil
Hallo,
Im a newbee also in android rooting, i had some question and clarification about some terms and hope someone can share their knowledge.
Here are some of my questions:
Im confused with the img backup file of each partition. Does redirecting again to each partition mean restoring the individual img file to each partition ex"cat /sdcard/mtd3_recovery.img > /dev/mtd/mtd3"
or we need a tool like in linux which is DD or DDRESCUE or something else.
For instance my backup individual partition img file i created before i install costum rom. If im correct in restoring the individual image file to each mtd partition is possible does it means im
back to the state where i used the original stock or before i installed the costum rom. Its like in linux where if u restore a dd root image file to the partition you will back to the state where you created
the image backup.
Does NANDROID backup means using a CWR recovery to backup the original/stock+rooted rom and restoring it using the same process from a costum rom will means im back to the state of original/stock+rooted rom
Im still in the rooted state right now. i just want to understand a few things like restoring to original/stock+rooted before i procedd to installing costum rom and other tweeking on the device.
Hope someone can share some info.
Thanks in advance.
Here's a quick guide to general principles of flashing ROM's (and factory RUU) in the Wiki section of XDA, and there's another sub-section of FAQ, please refer to it as a newcomer (we all were at one point ...)
http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
It's best NOT to mess around with individual *.img until you move beyond beginner's level to a higher "comfort" zone - in general, we use the tools already built-in by CWM - which has a submenu with functions for Backup, Restore (and, advanced & selective Restore)
It will create and read from the sub/directory created on the mSD card, and use it to accordingly.
You are rooted at this point, it is VERY important to go into Recovery Mode with CWM already installed/working, and make a Backup of your stock/factory ROM in its current state, this is your baseline - and, save a copy to your computer (Windows preferred) Make sure you write down any settings as necessary for future reference ...
Then, you can explore and install custom ROM by flashing the Zip saved/moved to the mSD card - and go thru the initial Setup steps. When your new ROM is working & stable, running smooth - go back into Recovery & do a Backup (a new subfolder will be created with everything you need to Restore later on, if & when needed - it will be time/date stamped for easy reference.)
If something go wrong, boot into Recovery, then select Restore & highlight your last known working saved Rom, and it will prompt you to reboot/restart once it's done. **
After a while, it will become second nature - just remember ** to always do a full wipe (dalvik, cache & system) when changing custom ROMs (which you should & will learn along the way - to clean the device of any old, residual codes & settings, etc.)
Hi,
Sorry for my English; I'm French people.
I have an HTC Tattoo with HCDR ROM 1.7 since one year. But with the patched market i can't have the new version of the market. I read lot of topic about the subject in this forum and the Frandroid forum but I not found a running issues.
Have you got a solution for my probem ?
Thaks a lot,
Florian
florianlyon
Dude, hey! I ran into same problem.
Here you go: http://forum.xda-developers.com/showthread.php?t=723255&page=66
read last messages in the thread, especially my posts
Hey !
Thanks for you answer. I have already read this posts but it's not work for me !
If you have successfully fix this problem please leave me the procedure and shell command.
Follow the URL and download original market:
http://www.mediafire.com/file/wrw9tdzhveoqvgh/Vendingtrue.apk
Then reboot your phone to recovery.
Start cmd in windows.
Go to C:\rtattoo folder (i presume u use 1-click root-rec too).
If necessary mount your phone's system partition as RW:
Code:
adb shell mount -o remount,rw system
And the main command u have to run here is:
Code:
adb push Vendingtrue.apk /system/app/Vending.apk
note: of course it's implied that Vendingtrue.apk should be in the same directory as adb or locate it in a different way if u want.
If push command executes successfully just restart your phone, if not - then, naturally, do some work around. U may even try running it under loaded Android, it may do the trick too (for example, once when i tried installing hosts file it worked).
The main idea, as u might have already guessed , is to replace Vending.apk. Then it will autoupdate itself at the first time u launch it.
Hope it helps, good luck, dude!
I have try this procedure when Android running but it was impossible to push the new Vending.apk even with the system partition mounted.
But in Recovery mode I could push the new apk.
But when I launch the market it not auto update and when I run
Code:
adb pull /system/app/Vending.apk
The Vending.apk size is 1158ko, as the vendingtrue.apk size is 1146ko.
So I conclude that the replacement was not performed.
Have you got a solution ?
Thanks a lot
Dude !
I retry and it's work !
My system partition was not mount correctly.
I launched the following command with my tattoo in recovery mode :
Code:
adb shell
mount /dev/block/mtdblock3 /system -o rw
ctrl+c (or exit)
adb push Vendingtrue.apk /system/app/Vending.apk
I reboot my tattoo and launch :
Code:
adb pull /system/app/Vending.apk
The size is 1146ko (YES my APK has successfully replace).
I ran the market, 5 minute after, it was up to date.
thank you very much for your precious help !
the new market is rubbish...too bug...too slow...get the old market...I have download the old market I can ensure you it's better than new
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
sirpy said:
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
Click to expand...
Click to collapse
Had any luck?
moding infocus m512 progress report
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
GalaxyWhy said:
Had any luck?
Click to expand...
Click to collapse
sirpy said:
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
Click to expand...
Click to collapse
Sounds good Keep me posted!
EDIT:
Are you running the most updated software? - http://www.infocusphone.com/m512updates.html
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
rooting infocus m512
GalaxyWhy said:
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
Click to expand...
Click to collapse
I bought it on lightinthebox.com anyways it shouldn't be much a problem to root it, since it's possible to flash a boot img to the device using fastboot.
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
{
"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"
}
In this picture it shows the phone having a recents button but on the website I bought it off it has a menu button. Which one does yours have?
You seem to know more about this stuff than me, I've usually bought well supported devices and rooting was a one click process. I just wanna get root access to be able to use Xposed Modules
Sent from my LG-D802
How'd you go?
I just received mine and I want to root it
rooting infocus m512
GalaxyWhy said:
How'd you go?
I just received mine and I want to root it
Click to expand...
Click to collapse
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
sirpy said:
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
Click to expand...
Click to collapse
Yeah 100% mine didn't have root but I figured it out after lots of searching around. I posted my method here http://forum.xda-developers.com/gen...discussion-t2893455/post55787107#post55787107 so others could do it if they wanted to
Similar problem here
sirpy said:
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
Click to expand...
Click to collapse
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
modifying fstab
Beni.Falk said:
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
Click to expand...
Click to collapse
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
sirpy said:
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
Click to expand...
Click to collapse
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Beni.Falk said:
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Click to expand...
Click to collapse
Well, yes you can try to run fsck. you should follow the method i've outlined in previous post on how to boot the device into ftm mode. then you should be able to run fsck on the system partition (/dev/block.../by-name/system). you will need to run fsck with ext4 option, though i'm not sure if fsck is included, so you might need to download the android version of it and copy it to your device in ftm mode to the root directory change its permissions to 755. (remount / partition as rw)
Firmware download link not working
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Tinox said:
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Click to expand...
Click to collapse
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
already upgraded by seller ?
sirpy said:
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
Click to expand...
Click to collapse
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Tinox said:
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Click to expand...
Click to collapse
download any terminal app, and type "su" in the terminal.
Looking for firmware link
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
sirpy said:
download any terminal app, and type "su" in the terminal.
Click to expand...
Click to collapse
Tinox said:
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
Click to expand...
Click to collapse
well as I said, from what you previously described you don't need the upgrade, you already have the latest.