The flex cable inside my g1 broke and so i replaced it. prior to this it worked perfectly. However, now it is not picking up any sim card whatsoever - i have factory reset it and it is locked ot t-mobile. I have tried a friends T-mobile sim and this did not work, i also tried a "giffgaff" sim, checking to see if it would detect it, still nothing.
I've been following this guide:
http://forum.xda-developers.com/showthread.php?t=452316
And cannot figure out how to get past:
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
How do i give busybox permissions :S?
Nevermind, got it. Used http://blog.vgod.tw/tutorial-activate-g1-via-wifi-without-a-sim-card/ as well to figure it out, this was posted deeper down in the thread posted before.
Related
Ok i have an g1 thats unregistered and i kow how to activate it through wifi but i cant because i dont have an router i was wonder if someone could explain to me how to bypass this without activating my g1 it said or how i send these commands with adb
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together
but i am so confused thanks for the help
Do you have root? Most custom ROMs give you an option to skip.
i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated
charles20212 said:
i was in the process of rooting my g1 when i had downgraded it but i couldnt finish it because i had to activate it when i got it it was already activated
Click to expand...
Click to collapse
It's been so long since I rooted that I can't remember if there are any other options. I think when first I got mine, there was no way to root with wifi. I couldn't even register while roaming, and had to drive 40 miles (nearest T-Mo tower) just to use my G1 for the first time. That sucked!
is there a way to bypass it without using wifi or can i install a new rom or something
If you are rooted, then try a new rom. Most of them will have the option to skip.
how i know if im rooted
Im trying to activate my g1 without a sim card and using the guide at
http://forum.xda-developers.com/showthread.php?t=452316
when i get to the step about busybox im stuck.. i get into adb push busy box, go into adb shell, set the permissions, try to telnet and then it say busy box permission denied
I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.
Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.
----wrong----
Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."
One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!
So I followed this guide to root my phone:
http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
Which worked. After that I decided I wanted a bash shell for my phone so I followed this guide:
http://forum.xda-developers.com/showthread.php?t=727566
I couldn't use adb remount because it gave me permission denied so I decided to use:
Code:
adb shell
su
mount -o rw,remount /system
And then I followed it up with the commands in the guide.
When I exited out of the adb shell I couldn't adb shell into it anymore.
It's giving me the following error:
Code:
- exec '/system/bin/sh' failed: Permission denied (13) -
This is likely because in the guide you replace the default /system/bin/sh with the bash version.
And in the guide it doesn't tell you to chmod it. I think this is where the problem lies.
Then I thought maybe I could open up a shell inside my phone with a terminal emulator.
However the shell crashes and closes automatically.
Then I thought maybe I could use a file explorer to change sh.old back to the normal sh.
Unluckily I haven't yet given root permission to my file explorer so I couldn't.
I noticed that my root also got broken when I checked whether I was still rooted.
So I tryed re-rooting it with iRoot which didn't work.
Any idea on how I could fix this problem?
I still have adb access but I can't use any kind of shell not on the phone nor using adb.
EDIT: because of this I am now unable to change my EMUI theme, I also can't connect to wifi anymore.
Also, I tried a factory reset which didn't work...
EDIT: okay so I've made a backup of my current ROM through TWRP and now I am attempting to install the stock firmware of B133SP01 through local update.
After that I'm going to locally update to B602 and B609 again. Hopefully that will fix it...
EDIT: Seems like I can't install the stock firmware it's giving me an error message saying that it failed. And yes I have flashed my recovery back to stock B609. I suppose this has something to do with sh not working correctly...
Have I screwed myself for life?
I'm still hoping that someone can come in and help me fix it. If not I might be doomed.