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.)
Related
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
I was excited about the rollout of Android 2.1 on X10 last November (it finally arrived...), then I was able to install more apps and experience more fun with upgraded os. However, here also comes the problem, I only had 40MB left in my internal memory, and App2sd can only be done with millions of steps...
So I was thinking.. if I have to put in so much effort just to get App2sd working, why not just spend the effort to install a custom ROM with Android 2.2 (where App2sd becomes a build-in capability, and I will be able to do voice actions too!)
Honestly, it was easier than I thought, but there are some details you probably want to pay attention to in the process, so I am writing this comprehensive guide here that can be easily followed (even for newbies!).
[All credits go to the CyanogenMod dev team for the custom ROM, zdzihu for xRecovery, Androxyde and Bin4ry for FlashTool, ShortFuse for SuperOneClick, Froshed Blue for themes.
Thank you all for the incredible work to make this possible! And sorry if I missed anyone...
NOTE: I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG.
1. Back up all your data.
- Use apps in the market such as MyBackupPro to back up all contacts, sms, call log etc. If your phone is rooted, you can also back up app+data with it (so you won't lose your progress on games or apps).
- OR you can sync your contacts etc via your Google account, and back up all apps with Astro.
- DO NOT use the backup & restore app with the stock 2.1, after you flash to 2.2, this app won't be available anymore, and there is no way you could retrive the data from the .sbf file generated by it!
UPDATE: SE Backup & Restore is now available here in the Extras section. I haven't tested it yet but if you want you can give it a try.
2. If you have already updated your phone to baseband 2.1.54 or 2.1.55, skip this step.
- Otherwise, go to here to find and download the most updated firmware (I used X10a _2_1_A_0_435 with DualTouch).
- Download FlashTool v0.29, copy the firmware you downloaded earlier to the firmware folder in FlashTool.
- Now flash your phone with this firmware, follow the instructions on the screen.
3. Root your phone.
- Download SuperOneClick v1.7 from shortfuse.org.
- Root with one simple click.
4. Install Busybox and xRecovery.
- Get Busybox from the market, once it's opened, it will tell you that your phone is rooted, install the newest version into /bin.
- Download xRecovery, rename the apk file to xRecovery.Zip.
- Unpack the file, find ./res/raw folder with 3 files - chargemon, busybox, xrecovery.tar).
- Copy these 3 files into /system/bin using app Root Explorer. (Note: this is the manual installation method, which I found more stable, or you can just use automatic install with the xRecovery.apk downloaded earlier.)
5. Copy the files for ROM installation (CM 6.1.3 V4, Google Apps Pack, and new Android market) onto your SD card.
UPDATE: CM 6.1.3 V4.5.7 is out with Camcorder working, in this step, you will copy CM 6.1.3 V4.5, CM 6.1.3 V4.5.7 instead of V4.
6. Install custom ROM.
- Reboot your phone.
- Right after the SE white text appears, press the back button a few times until xRecovery comes on (if it doesn't work, try one more time or reinstall xRecovery using the manual method if you didn't.)
- In xRecovery, use volume button to move up and down, home to enter.
- Do a Factory Reset, Wipe Cache Partition, Advance Options> Wipe Dalvik Cache, Wipe Battery Stats.
- Then install Custom Zip and choose CM6.1.3-V4.zip (or V4.5) for your SD card for the ROM. (If you are installing V4.5, install Custom Zip - V4.5.7 after this step.)
- Install Custom Zip and choose CM-V4Gapps.zip (or V4.5.7) for Google Apps.
- Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked- Login to market once, reboot your phone to xRecovery again, install Custom Zip and choose NewMarket.zip.
If you want more selections of theme, check out this thread.
Post Actions
- Restore all your information and apps.
- Get App2SD from market to easily move apps to SD or internal memory, or you can do it manually in settings>application settings>manage application. (Note: if you want to display a widget of an app, keep the app on the phone, DO NOT move it to SD as widget will not be available for apps moved to the SD.)
- MIUI Camera is included with the ROM, or you can use Camera360 (tested working). If you want camera flashlight, use Vigenette.
UPDATE: MIUI Camcorder is working on v4.5.
- Go to settings>cyanogenmod settings and settings>ADWLauncher for more tweaks.
UPDATE: ADWLauncher is been replaced by another launcher (I forgot the name) in V4.4+
_______________________________________________________________________
Read my blog for more reviews and guides of Android - http://baimandy.wordpress.com
Follow me on Twitter: MandyBai
Thanks! This kind of combined all the guide together makes it so much clearer~
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
mjrabhi said:
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
Click to expand...
Click to collapse
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
4androidonly said:
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
Click to expand...
Click to collapse
Thank you much much
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
thanx ... good guide
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
gil2004xp said:
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
Click to expand...
Click to collapse
Hmmm ... never thought of that since it doesn't concern me but if you want to change LED notification color for different apps, you can do it at CMsettings-user interface.
wasiimabbas said:
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
Click to expand...
Click to collapse
the rom is just personal preferences~ i am glad the guide helped~
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
xriel said:
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
Click to expand...
Click to collapse
really? I am not sure how to fix it since I never experienced this. But I do notice with the new 2.2 rom, it takes some time to recognize all the data on SD card at the initial start (both on the phone and on the computer).
The first time I connect to computer (USB storage mode) it took 5 mins for the computer to recognized it, and the phone was kind of froze for a while, but after that it's all fine.. maybe just try to wait a bit?
Mehn thanks for this. Soooooo easy.
becknise said:
Mehn thanks for this. Soooooo easy.
Click to expand...
Click to collapse
you're welcome
I'm just in the process of running through the guide now. Can't wait!!!
I have got a problem with completing Step 4. I have downloaded and install BusyBox from the MarketPlace but when I open it up all I get is a blank OK message and the Status: Looking for BusyBox...
Any ideas??
Also I can open xRecovery but if I click on the "Install xRecovery" button I get the little magnify glass change to a red stop circle.
Any ideas??
This is also I post of the Root Log
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 psneuter...
1466 KB/s (585731 bytes in 0.390s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1614 KB/s (1062992 bytes in 0.643s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock2
OK
Reading OS Version properties...
Version: 2.0
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1282 KB/s (26264 bytes in 0.020s)
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...
1760 KB/s (196521 bytes in 0.109s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Thanks
Thank you!!! Your guide was very helpful to me! Sorry for my bad English
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Thanks for this. Quick question, it may seem dumb but what do you mean when you say to :
"Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked"
Where in the menu do I find "programs" exactly?
NM... I didnt realize Sysctl was an App from the market. When I first completed it, I didnt have service so I couldnt use the Market. Flashed again and it works.
Thanks!
Testsubjec said:
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Click to expand...
Click to collapse
Are you referring to the parms for sysctl? if you go to the list of all applications, there is a pre-installed app called sysctl config (it's like a penguin icon), then you will be able to set the parameters there. hopefully this answers your question!
Device: Verizon Samsung Fascinate
Model: SCH-I500
Hardware verison I500.04
Firmware verison: 2.2.2
Baseband verison S:i500.04 V.ED05
Kernel verison 2.5.32.9
Build number SCH-I500.ED05
Background:
I am a simple root user who does not whish to flash any ROMs or custom mods. I just want root access to the phone. Until ED05, the SuperOneClick tool has done for the job for me every time. Verizon was kind enough to force ED05 down to me even though I declined it a about 5 days ago. I woke a couple days ago to my apps stating that root was not working. Boy was I pleased! Anyway, I promptly grabbed the lastest verison of SuperOneClick and fired it off and it said I was already rooted and asked I wanted to do it anway so I said sure, make it so Number One. But even after rerunning the root without errors, and rebooting multiple times, the applications don't think I'm rooted and the unroot process hangs when I try that. Since root is not working, I cannot take a backup via my Titanium Backup and I've never been able to use any of the CW stuff to take a backup image prior to flashing thanks to the nerfing of that process. I don't not want to lose any of my app data or SD card data in the process of rerooting and I want to be in a state that allows for very quick and easy "cleanup" of the phone in case I need to return it. I'm very nervous about trying any of the ODIN methods and losing my data or bricking the phone. Can someone please provide some detailed instructions on what the best steps are to meet my requirements?
Requirements:
1) No loss of current app data or SD card data.
2) Very low risk procedure
3) Simple procedure
4) Phone is a state that allows for quick and easy reversion to "clean" state without having to restore data from backups.
5) No custom mods/ROMs - official verizon releases preferred with Titanium Backup used to "freeze" unwanted bloatware.
ashesofthefall said:
Device: Verizon Samsung Fascinate
Model: SCH-I500
Hardware verison I500.04
Firmware verison: 2.2.2
Baseband verison S:i500.04 V.ED05
Kernel verison 2.5.32.9
Build number SCH-I500.ED05
Background:
I am a simple root user who does not whish to flash any ROMs or custom mods. I just want root access to the phone. Until ED05, the SuperOneClick tool has done for the job for me every time. Verizon was kind enough to force ED05 down to me even though I declined it a about 5 days ago. I woke a couple days ago to my apps stating that root was not working. Boy was I pleased! Anyway, I promptly grabbed the lastest verison of SuperOneClick and fired it off and it said I was already rooted and asked I wanted to do it anway so I said sure, make it so Number One. But even after rerunning the root without errors, and rebooting multiple times, the applications don't think I'm rooted and the unroot process hangs when I try that. Since root is not working, I cannot take a backup via my Titanium Backup and I've never been able to use any of the CW stuff to take a backup image prior to flashing thanks to the nerfing of that process. I don't not want to lose any of my app data or SD card data in the process of rerooting and I want to be in a state that allows for very quick and easy "cleanup" of the phone in case I need to return it. I'm very nervous about trying any of the ODIN methods and losing my data or bricking the phone. Can someone please provide some detailed instructions on what the best steps are to meet my requirements?
Requirements:
1) No loss of current app data or SD card data.
2) Very low risk procedure
3) Simple procedure
4) Phone is a state that allows for quick and easy reversion to "clean" state without having to restore data from backups.
5) No custom mods/ROMs - official verizon releases preferred with Titanium Backup used to "freeze" unwanted bloatware.
Click to expand...
Click to collapse
You can try this. http://forum.xda-developers.com/showthread.php?t=1045048 (Ignore that it says MOD, it only installs root )
(Sorry, this uses Odin, but I find it the easiest way, if your not sure then post and I'll try to answer your question, and it only installs root. Apps like SuperOneClick no longer work correctly).
Get Odin, the Samsung Drivers for SCH-I500, and this recovery: http://www.mediafire.com/?6x5utoca59et7o9. Put the su.zip on your SD card.
Install the Samsung Drivers. Power off the phone, remove the battery, plug in your phone into your computer while holding the volume down button and use Odin to install the CWM Recovery (click the PDA button and select the CWM recovery all.tar, then hit start). Once that is done, replace the battery, boot your phone by holding down power, volume down and up at the same time. Your phone will boot into CWM. Install the su.zip in CWM and reboot the phone. The kernel will remove CWM at boot so there will be no sign of it but after that your root should come back.
It worked fine for me.
That did work, thank you. I still don't quite understand what all the different pit, recovery, zip and tar files do and what exactly happens when you use the different files with Odin. Can you point to me to a "Odin and CWR for Dummies" or something that lays all this out in simple terms? I've read through the master rooting and recovery threads a few times but I still don't grasp exactly what the different pieces do and what they overwrite and when. For example, how would I go about quickly removing the root stuff from my phone now without losing all my settings and data?
It worked for me fine the other day also. And yes I was on Ed05
Sent from my SCH-I500 using Tapatalk
I was able to root 2 updates ago with SOC but just got around to re rooting after ED05 installed.
Didn't work...most annoying. lol
Checking with Root Checker and I get the following output.
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.1 - Added clear log to menu in log tab, More languages, Bugfixes is installed!
Standard su binary location: ls -l /system/bin/su:
-rwxr-xr-x root shell 26264 2010-10-16 22:04 su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root shell 26264 2011-08-15 18:46 su
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
SU binary not found or not operating properly
Any help?
jiminigrist said:
I was able to root 2 updates ago with SOC but just got around to re rooting after ED05 installed.
Didn't work...most annoying. lol
Checking with Root Checker and I get the following output.
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.1 - Added clear log to menu in log tab, More languages, Bugfixes is installed!
Standard su binary location: ls -l /system/bin/su:
-rwxr-xr-x root shell 26264 2010-10-16 22:04 su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root shell 26264 2011-08-15 18:46 su
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
SU binary not found or not operating properly
Any help?
Click to expand...
Click to collapse
The easiest way to root would be to use ODIN and flash CWM (via PDA, always)..
Then go into CWM then install the SuperUser+BusyBox.zip
I have 2.2.2 as well and the latest superoneclick did not work, but the old 1.5.5 version did work.
hey, hmm, i am new at this forum but i been rooting phones for a long time, well to make the story short, i have a samsung fascinate and i updated it to GB well after the update everything was working fine now that i want to install custom rom, or cw, trying to use odin, my computer won't recognize my phone, i installed the driver and everything but when i plug in my phone i and try to put it on download mode it shows a USB error, please can someone help i have search everywhere and can't find a solution,,, thanks thou,
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.
Hi,
I tried to upgrade the busybox with different manner (busybox, busybox installer, manual installation from xda), but no one works properly.
Each time i broke the original Archos busibox, so i lose the adb shell.
Can someone explain to me the good way to upgrade the busybox?
Thanks.
SirOch
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
SirOch said:
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
Click to expand...
Click to collapse
Google? also XDA has a great search feature have you tried that? :silly: Any particular reason why you want/need to upgrade busybox?
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
SirOch said:
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
Click to expand...
Click to collapse
Ahhh right, the quest for knowledge Your problem is as much to do with adb ( /sbin/adbd to be precise ) as it is to do with busybox, firstly you've probably wiped out the symlinks in /bin, especially /bin/sh which is the location that adbd on archos looks to run the when you do adb shell from your desktop. This is not the default location which just about every other android OEM adheares ,that is /system/bin/sh.
If you are going to upgrade the archos busybox be aware that a large number of symlinks back to /bin/busybox exist not only in /bin but also in /usr/bin /usr/sbin
Archos for reasons I still haven't fathomed, really went to town on restructuring and customized Android on the platform level.
A little tip if you've got more question, to save you bumping threads , which really does upset some folks round here... you'll probably get more more if you add more details, such as error messages etc. Saying " i lost the shell from adb." doesn't really help anyone who might be able to offer assistance. There about 10 different ways adb can fail to connect, Did the device disappear from the list or report as offline. or even come up with the message "- exec '/bin/sh' failed: No such file or directory (2) -".??
Hopefully that's helped.
Hi SirOrch,
i don't know why you loose your adb shell, but concerning busybox... the things on Archos tablets are like this:
Basically on a non rooted device we got a squashfs image mounted read only.
This image contains the stock busybox compiled by Archos (sharing system's uclibc) with limited functionality,
but containing enough tools to handle the daily job.
The path to this busybox is "hard-coded" as well. It's location is /bin which is the second entry in the path environment.
You might check that by typing printenv in your console.
The first entry should be /data/local/bin on your device.
So if you like to replace stock busybox with an advanced one, you should make sure that it will be installed to /data/local/bin.
Often there's no need to use all this apk Android Market stuff to get a proper busybox installation.
Sometimes it's little better to really understand what's happening under the hood.
Most busybox app's are statically linked, because with a static binary you don't have to take care of the device's libc or uclibc.
So you might easily extract on of the apk's or get one from xda-developers.
There are many floating around in the end.
If got one push it to /data/local/bin with adb.
You might need softlinks in this directory as well. This could be done by hand as well.
Anyway if you are a lazy person, who doesn't care about what's happening, go to the market install busybox.
Then check at /data/local/bin if it is there.
If it got installed elsewhere, some commands will still use stock busybox.
Extended commands might then use the installed one.
So check it out...
EDIT:
... aaaargh again simultaneous posting.
scholbert
Hi gentlemen,
Thanks for your help and sorry to forget to give you the error message i had:
the message was : - exec '/bin/sh' failed: No such file or directory (2) -
After investigation i found my mistake:
- In manual mode, i forget to change the ownership of busybox to root in /bin.
- when i tried to use any application from the market, the busybox was well updated in /system/xbin but the application also delete the busybox in /bin and don't change the symlinks in /bin. That's explain why adb shell won't work.
Regards.
SirOch