Related
Heya,
My name is Jonatan, just received my Hero phone a few days again, been playing with it everyday since then and I want to do some more then just the basic widget installing and configuring;p.
Just rooted my phone and trying to install busybox. Never really worked much with linux based systems so was wondering if anyone could lend me a helping hand on this one. Using the steps provided on hxxp://benno.id.au/blog/2007/11/14/android-busybox I tried to install busybox, but when I do # ./busybox --install it says permission denied. Have all my partitions on rw except for the rootfs thing, not really sure what that's for.
First of all, all credits for this tutorial go to wolfilein and batemann
wolfilein's original app2sd thread - http://forum.xda-developers.com/showthread.php?t=804574
Since the other "how to" thread is a bit cluttered, I decided to tell the community how I got app2sd running on my phone flawlessly, in details.
I'm assuming that you have already rooted your x10 mini/pro and you are familiar with partitioning your SDcard, running ADB tool and root explorer.
If not, then please refer to these threads
For rooting your phone -
http://forum.xda-developers.com/showthread.php?t=739874
How to use ADB -
http://forum.xda-developers.com/showthread.php?t=502010
So lets get going -
Step 1) Create 2 partitions on your SDcard, a) Fat32 b) ext2. I used Mini Tool Partition Wizard to create partitions. Remember if you are a windows user, you need to create first partition as Fat32 and second as ext2 other wise windows will not recognize your SD card when you will connect your phone/card reader.
A detailed tutorial on how to partition your card can be found here-
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
Step 2) Download attached rar file and extract them on your SDcard root (not inside any folder)
Step 3) Open ADB Shell and type - busybox. If you see the list of busybox commands you can move to Step 5. Otherwise refer to Step 4
Step 4) If you do not have busybox installed or recognized on your system, you need to install it. I found that best way to install busybox is the manual one, so even if you mess up with busybox installation, your phone is not bricked, yet.
So to install Busybox please enter the adb shell and type su, prompt should change to # sign, confirming that you have entered rootshell successfully.
Now type :
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
Code:
cat /sdcard/busybox > /system/xbin/busybox
Code:
chmod 755 /system/xbin/busybox
Code:
/system/xbin/busybox --install -s /system/xbin/
Once you finished the installation, typing busybox from rootshell should list busybox commands. If you can not get the list of busybox commands, or get message like permission denied, or busybox not found, please confirm that you can see busybox in /system/xbin/ and the permission is set to 755. you can use root explorer for this.
Step 5) Now its time to run App2sd.sh
So from rootshell, type:
Code:
sh /sdcard/app2sd.sh
and PRAY.. Its very important to pray, because anything goes wrong here, you will end up with a PROPER bricked phone. Nah, just kidding.
Your phone should reboot itself upon finishing. and when it comes back online, app2sd should be running on your phone..
good luck.
Disclaimer: I'm not responsible for anything that happens to your phone. You take the sole responsibility of your phone, if it gets bricked, vanished or turned into cheese in the proccess.
great .. and PRAY.. LOL
I tried this procedure last week. And it went wrong cause my transcend sdhc (class 2) was faulty OMG!!!
So I bricked my phone, repaired it, and now I'm waiting another 16Gb (class10) card ... so I can brick again my phone.. ROTFL.. no no.. I'm sure this procedure is going to be ok
Thanks to titanium backup I have not lost one bit
Mate seems like a great tut, I'm just flashing my phone to follow this properly =]
P.S. what is rootshell?
Manny- said:
Mate seems like a great tut, I'm just flashing my phone to follow this properly =]
P.S. what is rootshell?
Click to expand...
Click to collapse
You enter into rootshell When you type su on adb shell. the prompt in rootshell is #.
Thanks, I thought so just making sure so anyways I'm about to try this way now will report back soon
PS. lil mistake, should be 'sh /sdcard/app2sd.sh'
PS.2 check your inbox please
IF rooted using universal androot app
1. Does this work if phone is rooted with universal and root??
2. I don't have a card reader to format the sdcard.
I formatted using the Phone itself (through usb cable), but the card didn't mount, and prompting to format it
sridharrn said:
1. Does this work if phone is rooted with universal and root??
2. I don't have a card reader to format the sdcard.
I formatted using the Phone itself (through usb cable), but the card didn't mount, and prompting to format it
Click to expand...
Click to collapse
1. Yes it will work regardless of the rooting method.
2 .Make sure that first partition of your SD card is fat32.
Thanks for a great guide!
Finally got it working on my mini pro.
Don´t know if it´s your script or my phone but it didn´t want to run for me.
When I hit "sh /sdcard/app2sd.sh" the command-window just turns to # again without doing anything.
So I ended up running all commands manually instead and that worked nicely.
Same happened with me... how did you run the commands manually?
Manny- said:
Same happened with me... how did you run the commands manually?
Click to expand...
Click to collapse
Opened the app2sd.sh-file in an text-editor, then I can see all commands listed.
Then I just Copy-And-Paste the commands line by line (Not all at once) in the command-window.
@OP
please delte this
i and batman are already working on an picture howto
i've invested many time and this and now..... yes you scribe on you post that all credist go to us but why we must have 2 threads if you so interestet to help you easy can send me an pm or write an post
@other
I woukd making a howto on monday but batman has no time so i will do it whit him tommorow
and you script doen't work if you have an sdcard malfunction
yes you made a failsafebut you don't use it in ln.sh
if you run this script without an sdcard you will brick your phone !!
and by the way please ask before you edit/use my script
you coukld write a pm
wolfilein said:
@OP
please delte this
i and batman are already working on an picture howto
i've invested many time and this and now..... yes you scribe on you post that all credist go to us but why we must have 2 threads if you so interestet to help you easy can send me an pm or write an post
@other
I woukd making a howto on monday but batman has no time so i will do it whit him tommorow
and you script doen't work if you have an sdcard malfunction
yes you made a failsafebut you don't use it in ln.sh
if you run this script without an sdcard you will brick your phone !!
and by the way please ask before you edit/use my script
you coukld write a pm
Click to expand...
Click to collapse
Mate, I only made this thread to help the community. Since this is the method I used to get a2sd running on my phone. And I did not edit/changed your script, I wrote it down, which involved my own corrections and researchs (which I contributed to your thread as well). True that ln.sh was provided by batemann, that's why I gave you two full credit.
I can not delete the thread as there are posts there, however if you claim all the rights on the method, I'll pm the moderators and ask them to merge this thread with yours.
As for helping with picture how to, I would be more than happy to help the community.
Sent from my U20i using XDA App
Manny- said:
Thanks, I thought so just making sure so anyways I'm about to try this way now will report back soon
PS. lil mistake, should be 'sh /sdcard/app2sd.sh'
PS.2 check your inbox please
Click to expand...
Click to collapse
Replied to your pm. Manny, mate tell me do you have a mini or mini pro?
Sent from my U20i using XDA App
Ive got a Mini, btw I sent you some msgs on MSN but you went offline it should still be there, I wrote the output there too.
and wolfilein, I cant get it to work from looking at your thread this just makes things easier in my eyes, and hes right it is too cluttered that thread
@OP
i don't say don't do this i only ask why you hadn't write me an pn or some other info about this ?
and btw i and batman are aktually working on the picture howto please let us time
/system/bin/shcd: not found
Everything is OK, but when I run the script returns # so i run commands manually but first command returns "not found this command"
can somebody help me please ?
thanks
SOLVED, thanks anyway
Manny- said:
Ive got a Mini, btw I sent you some msgs on MSN but you went offline it should still be there, I wrote the output there too.
and wolfilein, I cant get it to work from looking at your thread this just makes things easier in my eyes, and hes right it is too cluttered that thread
Click to expand...
Click to collapse
Mate, I checked msn, but I did not get your msg there.. I'm online now, try sending it again..
Sent from my U20i using XDA App
so I've made a picture howto so now it's verry easy even with my howto
With app2sd, can i pick where i want to install an app?
on Main memory or SD?
and what would happen if i removed my SD card when its on?
or when i plug it in to the PC to add files?
thanks!
if you use this your phone won't not boot after reoving the sdcard
but if you use the orginal howto (my) my script makes a failsafe by installing app2sd and use that,
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.)
Firstly a big thank you macexplorer who again found the relevant links amongst much Japanese.
See the original thread on rooting the F-01D:
http://forum.xda-developers.com/showthread.php?t=1611484
Following are quick instructions on how to upgrade the device to ICS. All your data will remain intact, but the /system partition is completely wiped.
NB: YOU WILL LOSE ROOT IF YOU FOLLOW THESE INSTRUCTIONS. YOU WILL NOT GET ROOT BACK.
To be clear, at the present moment in time, you need to CHOOSE BETWEEN ICS OR ROOT, you can't have both. The official upgrade below completely reflashes the system partition, so tools like OTA RootKeeper will not help you. The new release is more secure than ever and at current we don't know a new way to get root. If anyone finds any new information, please speak up
DISCLAIMER: Following these instructions might brick your device, void your warranty, etc. This is unlikely since you're basically installing an official update, but to be clear, I disclaim any and all responsibility for any (permanent) damage that might be caused by these instructions. DO AT YOUR OWN RISK.
The original instructions are here (or see in Google Translate)
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
My instructions are slightly different, aimed at more advanced users, and serves the file direct from my server (I found the original server quite picky in terms of refer and user agent, and also slow. I'm also serving the unzipped version, since compression was 0% anyways).
PRE-REQUISITES
At least 50% battery (ideally more in case things go wrong...).
Settings -> About, make sure Android version is 3.2, and Build number is either V28R43A (as recommended on the official page) or V19R36D (what I had; it worked for me but YMMV).
Settings -> Storage, at least 1.5 GB free in "Built in storage" (try installing first to external SD card and let me know if it works.. it's a lot safer).
ICS UPGRADE FOR F-01D
Download F01D_TO_SP_ICS1.enc and put it in /sdcard (md5sum: 2014d0254568a4ef955b21476012a9b5)
Boot into recovery (power off, hold down both volume keys and power up), select "update firmware" and press the power button agin.
Pay attention... the first time I tried this, it rebooted back in to recovery part way.... if this happens, just repeat step 2 above and make sure the progress bar completes all the way.
After this, it will reboot a few times, don't worry. Boot 1 will do the "optimizing android apps" screen, Boot 2 will be "upgrading calendar, contacts, etc..." and Boot 3 will say "finishing upgrade" and let you use the system.
If anyone has any leads on re-rooting the device, speak up. From my initial observations security is tighter than ever, so this might be a problem... but there are clever people out there
Regarding root
No leads for now. We can create /data/local.prop using the ICS/JB restore technique, but unfortunately the new firmware is completely ignoring either this file or the ro.kernel.qemu property.
If I understood the google translated Japanese correctly, this guy got to the same conclusion, and is now looking for other solutions. I wish him luck because after spending the day on this I have to get back to my real work
http://blog.huhka.com/2012/09/arrows-tab-lte-f-01d-icsshell-root.html
Temporary Root
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
shame on the dandroids..
Post upgrade restart errors?
Hi, slightly off-topic but related - has anyone had issues after upgrading with google maps? Whenever I start google maps it will hang and then restart my tablet.
Essentially google maps is now unusable which is very annoying. Please let me know if anyone has experienced this too and if so if they have a solution to the problem.
Many thanks in advance!
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
longdau12 said:
I lost boot after upgrade the device to ICS :crying:
anyone help me repaid boot
Thanks:laugh:
Click to expand...
Click to collapse
Help me :crying:
macexplorer said:
This link in xda works to get a temporary root:
http://forum.xda-developers.com/showthread.php?t=1886310
i think to get permanent root, need the lsm_disabler.ko for ICS kernel.
Update:
ICS kernel has blocked loading kernel modules; so cannot insmod a custom kernel.
so cannot remount /system, and cannot get permanent root..
Click to expand...
Click to collapse
FINALLY..ROOT on F-01D for V08R31A
I hope someone is still using the F-01D. So here's to you diehards.
After many many failed attempts, i finally managed to get a more permanent root.
Probably others have got this to root, but I havent seen anything come up via searches.
Main stumbling block has been in getting the address of 'ptmx_fops'. Finally got it thro, rootkitXperia_20131207.zip (get_root..this prints but fails in ptrace; ptrace is blocked in f01d)
I have just managed to get a permanent root. The steps maybe little approx. Do verify and let me know. Its non-destructive, so no harm done.
but do at your own risk..and other standard disclaimers apply
Steps:
1. do the temp root as per : http://forum.xda-developers.com/showpost.php?p=33071441&postcount=3
2. get the exploit source from https://github.com/fi01/unlock_security_module
(recursive download)
3. compile the source. this will generate a libs/armeabi/unlock_security_module binary
4. add the following recs to the device_database/device.db
these are kallsyms kern func addresses; most are avail direct from kallsyms, except for ptms_fops.
Code:
sqlite3 device_database/device.db
insert into supported_devices values(187,'F-01D','V08R31A');
insert into device_address values(187,'commit_creds',3221986012);
insert into device_address values(187,'prepare_kernel_cred',3221985196);
insert into device_address values(187,'ptmx_fops',3229222484);
insert into device_address values(187,'remap_pfn_range',3222251308);
insert into device_address values(187,'vmalloc_exec',3222293708);
5. push device.db and unlock_security_module to /data/local/tmp/
6. simply run from /data/local/tmp: ./unlock_security_module as the root obtained temp earlier.
7. after sometime, this will say LSM disabled!!
8. now remount /system as rw. carefully copy su binary to /system/xbin/ (pref use the latest version from SuperSu).
Also copy Superuser.apk to /system/app
>>carefully copy means: chown/chgrp /system/xbin/su to "0"; set perms: chmod 06755 /system/xbin/su.
9. copy busybox from /data/local/tmp to /system/xbin; and install (./busybox --install -s /system/xbin/
10. At this stage, su doesnt seem to work for newer shell connections (must do _su and then su). probably due to the exploit messing up the kernel.
11. reboot. and enjoy your newly permanent rooted status.
12. after reboot, still cannot do system remount as lsm is back to original. rerun the unlock_security_module should disable this.
maybe even move this to /system/xbin/;
But this seems to destabilise the system.
Its not possible to use a lsm disabler ko insmod. the kernel sec mech validates the module with path and hash.
So it has to be: unlock security; do your thing with /system etc., reboot.
(not sure yet if any changes to /system/buid.prop will help)
Do let me know how this works out and point out errors in the steps.
And as luck would have it there is a new ICS release out on 5-Feb.
https://www.nttdocomo.co.jp/support/utilization/product_update/list/f01d/index.html
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/data/download.html
(F01D_TO_SP_ICS2.zip)
This moves the version to V12R33B.
Do not hazard to update to this, if you want to keep this root. this release probably fixes many of the exploits.
the wifi model seems to have got 4.1..wonder is something will trickle down to f01d.
Recently I decided to try Slim Bean on my phone, seeing they released a new version a few days ago. I had been running Cyanogenmod 7 but decided it was time for a change. Initially, everything worked great, I was able to reinstall all my old apps, send texts, and things functioned well.
About 12-14 hours after doing this however, my phone stopped having signal. I didn't reboot it or anything, just no longer would it pick up a signal. Checking the about phone revealed it saying it had an unknown baseband and IMEI, I wasn't too concerned, I had backups of the EFS files, so I turned on USB debugging, plugged my computer in, and used an adb shell to move the backup to the main system. However, this still didn't work for my phone.
According to the Slimrom's FAQ, there are two solutions to this: delete the 00check and 98tweaks files in the system/etc/init.d folder, or just reinstall the ROM. However, using an adb shell or a terminal emulator on my phone, both with superuser powers, I can't remove those files. chmod spits back that they are read-only files. lsattr shows only the A tag active, which shouldn't be standing in my way. I seem powerless to get rid of these, and I can't find any guide as to how to do so. I've tried restoring to factory defaults and reinstalling the ROM, and this time I don't have signal right from the start. Can anyone help me figure out what to do about this? I've searched around and can't find any answers, which is making me think I'm just missing something really stupid. Any help would be appreciated!
Update: Figured it out. The system partition was mounted as read-only, and I thought I had tried remounting it but must have tried a higher level directory or botched the command. mount -o remount,rw /system gave me the ability to delete those files. Sorry for the trouble!