Alright, pretty much my phone was fine, but it fell and now I can barely see the bottom third of my screen, I can still touch the whole screen however. Anyways since it was rooted I couldn't send it in for dead pixels. So what I ended up doing was the 1.56 RUU and I got the error 140. But since I can barely see the screen to do the downgrade through SD card I instead went up to 2.27.651.5.
Now I turned on the phone and it's as if the first time it turned on. My question now is pretty much is the phone un-rooted even though I went up in firmware and if so how do I double check?( Is it through the ADB?) And secondly, will I have to do anything else or am I good from here on out?
Which hboot & recovery were you using?
To see if your unrooted download an app from market that needs root access also I believe I read download Terminal and type the cmd su- I forgot who posted that sorry I cant give credit.
Here useful tool-- SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
or try these links they should help
http://forum.xda-developers.com/showthread.php?t=657086
http://forum.xda-developers.com/showthread.php?t=846173
There is now also an app called root checker in the market free. It works well.
Sent from my HERO200 using XDA App
Or you could finish off the screen with another fall and send it in.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Try using adb, I figure if you can't see the screen it will be hard to download from market so
cd c:/android-sdk-windows/tools
adb shell
su
if it grants superuser permission you're still rooted
My end button stopped working, so I had to do the same thing, and they never said anything when I went into sprint. They just mailed me a new hero.
Related
I have a G1 that was unlocked. I tried to install a newer custom ROM and all locked up. So I recently restored to the RC29 ROM, which I learned reflashed everything.
I have an AT&T and this thing wants me to activate the phone. I've tried plugging in my APN settings for AT&T, but it just won't go. It keeps telling me could not connect to Google etc. There is no option for wifi, so I can't activate it that way.
I feel that if I could fastboot it, I could flash it to bypass the bs activation screen. Someone please hook me up. I'd make a donation to you via paypal. I do know that there is a website to unlock it for $25. But I know there's a better way to do this.
Please assist, and I promise a donation. Thanks tons and help would be greatly appreciated as I have no means of a telephone at this point. Seriously, thanks.
Do you mean the "touch the android to begin" wizard? if so, you can bypass that by touching the four corners of the screen clockwise
all i do is tap softly top left
top right
bottom right
bottom left
tap above the emegency call line
also seems to work better if the white hand is on screen(but that might be me thinking that lol)
Click to expand...
Click to collapse
Source:http://forum.xda-developers.com/showthread.php?t=588017&page=2
That doesn't work on any g1 start up wizard much less a stock cupcake one...
so I'm guessing you don't any a recovery? That you downgraded using fastboot? If so I think your only option is adb... just download amon_ra recovery for 32b dream... push it with adb
if you do have a recovery just flash a newer rom, one that gives you the option to skip the sync at setup
-------------------------------------
Sent via the XDA Tapatalk App
That's exactly what I was thinking. I'm new to this stuff, so I may need a slight walkthrough. I have mac, so last time I did it, I just dragged and dropped the SDK tools to the terminal and was able to adb through there.
But if it's easier to do it through a PC, I'd rather do that. Anyone have a few min of time to explain? Mac or PC is good. By the way the four corner thing didn't work. ::sigh::
i believe this link should be of some help
wiki(DOT)cyanogenmod(DOT)com/index.php/G1_logon_to_google_via_wifi
Replace the (DOT)'s with .'s of course haha.
Dude. You totally made my day. After getting yelled at by a T-Mobile rep who thought he was hot ****, this really made my weekend.
The process worked great, thank you n1ckr0th.
Cheers. Happy 4th.
angasreid said:
Dude. You totally made my day. After getting yelled at by a T-Mobile rep who thought he was hot ****, this really made my weekend.
The process worked great, thank you n1ckr0th.
Cheers. Happy 4th.
Click to expand...
Click to collapse
i can't believe i never saw this post, but i'm glad to be of assistance
Hello,
I have a unlocked TMobile G1. Few days ago the phone got dropped on the hard floor and I had to pay $130 to get it's cracked LCD replaced. The phone worked fine after that until yesterday I accidentally dropped it from my computer table. This time, there's no physical damage to the screen or the phone. However, the touch stopped working and I've been getting error(android.acore process) while using the "Gmail" and the "dialer" options. Rest of things were working fine.
So, I choose to do a factory reset. Now, after restarting I am stuck on the "Touch the android to begin" screen. The touch is not working and I am not sure how to go past this screen.
Does anybody know of any keyboard short-cut or any other trick which I can use to go past this screen without touching it?
Also, anybody have any idea on what went wrong with the touch?
Thanks
Raj
Wait, are you still rooted? Use adb from your computer to remove the setup apk.
Use:
Adb remount
Adb shell rm -f /system/app/SetupWizard.apk
Sent from my HTC Vision using XDA App
Thanks for the reply. I haven't yet rooted my phone but I can look up on google and do that. Mine is T-Mobile G1 - 1.6 Firmware.
Using adb to remove the setup apk will get rid of the welcome screen or the Google set up screen which comes after that or both?
Currently, I am stuck on the welcome screen and I just need to go past this screen. Google I can set up from phone also if I can get past this screen.
Thanks
Raj
How to know if my phone is still rooted?
marcblaze27 said:
How to know if my phone is still rooted?
Click to expand...
Click to collapse
lots of ways, an easy one is download an app from the market that requires root and see if it works, actually i think there even be one that all it does is check for root.
demkantor said:
lots of ways, an easy one is download an app from the market that requires root and see if it works, actually i think there even be one that all it does is check for root.
Click to expand...
Click to collapse
ccheck the guide in my signature, it has a how-to root method and also a google by-pass method which could also be useful in your situation to get by the little guy, you need to do the google by-pass so you can enable usb debbugging(which allows you to run adb commands) then from there just delete the setupwizard.apk and so on.... but your screen may be screwed lol
*2nd EDIT*
Okay now I don't feel so dumb, I renamed the otacerts.zip thing but i am still getting reset
I did find an application that is call BN authentication service. I can't uninstall it from the normal App installer, anyways to get around this? Like ADB
*EDIT*
Ha I feel so dumb, I just needed to reboot, then change the names. So after i changed the names I rebooted again and its all good now
Thanks eyecrispy
* original*
I have a rooted nook color with a stock 1.0.1 rom, CWR, and a over clocked kernal. I have only 1 real problem, I guess besides not being able to download from the marketplace - my nook keeps on getting reset by B&N! They don't unroot it, and my recovery is still intact, but it really sucks not being able to connect to their shop. It's not that I would use their shop it's just that I accidentaly press it every now and then and it resets my device. I have to back up my device once everyday to make sure nothing gets deleted because sometimes, even when I don't press the shop button, I don't even have to press anything, it resets the device after its been connected to wi-fi for a while. Like the other day, i just set it down to go to the restroom, I come back to find it at the Android setup or the quick setup selection page. When I select Android setup when I press the little android nothing happens. When I select the B&N quick setup it, i can do that no problem. So now I just turn it off from there and load my back up through CWR.
Anyways, is there anyway to stop it from connecting to the B&N authentication service or something? I have seen people with similar problems, but no one seems to have it happen to them over and over and over again.
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
eyecrispy said:
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
Click to expand...
Click to collapse
Really? All th threads I have read people say it happened once but after a reboot it was fine. Maybe I just missed it. If you could please tell me how to disable OTA updates that would be a big help. Thanks
*EDIT*
Found what you meant, I am trying to use Root Explorer but am having no luck. I gave it superuser permissions yet it still wont let me changes any system files
Hero CDMA randomly shuts off whenever I am processing a lot of info (navigation, music, browsing, etc.)
I rooted with z4 root, and use clockwork mod through rom manager. I am using cm6 vanilla http://forum.xda-developers.com/showthread.php?t=731659 , but the same problem happens with any other rom I try.
I have done a lot of research on it and it seems that no one, so far, has a solution or a reason for it happening. Most everyone is just saying that it should be returned.
So my questions are-
1. does anyone know of a working solution?
2. If I have to return it how do I get Super User off so they don't notice it at the store? (Z4 lets me unroot, and Rom manager is easy to get off, but Ive yet to find a way for z4)
I had a similar issue with cm6 whenever I listened to music and browsed and texted all at once. Since switching to cm7 it hasn't happened. From my experience, cm7 is overclocked at 691 and cm6 is 768(approximately) I think random reboots come from our phone not being optimized to perform this well. My solution is underclock it a bit so it doesn't overheat as much. This is also a sign of needing a new phone. Our phone is amazing but with the standards of modern technology, we (Hero users) need a better phone. I'm personally waiting for the Evo 3D.
Sent from my HERO200 using Tapatalk
Yeah, try dropping your max cpu down until you quit getting reboots. Some Heroes can handle 768, some can't.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Well I have been very careful to never clock over 691, but I guess that my particular phone couldn't handle it...
So in that case, does anyone know how I can get it back to stock, mainly wothout SU on it? My several attempts never worked.
bigbird5788 said:
Well I have been very careful to never clock over 691, but I guess that my particular phone couldn't handle it...
So in that case, does anyone know how I can get it back to stock, mainly wothout SU on it? My several attempts never worked.
Click to expand...
Click to collapse
Just Run the Sprint RUU (which can be found on HTC website) from your computer and that should put your phone to the state it was before you rooted it.
Are you S-OFF? If so, you might need to find the steps for S-ON and run them, too.
Just did some research of what s-off/on is.
Edit: Wait in Hboot I see that it says S-ON
so for an RUU do I need on or off?
You can run the RUU regardless of S-off/on status. Only difference is that if you are S-off, the RUU will not restore you to S-on.
Sent from my HTC Hero CDMA using XDA Premium App
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Pull the battery fo a few and wait before a reboot?
http://www.youtube.com/watch?v=TGjBRAVZKW4&feature=youtube_gdata_player this is the issue that's happening.
Sent from my MB860 using XDA App
so you said you went in to recovery and it did nothing? So you couldn't even get recovery to load? and are you stock or rooted with clockworkmod recovery?
I can't even get it into recovery. I hold the volume keys and power buttons and it just does the boot up then black screens.
Sent from my MB860 using XDA App
Just hold down the volume down button, then hold down the power button also. Continue to hold both through the lg splash, then it should be into recovery.
Sent from my VS910 4G using XDA Premium App
isoutsider said:
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Click to expand...
Click to collapse
I had the same thing happen to mine 20 days after I got it. I had to have it replaced under the warranty, which means they had to ship it next day air.
I've heard of a few other people with the same problem.
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Unfortunately you are going to have to get a replacement from VZW. If you are within the 14 day period you can just swap it at the store. otherwise you have to go through the Warranty folks and make sure you have them ship it to you overnight.
isoutsider said:
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Click to expand...
Click to collapse
Do you have Clockwork installed?
If so, this is an easy fix.
If not, well, it's a little tougher.
The gist of what's happening is easy to find by connecting your phone while it's booting to USB and running "adb logcat" on your desktop.
That will give you the boot logs and the exact reason for what's happening.
If you're running my decrapified ROM, you may want to switch back to the stock ROM. Go to my stock NANDROID thread, download that, put it in the right folder on your SD card, then boot into clockwork and follow the instructions in the stock nandroid thread.
Make sure you clear data also!
No need to call verizon
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
isoutsider said:
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yep, having ADB access is a surefire way to get your phone up and running again.
But, just for future reference, LG has a failsafe firmware updater that will always work, no matter what state the phone is in.
It's not super easy to set up, but it will fix a phone no matter how broken the software may be.
There's a thread in the Dev subforum with the files and instructions, but the gist is that it's accessed by holding VOLUP+POWER with usb plugged in, then plugging in the battery.
It's successfully recovered 3 phones so far.
It may not be the easiest way to get the phone back, but it has a 100% success rate
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
isoutsider said:
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
Click to expand...
Click to collapse
Well... you could always try my "toggle ADB" trick.
Turn usb debugging on, then back off, then on again.
Then follow the rest of the rooting instructions, but skip the whole exploit section.
(Basically, remount /system as rw, push su, chmod su, and push superuser, and install busybox)
Ironically, the phone doesn't actually NEED any exploits at all-- it's pretty unlocked to begin with!