Jump to content

Firestorm79

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Firestorm79

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    Orange San Diego
  1. In fact here's the full message from start of my process to finish...: Please make your decision:7 * daemon not running. starting it now on port 5037 * * daemon started successfully * ============================================= [ This script will root your Android ] [ phone with adb restore function Script ] [ by Bin4ry thanks toGoroh_kun and tkymgr ] [ for the idea Edited by Ricky wyatt for ] [ Orange San diego ] ============================================= New Rooting Your Phone Press any key to continue . . . Pushing busybox.... 3770 KB/s (1085140 bytes in 0.281s) Pushing su binary .... 2899 KB/s (23755 bytes in 0.008s) Pushing Superuser app 3973 KB/s (1468798 bytes in 0.361s) Making busybox runable ... Now unlock your device and confirm the restore operation. Please look at your device and click RESTORE! If all is successful i will tell you, if not this shell will run forever. Running ... Successful, going to reboot your device! Waiting for device to show up again.... mount: Operation not permitted mv: can't create '/system/xbin/su': Read-only file system mv: can't create '/system/app/Superuser.apk': Read-only file system cp: can't create '/system/xbin/busybox': Read-only file system Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/app/Superuser.apk: No such file or directory Unable to chmod /system/xbin/busybox: No such file or directory rm failed for /data/local.prop, No such file or directory reboot: Operation not permitted You can close all open command-prompts now! After reboot all is done! Have fun! Bin4ry Press any key to continue . . .
  2. nah not working, let me tell you guys step by step what I've done: 1) I installed any adb/superuser etc. Then ran 'San Diego' from the C drive. 2) The Tool successfully pushed adb insecure on to my phone, but then there was a one line message saying: 'run adb, click box, unplug mobile then replug usb, then press any key to continue' 3) I go into my phone apps, run adb insecure, and it gives me that stupid message about 'superuser access is needed, but could not be acquired. are you rooted and did you give permission?' 4) I ignore it and carry on by pressing any key. 5) I get the full menu and press '7', 6) the shell says pushing busybox, pushing su binary, pushing superuser app, etc I get the restore option, so I hit restore. 7) Shell says 'successful, going to reboot device! Waiting for device to show up again...' 8) THEN I GET THIS MESSAGE: mount: Operation not permitted mv: can't create '/system/xbin/su': Read-only file system mv: can't create '/system/app/Superuser.apk': Read-only file system cp: can't create '/system/xbin/busybox': Read-only file system Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/xbin/su: No such file or directory Unable to chmod /system/app/Superuser.apk: No such file or directory Unable to chmod /system/xbin/busybox: No such file or directory rm failed for /data/local.prop, No such file or directory reboot: Operation not permitted You can close all open command-prompts now! After reboot all is done! Have fun! Bin4ry Press any key to continue . . .
  3. I have adb installed but didn't know whether superuser was installed, so I just installed it from the Play store... is that the same one? by Chainsdd? The thing is when I run adb insecure it says 'superuser access is needed, but could not be acquired. are you rooted and did you give permission?' but I have the above app installed (plus it says on the shell screen that superuser is being pushed onto phone) so I don't get why adb insecure isn't working... p.s. how do you actually install adb insecure and superuser via the tool? I downloaded both from the app store...
  4. hmmm... just ran the root again (option 7), and I progressed much further than last time with v4.0.4. The shell screen actually ended saying enjoy your rooted phone etc etc... but then when I ran root checker it said my phone did not have root access?!? noooooooo. what's going on?
  5. ok ive just factory reset my phone cos i couldn't take it anymore... so I'm back to 4.0.4 - is that the one i need to be on?
  6. Yes I did! why?? p.s. what is ADB process?? [noob alert]
  7. it doesn't :( I've already posted there... can't root. and can't clear internal storage... I'm beginning to despair...
  8. thanks - I can bypass the adb bit now, but still can't root as my phone doesn't seem to restore data... it says restoring, and then it stops the restoration without the phone being rooted and the shell window still keeps running...
  9. my phone doesn't root. At the 'restore my data' stage it says 'restoration ended' and my phone screen doesn't flash or anything and the shell keeps running! please help!
  10. I have exactly this problem - can I delete/do anything to increase internal storage space on an unrooted OSD? thing is I can't root it at the moment as I need to install adbd insecure, and it won't let me install any apps as I have less than 200mb of storage space!!
  11. Hi guys, I'm getting a low on space message. My USB storage is huge, but internal storage is nearly full despite the fact that I only have 300mb worth of apps on the phone memory... the rest of the space is being taken up by data & logs... I've deleted so many apps just to make space, but it isn't even making a dent on the memory space.... please help...
  12. thanks guys. Yes it was the case. When I move it around a bit so that the light sensor is completely clear the screen wakes up! Now I have the dilema of getting a new case or sticking with it and working around this problem...
  13. Never presume too much of a nooooob thanks - I think the case is affecting the sensor (is the sensor the rounded rectabgle bit next to ear piece or the circle bit?)
  14. Hi guys, this is my first post so hello all! now for my problem... during calls the screen obviously goes dark when the phone is near my ear. however when i have to access the screen during a call for whatever purpose (either to access the number pad, or mute call, or access other apps etc) the screen either remains dark or becomes temperamental. And by temperamental I mean goes nuts: It stays dark so I go to hit my power button, but it wakes up just before I hit the power button, which means it goes dark again, which means I have to hit the power button again! Sometimes I try and second guess it and pause with my finger just hovering over the power button and then the screen wakes up! But only for a second and then it goes back to sleep!!! On the other hand it will just stay dark so I have to hit the power button. I'm worried about knackering out my power button. Now I wonder whether two factors are affecting this issue: 1. I've turned off NFC 2. I've put on a SIKAI custom made silicone case on my OSD I do hope some of you can shed some light on this problem...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.