[Q] I9000T stuck during boot, can't get root - Galaxy S I9000 Q&A, Help & Troubleshooting

I used z4root's temporary root and enabled RyanZA's OCLF but the phone never booted again (stuck at Galaxy S logo, after my carrier's logo.)
"adb logcat" shows that pretty much everything in /data is missing.
I can't get root to investigate much further. I installed update.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=728754
which gave me su and busybox, but su just reports "Permission denied" and logcat shows
E/su ( 3315): stat failed with 20: Not a directory
W/su ( 3315): request rejected (2000->0 /system/bin/sh)
(in recovery mode, the stat fails with 2: No such file or directory instead). "su -s /system/xbin/busybox" fails in the same way.
I have /system/app/Superuser.apk, but given that nothing is really running due to the state of /data I don't think that helps. I can't see what's in /data due to not having root though.
any suggestions?

ok I have unfucked the phone. I couldn't get RageAgainstTheCage to run (never got a root shell), but the newer KillingInTheNameOf worked.
In /data I found that the lag fix had renamed data, system, app, app-private, dalvik-cache with .old suffixes. The ext2 volume was there but nothing was mounting it on boot. The directories had been replaced with files just containing the text "stump".
For now I nuked the files, renamed the .old directories back to what they should've been, and the phone is working again. (Still no lagfix though.)

Related

Permissions /system/csc/

I have downgraded from JPK to JM8. When recovery runs I get an errormessage about "can not access /system/csc", not exact words but I think I've understood it right. I have checked it with ADB and I have permissions set to "drwxr-xr-x root root csc" and in /system/csc I have "-rw-r--r-- root root" on all files. It seems a little strange that my permissions are set to that in the folder. Are those permissions correct?
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Ok. Will do that. I'm looking for a reason to why I can't flash docs rommod onto my phone. I can't get any further than to the S on black background hearing bootsound but the phone doesn't boot up to a ui. Thought the message could be a clue to that problem
did you do a factory reset in recovery?
When do I have to do that factory reset? I have tried to do it after the slimmod flash. Should I do it before flashing the mod? Now I have oclf installed. Do I have to remove it before trying again?
I have done a clean install of JM8. Installed OCLF, rooted, installed RomManager and clockworkmod recovery. Pushed extreme superslim to internal sdcard. Rebooted into recovery. Did a factory reset and wipe of cache. Installed zip from sdcard. ONLY DIFFERENCE IS THAT MY CLOCK SHOWES TWO HOURS TO EARLY. What am I doing wrong?
Install fresh jm8 push docs update.zip to sdcard and apply it. Then install those rest...
Sent from my GT-I9000 using XDA App
At last! After to more resets and flashes I have Extreme Slim on my device and I really likes it. Big applause to doc. Happy HTC:ing.
mickeko said:
It's not related to JPK at all. JM8 expects multi-CSC and the XEE CSC is not. There is no problems at all connected to that error, so you can safely ignore it.
If you're like me though, and hate to see it, there's a really easy way to make it go away. Create the following 2 directories (root required):
/system/csc/XEE
/system/csc/XEE/system
Simple as that.
Click to expand...
Click to collapse
I noticed with this you had to change the permissions for these foders using a program such as root explorer. Tick all boxes. Well, that's the only way I got rid of the error.
Also case sensative..
/system is usually mounted a read-only, you have to remount it like this from terminal emulator (rooted of course)
$ su
$ mount -o remount,rw /system
then run
$ mount
you should see /system mounted as 'rw'

Help Please - Hangs on powerup

My SGS shows the boot up screen/noise, then just sits on a black screen and vibrates occasionally
I'm able to press the 3-buttons and boot up into ClockworkMod Recovery, however nothing seems to fix it. I've tried applying update.zip, wiping cache, factory reset, loading the restore-update.zip, and "restore" to the only checkpoint, but nothing works.
I screwed up when installing a theme, these were the first part of the directions:
1. adb shell
2. su (grant su rights on your phone when asked)
3. mount -o rw,remount /dev/block/mtdblock3 /system
3. rm system/framework/twframework-res.apk
4. rm system/framework/framework-res.apk
5. rm system/app/settings.apk (if no file is found try Settings.apk ... no ide if it matters tho)
Click to expand...
Click to collapse
I got this far, then realized that the files I needed to replace those with were on the internal SD, but IN A ZIP. So I couldn't use them. RMing the old ones meant nothing worked anymore.
Now my phone is in debug mode, can't seem to get su access (although I can use adb to a limited extent), and I can't get it to work
Any help for me?
I have3 the same problem Have you found out how to fix it?
Looks like your going to have to use odin to reflash ive had this many atime from unsuccesful modding and always worked.

[Q] /: files lost on reboot?

My phone has been "broken" for the past 7 days, and I'm having troubles uploading any factoryfs.rfs containing the stock /app and /media folders.
A possible workaround would be flashing as much as needed(sh executable; ls, mv etc) to be able to push the rest through adb.
Pushing the /media folder seemed to be working at first. Here's the issue: when I reboot and execute ls trough adb the /media folder is missing.
I also tried replacing the push command with "mkdir test.d". That folder was also lost on reboot.
When creating the "test.d"-folder in /mnt/sdcard it stayed.
Any suggestions are appreciated.
Another quick question that's too simple to find by googling: does your ClockWorkMod show the option to mount /system at recovery boot? I'm a bit worried since mine does. It could be related to the topic.

cannot root S5830

Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
simmo2302 said:
Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
Click to expand...
Click to collapse
If your phone is unlocked try to flash a fresh stock rom via Odin, maybe you don't have enought free space in your system patition
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
simmo2302 said:
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
Click to expand...
Click to collapse
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
simmo2302 said:
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
Click to expand...
Click to collapse
Do you have thinkdroid installed?
Viper The Ripper said:
Do you have thinkdroid installed?
Click to expand...
Click to collapse
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
simmo2302 said:
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
Click to expand...
Click to collapse
I'd tell you that if you didn't have enough space on the system partition, maybe you could try flashing THIS before rooting your device and then you'll try flashing root again so...
Try The Ultimatum
Sent From my GT-S5830.
Current Rom-The Ultimatum
Kernel-Fire OC Kernel
Audio Manager-BEATS
Hit Thanks you unthankful $*%$&. Its There For A Reason.
Samsung Galaxy Ace [GT-S5830] root method (Optus branded units and possibly others)
I tried many methods, and none would work with my Optus branded S5830. I assume it was partly due to having less than 1MB available on the /system partition. After some perseverance, it now has root, here was my method, hopefully it can help others.
Some files mentioned in this are available here: http://goo.gl/6XlwEx
1. Install Samsung USB drivers: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
2. Install and setup (for atleast your android version) the SDK from Google (http://developer.android.com/sdk/index.html)
3. Ensure that the platform-tools (or which ever folder contains adb.exe) is in your system path variable (google it).
4. Put custom recovery image on sdcard: recovery-clockwork-5.0.2.6-galaxyace.zip
5. Turn off device, and boot to recovery (home + power)
6. Flash recovery-clockwork-5.0.2.6-galaxyace.zip and reboot
7. Turn off device, and boot to recovery again (home + power)
8. From a command prompt, run 'adb shell' it should drop you to a shell with root privileges (#).
Code:
> adb shell
#
9. Mount the '/system' partition from the custom recovery (mount partitions)
10. Make some room on your '/system' partition, delete Skype, Think Office, etc. You will need to do this as the bloatware has left no room for the su binary and SuperUser.apk
11. To get rid of skype or Think Office, from the command line type the following and then press enter.
Code:
# rm /system/app/Skype.apk
# rm /system/app/thinkdroid.apk
12. Extract universal_gb_root_v25.zip to a folder, and open another command prompt at .\universal_gb_root_v25\system\xbin and type the following commands:
Code:
> adb push busybox /system/xbin/
> adb push sqlite3 /system/xbin/
> adb push ssh /system/xbin/
> adb push su /system/xbin/
> adb push ..\app\Rootvalidator.apk /system/app/
> adb push ..\app\Supersu.apk /system/app/
13. Go Back to you 'adb shell' command prompt, and type the following to confirm the files have been pushed (you should not get a 'No such file or directory' message)
Code:
# ls /system/xbin/su
# ls /system/app/Supersu.apk
14. Set file access permissions (change mode) with the chmod command
Code:
# cd /system/xbin
# chmod 6755 su
# chmod 755 busybox
# chmod 755 sqlite3
# chmod 755 ssh
# chmod 644 /system/app/Supersu.apk
15. Now also copy the files you pushed to /system/xbin to /system/bin
Code:
# cp su /system/bin/
# cp ssh /system/bin/
# cp busybox /system/bin/
# cp sqlite3 /system/bin/
Code:
# reboot
The phone should reboot as normal,
17. Once in turn on USB debugging (google it). Go Back to you 'adb shell' command prompt (which will have quit the shell after the reboot) and type:
Code:
> adb shell
$
18. Note that this time there is likely a $ prompt, if so, enter the command 'su' and hit enter. SuperSU should pop up on your device asking for su rights, say yes. If you get the # prompt, you are now rooted.
Code:
$ su
#
19. As an alternative to steps 17 and 18, (after the reboot, before turning on USB debugging), you can just open Rootvalidator from your app drawer to test for root privileges. You will also notice the SuperSU and cwm_recovery apps now in the app drawer too.
If it hasn't worked, make sure you've followed the steps correctly, you can safely repeat them, or play with the file's (busybox, sqlite3, ssh and su) user owner/group owners so they match most of the the other files in '/system/bin' and see if it helps. USe 'ls -l', 'chown' and 'chgrp' (again, google their usage)
ie. as an example, below shows that 'busybox' is owned by user 'root' and group 'shell', to change the group ownership to root, i would type 'chgrp root busybox' at a root (#) prompt.
Code:
# ls -l
-rwxr-xr-x root shell 2007456 2008-08-01 22:00 busybox
-rwsr-sr-x root root 311872 2013-12-08 09:09 su
- The End -
I think you should you should flash a stock rom via odin.

Hard reset says rootedl; application says not rooted; stock recovery red escalmation

Exactly what it says title. My phone is both I think rooted and unrooted.
I tried all the possible rooting methods, none of it are working. Only thing worked was unbricking the phone. Right now on stock 4.4.2.
Trying to use ioroot25 but phone get stuck when it does adb recovery reboot. Dead android with red escalation mark.
Kingroot total failure.
Ran I think ioroot5?; \
Code:
Mounting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to open /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
3671 KB/s (1468798 bytes in 0.390s)
pkg: /data/local/tmp/superuser.apk
What should I do
GUYS I need help. I just did a fresh install of stock VS980 23A. the custom recovery still has showing me a red mark. But this time in fastboot, it shows UNROOTED Before it showed rooted
Does this mean my phone was 'half rooted?
Ok, I have honestly hit the wall. I don't know what way out.
Only way out I thought was if I could push the TWRP files via adb i could fix it to bypass the restrictions but I can't. When I try pushing loki_tool and twrp.img via adb using ioroot folder, I get "permission denied".
I can't access the stock recovery because from the Googling I did, the stock recovery is corrupted and requires custom recovery. How the hell can I get custom recovery in if I can't even access the adb root permission.
Yes I tried the 'su' in adb method, it doesn't even recognize the command.
Going to google if I can install TWRP/custom recovery for lg g2 vs980 using download mode.
Victory! All those lame ass tools, loki_tool, lg_one_click_root, iorootv25-1-2-3-5 version. None worked!!
But this bad boy did it! -> http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906

Categories

Resources