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,
Related
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.)
Today i tried to root my sgs2 applying liquidperfections method (odin & s2-root). I followed all the steps, but after flashing the secured kernel (step 11), it looks i don't have root access. SU is installed but does not react. Rootxplorer fails and Titanium backup also...
What happened? What do i do now?
Download this and flash via cwm problem will be solved
No custom count as well as no triangle
http://www.4shared.com/zip/IA_mpMSo/SU-Busybox-Installer-1.html
Cheers
Sent from my GT-I9100 using Tapatalk 2
rjsmer said:
flash via cwm problem will be solved
Click to expand...
Click to collapse
OP specifically mentioned he flashed an original kernel, therefore no CWM recovery.
@OP, I don't know why you're having that specific problem, but why not just do what most do and flash a CF-root kernel? One step instead of 11.
Re: No proper root?
Thanks for replying, but I'm pretty confused now...
I'm new to all this, and the only thing I want at the moment is rootaccess; then I'll check and learn, step by step about roms etc. - well, that was the idea.
Becaus SU and Root Exlorer were acting strange and Titanium Backup said I nedded root, I installed free app 'root checker' which says that "the device is not properly rooted" (not properly, that kind of says it is rooted, but not how it should... right??)
Another Senior member pm'd me today about it and says he will help me;
rjsmer tells me to install an apk
and oinkylicious, u, that's what I suppose, are telling me not to install that apk, becaus I have a original kernel again...
So, is there any1 that can tell me what to do exactly;
I don't have any preference for 1 specific method, but I'd like a method that is easy and not too risky...
Oinky was correct, assuming you have an I9100/T (check the sticker under the battery), CFRoot is simple & will install CWM by default which will enable you to to flash roms/kernels, backup & restore easily (among other things).
However, what you really should not do is rush it or take shortcuts. Rushing & taking shortcuts leads to borked phones & you having to pay to have said borked phone repaired/replaced.
Read the first page of the CFRoot thread thoroughly, and follow the instructions to the letter. Pay particular attention to the section a 3rd of the way down the page in bold red that says "Help ! Which file do I use". Read this bit thoroughly & understand it. If you do & then come back to this thread & ask "Hlap ! What kernel do I use ?", that means you haven't read/understood it properly & you're probably at risk of bricking your phone.
Edit - You want a method of rooting your phone that isn't risky ? There isn't one. Flashing stuff to your phone always entails (a normally very small) risk you'll brick your phone. That risk increases exponentially with how poorly you understand what it is you're doing to your phone (gets back to the no rushing/no shortcuts, following instructions & understanding what you're doing I mentioned above).
Narcotrix said:
Thanks for replying, but I'm pretty confused now...
I'm new to all this, and the only thing I want at the moment is rootaccess; then I'll check and learn, step by step about roms etc. - well, that was the idea.
Becaus SU and Root Exlorer were acting strange and Titanium Backup said I nedded root, I installed free app 'root checker' which says that "the device is not properly rooted" (not properly, that kind of says it is rooted, but not how it should... right??)
Another Senior member pm'd me today about it and says he will help me;
rjsmer tells me to install an apk
and oinkylicious, u, that's what I suppose, are telling me not to install that apk, becaus I have a original kernel again...
So, is there any1 that can tell me what to do exactly;
I don't have any preference for 1 specific method, but I'd like a method that is easy and not too risky...
Click to expand...
Click to collapse
What I would do is
1. Flash stock firmware
2. Flash insecure kernel (CF-Root)
3. Check for root
Root will be there and just a case of progressing to custom roms etc
No proper Root
OK, thanks for the info
I don't want to rush anything, and I did inform me well. But for what I understand, is that I did everything alright yesterday, except re-flashing the stock/secured kernel (an optional step...)
Basically, if I apply the CF-Root method, I'll have a unsecured kernel?
So, what do I do now ?
Completely reset my phone, and apply CF-root ?
I think reset, because I have SU on my ophone now...
- Do I reset the gs2 or leave it & apply CF-Root?
- What is strange is that no one can tell me why this happened or what the problem is exactly ?
CF-Root
MistahBungle said:
Oinky was correct, assuming you have an I9100/T (check the sticker under the battery), CFRoot is simple & will install CWM by default which will enable you to to flash roms/kernels, backup & restore easily (among other things).
However, what you really should not do is rush it or take shortcuts. Rushing & taking shortcuts leads to borked phones & you having to pay to have said borked phone repaired/replaced.
Read the first page of the CFRoot thread thoroughly, and follow the instructions to the letter. Pay particular attention to the section a 3rd of the way down the page in bold red that says "Help ! Which file do I use". Read this bit thoroughly & understand it. If you do & then come back to this thread & ask "Hlap ! What kernel do I use ?", that means you haven't read/understood it properly & you're probably at risk of bricking your phone.
Edit - You want a method of rooting your phone that isn't risky ? There isn't one. Flashing stuff to your phone always entails (a normally very small) risk you'll brick your phone. That risk increases exponentially with how poorly you understand what it is you're doing to your phone (gets back to the no rushing/no shortcuts, following instructions & understanding what you're doing I mentioned above).
Click to expand...
Click to collapse
Actually, my phone is a GT-I9100, no letter at the end...
And, I do know that flashing is risky, and I agree that it the less I know, the more it becomes risky, but, hey, I'm willing to understand and learn...
Anyway, my other contact send me this to flash ? What do you think ?
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5
That does not match my current firmware (XWLP4), does it ?
So, I did read page 1 of Chainfire's thread, and I think I have to go for the CF-Root-SGS2_XW_O2U_LP3-v5.4-CWM5 one...
So, once my phone is flashed with this one, what are the possibilities / opportunities, except installing apps that require root ?
Are there any guides or threads to introduce new people to this ?
I have no idea if the LPS kernel your 'contact' sent you will work or not. At worst your phone won't boot (you'll still be able to get into download mode & flash something else). As to what kernel you should use, all the info you need is in that section 'Help ! Which file do I use ?' which is why I drew attention to it. If you're apprehensive or unsure of what you're doing, don't until you are sure.
What are the possibilities/opportunities once you've rooted your phone ? Basically it gives you control over your phone. You can freeze or uninstall apps that carriers/Samsung have put on the phone for starters. And obviously if you use CFRoot to root your phone, you'll have CWM installed which makes flashing roms/kernels, backing up & restoring really easy (among other things).
As I said in another thread all of 5 minutes ago, I very much recommend you read the Stickies, just about everything you could ever want to know is in those threads. You just have to read & learn.
Edit - Re: your question 'What is strange is that no one can tell me why this happened or what the problem is exactly ?' in your earlier post, the reason for this (root failing) is we don't know. We're not there with you to know exactly what you did/didn't do, and besides, the method you used isn't from this site.
Well, thx a lot for tips and explicarions!
I'm still informing myself...
I'd go 4 cf-root, but still hesitating becoz my device looks "semi"-rooted, but is that possible? Some apps are 'seeing' root, but can't have access to it...
Oh and the method i did use initially comes from this forum, really. Thread by user LiquidPerfection...
Sent from my GT-I9100 using xda app-developers app
Edit:
These are the results of the root checker-tool. Can some1 please explain or tell me what to do mow? Thank u
Superuser Application Status:
Superuser application - version 3.1.3 -is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: No such file or directory
Analysis: File /sbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root shell 22228 2011-09-27 23:12 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your GT-I9100 device by Root Checker Pro version 1.2.7 from joeykrim in the Android Market - http://goo.gl/NcnHn
Hi XDA Community,
Your forums have helped me in the past and I spent some time scouring the posts before posting this one as I couldn't find anything that was specific to my issue. Since this is my first post, I thought that I would save a ping pong of responses, by being fairly expansive on what the problem is and what I have tried; thus hoping to pinpoint my issue a little quicker.
Device Details:
---------------------
Model Number: GT-I9100
Android Version: 4.0.3
Kernel Version: [email protected] #3
Build Number: IML74K.XWLP3
ROM Firmware: Samsung-Updates.com-GT-I9100_O2U_1_20120326173406_jiut50pyip.zip (via Samsung Kies)
Rooting Method / Kernel: Odin3v185 / CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Summary
--------------
Since the beginning of July 2012, I successfully upgraded from Gingerbread v2.3.6 to ICS v4.0.3 using Samsung Kies then initiated root privileges by using the CF-Root Kernel via Odin (versions shown above) - All has been working fine 100%.....
However, it appears that I seem to have lost my SU permissions and may have disabled my root access, even though my device was rooted and I would appreciate any assistance from anyone who might have time to shed some light on the situation.
Behaviour of Apps I have tried that require root
-------------------------------------------------------------------
SuperSU
SuperSU Pro v0.96 lists in the 'Apps' tab (denoted by a green # symbol) that I have granted all relevant Apps that require SU privileges. This includes AdFree, BusyBox Pro, Root Checker Basic, Root Explorer, SetCPU, Terminal Emulator, Titanium Backup, Triangle Away.
Terminal Emulator
Terminal Emulator displays the following and when I enter the su command at the prompt, I just see a carriage return with a grey block. In other words, I do not see the # symbol denoting I have su privileges.
a/local/bin:$PATH
[email protected]:/ $su
Root Explorer
Root Explorer no longer displays a directory listing and simply displays a pop up from SuperSU after tapping on Root Explorer, "Root Explorer has been granted superuser permission for an interactive shell." then the following message from Root Explorer itself:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on."
Root Checker Basic
Apart from the App stating "Please wait for Root Check to be complete. Systems appears to be running very slow" after tapping on the [Verify Root Access] button. It never seems to provide an output after a few minutes waiting. My conclusion is that it cannot get su permissions.
BusyBox Pro
SuperSU displays the message that Titanium Backup has been given root access, however I get the following message:
"Asking for root rights..."
Then after a few minutes I receive this most enlightening output:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox and try again.
This attempt was made using the "/system/xbin/su" command."
I read somewhere that Titanium Backup uses it's own BusyBox installation and not the system wide BusyBox package so I went in to the Titanium Backup preferences and selected 'Troubleshooting settings' then chose 'Force system BusyBox' to see if my issue was a BusyBox specific problem. Again, it failed so not sure if it is BusyBox or my SU permissions that have somehow got corrupted or been disabled.
Additional Information
-------------------------------
Using 'ES File Explorer', I can confirm that the following file's exist at the appropriate location paths:
/system/xbin/su
/system/xbin/busybox
Conclusion so far
-------------------------
It appears that on the face of it that I have lost my root permissions, so I removed apps from SuperSU, then uninstalled the App (e.g. Root Explorer, Terminal Emulator et al.); then performed the rooting procedure again via ODIN and the CF-Root kernel. The process itself worked flawlessly and so after it rebooted, I installed the Apps in question from the Google Play Store again and they prompted to be granted SuperSU privileges. Unfortunately, the same issues arose where it appears that it cannot communicate with either the su command or BusyBox to do what it requires.
Does anyone have any ideas as the phone is fine apart from this and although performing a Titanium Backup backup around two weeks ago, I would sooner not have to wipe everything if I can help it. I wonder if it is an update that somehow confused things...Either way, I cannot use Titanium Backup to backup/restore due to it requiring SU/root permissions, of which I do not seemingly have anymore.
Any ideas please as I am scratching my head and have gone blurry eyed at spending hours viewing various forums and posts?
follow this steps:
1. Unroot your phone with the unroot method here
2. To be sure, unroot again with the method here
3. ROOT your phone again using Any of the Rooting methods in the links provided in step 1 or 2.
Good luck
ICS 4.0.3 Lost su permissions even though device was rooted - Resolved
:good: Issue Resolved :good:
Many thanks for contributing to my issue. I had come across the post before in your links and although the directions were not completely related, there was a section pertaining to a zip file that I must have missed.
Conclusion
----------------
As can be read in the post, I was unsure if my issue related to losing root, a possible corrupt su file itself or BusyBox. As you will see on the link below, Busy Box actually creates hundreds of symbolic links (symlinks) and due to my perhaps overzelous approach to wanting a quick fix; I must have inadvertently created too many links with different versions of Busy Box and therefore when an App that was correctly added and granted SU permissions within SuperSU, when it then communicated with Busy Box / su to authenticate; I can only imagine it got confused and was lost with all the dead symlinks. The net result was that although SuperSU stated that it had granted permissions to the Apps requiring root, it never got to communicate with the su file contained within /system/xbin. I hope that makes sense, well at least I am pretty sure that is what happened.
Solution
------------
Firstly, I cleared all entries contained within SuperSU and therefore removing all Apps from being granted with root access (they didn't have it anyway at the moment).
I saved the zip file contained at the following link on to my external SD card and choosing to 'install zip from sd card' within the CWM Recovery (Volume Up + Power + Home button); effectively this uninstalls Busy Box completely from your device, including hundreds of symlink files - including many which in my instance was causing issues with Apps that required root to function correctly.
Busy Box Uninstaller v1.0 here
I restarted my device and downloaded Busy Box from Google Play Store and when I opened Root Explorer and the other aforementioned Apps shown in this post, they prompted to be granted root permissions (SuperSU) and voila....it worked ! :good:
I hope this may help other droid users experiencing similar symptoms.
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.
Like everyone else, I picked this Azpen A743 up at Microcenter for $20. It was advertised as having 5.1, but came with 6.0.1. I bought it to stream music from my Asus router with samba share drive. Other than that, just plan to use Google News, weather app, and light web browsing. Tried a couple rooting methods but no luck. Reluctantly tried Kingo Root, but it never finished the process. (I've read these devices come preloaded with malware, so some more from kingo root won't hurt). From what I've read and searched, there isn't any custom recovery for this tablet. Anyone know how to root it? I did manage from stock recovery to sideload SuperUser.apk, but it doesn't work.
I have USB debugging on, and bootloader unlocked.
Specs are: Allwinner 1.3 GHz A33 4core
The recovery lists the tablet as:
A33_86v/astar_xr819/astar-xr819
6.0.1/MOB30R/20171221
and firmware version v6.0rc3 (I have found references to OxygenOS for that FW version)
If there is not a root method, is there a way to alter/replace the hosts file? I would like to transfer the hosts file from my phone generated by adaway. I have copied my phone's hosts file and tried:
adb reboot download - reboots to OS, doen't seem to have a download mode, but it would almost have to in order to update the FW
adb reboot bootloader - boots to Azpen screen buring bootup, but just hangs
adb push - system read only
adb shell - cp hosts (read only)
adb shell, then su - SuperUser pops up saying ADB need SU access, grant it but nothing happens. can type, but nothing happens.
from recovery, if I mount /system, then device no longer detected by adb.
Didn't try any fastboot commands, scared of losing data, and I don't see anyway to back up the current FW
Also tried the Phoneixsuit software to install apks, but it didn't work
created my own update.zip - 255 error (or not verified even when using various methods to sign the .zip file-Sign-em, Auto-Sign)
Is there a way to create a .zip or apk that is signed that will copy the hosts file to /etc/hosts?
Any advice or guidance would be appreciated.
Have you had any luck since posting this? I'm trying to root the same device, but no luck so far.
Nope. Somehow managed to push Superuser to it, but still not rooted. SU app pops up asking for SU if "adb shell SU", can grant permission, but still nothing. Can't make permission changes to RW. I finally got fed up and tried flashing the wrong firmware to it, but even that wouldn't work. PhoenixSuit, PhoenixProUSB, PhoenixCard would not work to flash different firmware... and no response from Azpen about lollipop firmware or any firmware for that matter. Won't return emails or answer the phone.
I don't know if by pulling the /system folder ,making changes, then using a tool like Dragonface to build a prerooted image would work or not. Can't really do anything without the right firmware for the device.... and I'm not counting on that happening.
This is a good place for info on A33 info and tools:
http://forum.gsmhosting.com/vbb/f906/
I finally got widgets to update after a month of tinkering.... everyday it tells me the SD card is corrupt... other than all of the above, it is a decent little tablet for the $20.