Upon reading the title you probably entered ready to flame me for not using the search button. The reality is though, that is just one of my many problems I'm having. I'll start from the beginning, give you the whole rundown and hopefully you can help, because if I can't figure this out soon I'm going to start smashing things, my G1 being first on the list.
A couple of days ago i was just surfing around, heard about custom ROMS, rooting, etc. so I started my journey. Thinking this would just take an afternoon, at the max, was a mistake on my part. I started here:
[ROM]TheOfficial TMO (US/EU) & HTC ADP - CRC1- Rooted [8/17/09]- v1.5.2-SecurityPatch
Looking at the prerequisites, I realized I lacked both the requirements so I followed that threads link to here:
Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
I was able to complete up to step 7, but 8 posed a problem.
When trying to sync my google account to the phone it gave that old message we all know and love from when the G1's were just released. The one where it tells you: "There is a problem communicating with the Google servers. - This could be a temporary problem or your SIM card may not be provisioned for data services. If it continues, call Customer Care."
At first, I thought maybe it was because I had horrible service in my house, ranging anywhere from 0-2 bars. Thinking I could easily fix the problem by walking up the road to get 4 bars, that's what I did. Still having trouble communicating with the servers. It's obviously not server overload like they tried to say at launch and it can't be I don't have data services because I've been paying and using them for about 9 months now. So I set off to the internet for a fix. I came across this:
[How To] Activation over Wifi
Reading the first sentence, it told me to set up ADB. So I went here:
Setting up ADB
But, I obviously couldn't complete the steps listed because I can't set my phone to debugging mode with out it being activated. So I went back to the Wifi act. page and scrolled down to find this:
[How To] Activation over Wifi (12th Post)
Following the first step, I typed <enter>reboot<enter> and nothing happened.
This, obviously, confused me very much. Because, did I not just wipe my whole phone and install rc29?
But I disregarded it, putting it to the side as a fluke and hoping the rest would work anyway, because at this point I just wanted things to start working.
I went to step 2, but once again I can't do that because I don't have access to the phone settings.
But I just continued.
Upon trying to complete step 5, I was just pissed... This seems like a never ending road. Of course, my phone had to be wrong and show up as a USB mass storage device. So I followed the steps, but I don't understand part D in step 5 because it only gives me one choice on the list which is USB mass storage device. After this I started trying everything, uninstalling that driver, turning of PnP, just about everything I could think of.
If someone could just help me, even a little, I would be so very happy.
If you need any info at all just, pictures, build info, w/e I/'ll have it to you as soon as I see your message. If you don't understand something I said, ask right away and I'll answer. Thank you so much in advance lol
Mind you, I've tried all these guides a couple times over, I've tried different guides and I've installed rc29 3 times now. Still no luck
I'm confused....
I have a few questions before we start you on the journey to getting you rooted.
Firstly, am I understanding things correctly when I assume that you have already flashed DREAIMG.nbh (RC29) onto your phone and can't get past the setup screen?
Secondly, you say that you have data service, but then say that you didn't have enough "bars" so you headed up the street for more "bars". Are you sure you have data service because the bars on the phone have to do with cell reception and have nothing to do with data service.....
Thirdly, are you on 3G or EDGE in your area?
If you do indeed have a data plan for sure, then other than a crappy 3G or EDGE signal, there really shouldn't be a reason for the error message your getting other than google's servers might actually be experiencing difficulty. No way to know for sure.
If/when you are able to get past the login screen to root, go to this link
http://forum.xda-developers.com/showthread.php?t=548924
instead of Easiest How To for: Root, Hero, Recovery, Partition (no computer), etc. READ FIRST!!
its recently updated, and easier to follow.
I have bad service...
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
KingTasty said:
Yes, after flashing RC29 onto it I can't hook my google account up to my phone. I've got EDGE in my area, checking t-mobile's service map though I found that it's really bad right where I live. Until I can head out to somewhere with some good service any ideas on how to get he wifi act. to work?
Click to expand...
Click to collapse
If you cannot get adb working properly, then you cannot use JF's method to bypass the signin screen therefore you just have to wait until you can get to a better service area.
Your two choices are: bypass the signin screen or sign in over the network. You can't sign in over the network as previously stated by you, and you cannot bypass the signin screen because you can't get adb working. There is no way to setup wifi within android if you are stuck at the signin screen
but wait?
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
KingTasty said:
There must be someway to activate ADB, because if there's not then isn't a guide activating through wifi pointless?
Click to expand...
Click to collapse
There are plenty of guides on how to get adb working... its just so happens that you reported that you can't figure it out. If you can't figure it out and get it working, then you can't use the sign in screen work around as outlined in JF's post.
The very first step in JF's work around is
You have to connect to your phone with adb shell and get root access, and then type the following command:
Click to expand...
Click to collapse
Since you can't do that, you can't do the work around. Try reading up more on adb and see if you can get it working.
Couple questions
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
OMG help me too i have the same problem !!!
KingTasty said:
I've basically fixed all the problems I was having that needed to be fixed to use ADB except for one. According to every guide I need USB Debugging enabled, My questions is how did others achieve this with being activated?
Click to expand...
Click to collapse
I know for a fact there that I saw some terminal command not too long ago to be able to activate usb debugging from the command line. I can't for the life of me remember where I saw it, but if you can be patient, I may be able to find it eventually.
florevil said:
OMG help me too i have the same problem !!!
Click to expand...
Click to collapse
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
KingTasty said:
Just keep checking back here and see where we get, hopefully we can figure it out.
@DirectMatrix:
The command is <enter>setprop persist.service.adb.enable 1<enter> and you enter it in your phone, but that only works with RC28 I think. Or does the RC29 have the hidden shell also? The reason I'm thinking it doesn't is because when I type <enter>reboot<enter> nothing happens. The only things I can think of is that I'm on the wrong screen when typing or the RC29 I'm using is messed up.
I'm on the very first screen when registering, where the it says touch the android to begin. btw, thanks for all the help so far
Click to expand...
Click to collapse
RC29 has the hidden shell also which is what allows the telnetd command to be entered to start the rooting process. It sounds like when you enter the reboot command at the welcome screen you should be getting a reboot because you said you installed RC29. It also sounds like your doing the commands in the correct spot but just to recap, you should be at the "touch the android to begin" screen, once there, just slide out the keyboard, hit enter, type reboot, hit enter again and the phone should reboot.
What happens if you keep trying to follow JF's guide even though you can't get the reboot to work? Have you made any promising progress with steps after the A few tips and tricks section?
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
KingTasty said:
I flashed it again, and reboot works now. I don't know what was wrong before. I'll try the "setprop persist.service.adb.enable 1" again. Just to be clear, after typing that nothing happens right? and I'll go check the tips and tricks.
Click to expand...
Click to collapse
Glad to hear it and yes, your right, nothing that you can see will happen. Essentially what it is doing is executing the command behind the scenes same as would happen if you were to hit the check box next to usb debugging if you were able to.
The way you will see if it worked is you should be able to open up a command prompt assuming your a windows user and type:
Code:
adb devices
You should see a device listed something like HT.........
Lemme know if you have anymore problems
Still nothing.
I tried but I don't think it worked, but it may have. The problem could be my drivers so I followed this.
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
Click to expand...
Click to collapse
I did that but every time I plug my g1 back one it makes a new one, calling it USB Mass Storage Device. I keep deleting it but it keeps coming back every time.
Here's what I got in cmd.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tyler>cd C:\android-sdk-windows-1.5_r3\tools
C:\android-sdk-windows-1.5_r3\tools>adb devices
List of devices attached
C:\android-sdk-windows-1.5_r3\tools>adb shell
error: device not found
C:\android-sdk-windows-1.5_r3\tools>
I'm not really sure what to do now... I guess I keep trying to see if it'll work. Meanwhile, what do you think?
King,
PM me your contact info and I'll try to troubleshoot this with you. I did it the old fashion way without any programs and I think I remember my steps so I just have to walk through it again.
You could also try this adb tutorial, thats the one I used and would use if I were to walk you through it.
http://forum.xda-developers.com/showthread.php?t=502010
Alright yeh, sounds good.
Gimme like 20 min, I'm gonna go grab something to eat quick.
Take a look here though, I uploaded what re appears every time I plug in my g1. Something must have been turned on or changed be cause now 3 new drivers appear every time instead of just one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But still no luck in cmd, so something is still wrong...
Hi! I have the same problem too. There're a lot of tutors online but they are just copy and paste from each others. I did pass by the first time via wifi when I root my G1 but cann't the second time rooting my girlfriend's.
The USB driver that window or HTC using before works on vista and only see the device as ADB composite deivce, but not anymore, Windows now recognized the devices as ADB composite device AND mass storage. I don't know about XP. and don't know what to do about it
I think that's why I can not enable ADB on G1 by typing "setprop....enable 1"
Anybody help? Offering your Tmo SIM card for 5 mins? I am at Dallas. Txt [email protected] #469-759-9897 Really need it PLZ
I guess this is obvious but I just want to clarify: Everytime you flash the rom you need to re-activate the phone? Or is activation only a one time requirement?
I just purchased a used, tmobile g1 (from the US) and am hoping to root it and flash SuperD's wrong as soon as I get it. However, the problem is I obviously don't have a Tmobile SIM and I don't have a data connection on my local sim card.
Do I have to go through these ADB steps to activate the phone? Thanks!
Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.
bart1822 said:
Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.
Click to expand...
Click to collapse
it seems that you lost your OS for some reason. Data recovery would be a waste of time since you already reset the phone anyway so if you didn't use an SdCard then bad luck.
If you dont wanna send you phone for repair, your best option its to ROOT and install a Verizon software yourself.
NOTE: if you had an SdCard and also got deleted, just use any data recovery program to recover most of the files
NOTE: do a bit of search about recovery programs as they might also access you phone if rooted. maybe one in Google play store?
bart1822 said:
Apologies. I posted this first in another forum, but this appears to be the correct place for it, and I think I just messed up trying to post to this forum.
Hopefully this isn't too big a question.
My phone just did this all on its own, I was just browsing the web with it. Just running whatever was on there from Verizon and HTC, not rooted or anything.
Now all I can do is get to the fastboot menu, and can do a few things there. I just tried to go to hboot then factory reset, this after trying a lot of things, and it didn't work.
It's connected to my computer, it seems to be recognized, at least by "fastboot devices" but not by "adb devices".
It shows as "***LOCKED***" and "S-ON". Everything I've found that talks about changing those requires going into the settings, setting developer mode and or usb debugging. I can't see how to do that if I can't get into the OS.
I chatted online with HTC yesterday, and they said Verizon should help. I just spoke to Verizon, and they said HTC should help. So, it looks like I get zilch from either of them. At this point I'm looking for a data recovery company, maybe someone can crack the thing open and get my photos out of it.
The irony here is that if I had rooted the phone already I likely wouldn't be in this mess. It feels like encouragement to root these devices before they inexplicably choke.
Am I screwed?
Thanks for any assistance.
Click to expand...
Click to collapse
If your primary concern is data, my guess is you would be wasting time even with recovery software, all those I have tried have successfully recovered images half black, half missing etc.
IMPORTANT: Only valid for Android 6 (Marshmallow)!
Description of problem
The lock screen functionality adds some protection against others randomly using your phone, but some people prefer to not have this function on their phone. The reason may be that it is a waste of time to have to write in the PIN/password every time the screen has been locked, plus maybe you feel that you can protect your phone well enough from others even without a password. The problem is that if you have ever activated the screen lock function by adding a password, the Honor 4x does not offer an option to revert back to not having a password. Some people on the internet suggest going to Developer settings, where there should have been an option for disabling the screen lock. But on our phone, this option is disabled (still visible in gray color).
Solution
The usual solution in such a situation is to wipe your phone and do a factory reset. I actually saw a representative for Huawei write this as a solution for this problem. But there is a much simpler and faster way. The purpose of this guide is to show you how you can easily go back to no screen lock without doing a factory reset.
We will use the program 'adb' (android debug bridge) to reset the settings. You also have to delete three files so your phone (android) no longer thinks that you have a password installed. When the password is set, these files are created and android will check for them later to find out if you have the password set, so they must be deleted.
First make sure you have adb installed and that your phone has enabled USB debugging mode in Developer settings. Connect your phone to your computer with a USB data cable and check that your computer has permissions to operate on your phone by typing:
Code:
adb devices
This should list your connected devices as a code on the left and 'device' on the right. If instead of 'device' it says 'no permissions', you have to go to Developer settings on your phone and revoke all USB debugger permissions, then disconnect and reconnect the cable. This will make a window pop up on your phone asking to give permission to USB debug mode for your computer. Click on the "don't ask again" option and then OK. Now we're all set, and can go through the required steps. Type one line at a time:
Code:
adb shell
su
settings put secure lockscreen.disabled 1
rm /data/system/locksettings.db
rm /data/system/locksettings.db-shm
rm /data/system/locksettings.db-wal
reboot
And voila. Your password protected lock screen should be removed, and you can enjoy the time saving during your day and not having to punch the code every time. If you want the password back later, just go to Settings and "Screenlock & passwords".
This solution was originally posted by user dp5l6dph5l24 in this post. I have tested this on a Honor 4x (Che2-L11), with kirin chip. If anyone has improvements to this how-to, feel free to add suggestions/improvements. Mainly it's nice to have this posted as a reference, for convenience, as in my experience this is a quite common problem.
Thanks man..this will definitely help..
Bob1900 said:
IMPORTANT: Only valid for Android 6 (Marshmallow)!
Description of problem
The lock screen functionality adds some protection against others randomly using your phone, but some people prefer to not have this function on their phone. The reason may be that it is a waste of time to have to write in the PIN/password every time the screen has been locked, plus maybe you feel that you can protect your phone well enough from others even without a password. The problem is that if you have ever activated the screen lock function by adding a password, the Honor 4x does not offer an option to revert back to not having a password. Some people on the internet suggest going to Developer settings, where there should have been an option for disabling the screen lock. But on our phone, this option is disabled (still visible in gray color).
Solution
The usual solution in such a situation is to wipe your phone and do a factory reset. I actually saw a representative for Huawei write this as a solution for this problem. But there is a much simpler and faster way. The purpose of this guide is to show you how you can easily go back to no screen lock without doing a factory reset.
We will use the program 'adb' (android debug bridge) to reset the settings. You also have to delete three files so your phone (android) no longer thinks that you have a password installed. When the password is set, these files are created and android will check for them later to find out if you have the password set, so they must be deleted.
First make sure you have adb installed and that your phone has enabled USB debugging mode in Developer settings. Connect your phone to your computer with a USB data cable and check that your computer has permissions to operate on your phone by typing:
Code:
adb devices
This should list your connected devices as a code on the left and 'device' on the right. If instead of 'device' it says 'no permissions', you have to go to Developer settings on your phone and revoke all USB debugger permissions, then disconnect and reconnect the cable. This will make a window pop up on your phone asking to give permission to USB debug mode for your computer. Click on the "don't ask again" option and then OK. Now we're all set, and can go through the required steps. Type one line at a time:
Code:
adb shell
su
settings put secure lockscreen.disabled 1
rm /data/system/locksettings.db
rm /data/system/locksettings.db-shm
rm /data/system/locksettings.db-wal
reboot
And voila. Your password protected lock screen should be removed, and you can enjoy the time saving during your day and not having to punch the code every time. If you want the password back later, just go to Settings and "Screenlock & passwords".
This solution was originally posted by user dp5l6dph5l24 in this post. I have tested this on a Honor 4x (Che2-L11), with kirin chip. If anyone has improvements to this how-to, feel free to add suggestions/improvements. Mainly it's nice to have this posted as a reference, for convenience, as in my experience this is a quite common problem.
Click to expand...
Click to collapse
Awesome script. all though it did not work for me on my Nokia G300 would you please help me find a way to get past this on the G300
I need a Lock Screen work a round....
Nokia G300 running Android 11, aoki, sm_emmc
Ive got adb and have privileges set elevated and a win 10 laptop. but i only have this laptop for a day or 2.
I will even root it if the possibility arises..
I have no access on the phone.
I can only put it in Fast Boot with no option of Factory Reset
So please help me
I have an Odyssey that currently has 57644 minutes before I can try another code combination. I would like to flash a new ROM on to it that would allow interop unlocking and let me get all the stuff I want off of it. Granted, that isn't a long time to wait to try again, but that is the tail end of a couple years of waiting. I wrote some possible codes down near to the time it got locked, but that is about all I have to go on and I'm not optimistic.
So, I connected the phone to my Windows 10 laptop and it was recognized (eventually.... had to do several soft resets of the phone). In Explorer, however, there was just an empty root directory showing up. I tried MBN_Creator but it also could not see a valid phone to flash to.
In Device Manager, I saw that only a generic (from 2006) USB/phone driver was installed. I have not been able to find a driver (Samsung or otherwise) that will install on Windows 10. I have tried a few on a WIndows 8 Pro system I have, but they also have not worked at showing any kind of file system on the phone. Is there something in the Windows Phone SDK that could be used?
I saw several references to being sure to use the original Samsung cable. I can't find that, but I tried one I did have along with borrowing a newer Samsung. The cable I have shows several folders on the borrowed Samsung (as does the cable my friend's using ... also not a Samsung cable), but neither cable works with the Odyssey.
I've tried soft resetting and power-cycling several times, but no dice.
I'm out of ideas, and would appreciate any insight you can give me.
I stumbled across a 'fix' for the huge number of minutes which was to pull the SIM and reseat it. So, I gave that a try and it came back on with 1.2 million minutes. . not the result I was hoping for.
I repeated the reseat and it was back to the 57k and change.
On the off-chance that the directories would show up, I checked and still nothing.
Once, I got the confirmation pop-up on my laptop for access to photos on the phone, but that had be finished on the phone. It seems weird that I wouldn't have been prompted for that last night, or the other times I tried this morning.
Now I'm thinking what I saw last night with my friend's phone was solely due to one being locked and the other unlocked (so, user error and ignorance). I thought I remembered seeing things when locked and connected to my old computer. I guess I must have allowed access.
From poring over the internet, it looks like what I want to do isn't possible and I'll just have to wait it out and hopefully guess right. If I'm wrong about having to wait, I'd appreciate being corrected.