Database Users

I think something is missing from rooted G1

I have rooted my g1 and now all of the old features no longer work. I am running JFv1.42_RC33. I can no longer auto rotate and the on screen keyboard is no longer there. I also noticed the icons are different and that the Android logo when you power the phone on os reverted back to the old one.
What am I missing? I really just want to be able to use all of the cool features that tmobile wants to keep away from me.

why not to rename system app .bak (how I bricked my phone) - Resolved

Resolved: see post below.
Hi there, I'm really writing this hoping that maybe someone knows a fix for my problem and as a warning for why renaming system/apps with .bak is a silly idea when you can just do it via titanium or something similar.
About the device
Phone is a bell model, rooted but running the stock rom. I froze a bunch of apps with titantium (the smart way) but also added the .bak extension to some apps in the system/app folder.. I can't remember which ones but evidently important ones.
Everything was fine until today when an app I sideloaded caused my phone to go into a boot loop. I've been fighting with wakelock issues lately so I figured it wasn't a big deal to pop into the android recovery and do a factory restart. Problem is, some of the apps I added the .bak extension to are needed via the setup.
Problem I'm having
I can boot the phone fine and get to the blur setup screen which I can bypass as well. Problem is, once I skip the screen I immediately get a force close, and instead of taking me to the home screen, it goes back to the blur setup screen. I tried the keyboard shortcut bypass method which also works fine, but renders the phone useless since I can't access any menus, etc. It's just a black screen with the notification bar at the top. Horrah!
Long story short:
I can't enable usb debugging unless there is a way to sneak into the settings menu from the emergency call screen
Bell doesn't have a stock rom available
I can't re-root and fix my problem via adb because I can't turn on debug mode.
GAH!
Anyways, I'm pretty screwed. What are my choices?
I can return it to bell and hope they don't notice my giant gaff, flash an aftermarket rom and lose any warrenty I might have (I'm pretty toast now anyways) or buy a replacement phone.
Any thoughts would be greatly appreciated
- Kate

OMG
my heart had literally stopped beating for the past hour until I remember reading somewhere that you could text message a link to a replacement launcher hosted on dropbox.
OMG
Problem solved, phone is working.. I think.
Lesson for today kids: Do not mess with things you're not totally 100% sure about. Also, don't screw around with work phones. You need them to stay employed. Bricks don't keep you employed.

Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
And I have sent 2 of my atrixs back to at&t both were unlocked and rooted
No questions asked not on extra doller spent I love insurance its worth 5 dollers a month to me + my phones were both bricked by apps in the android market
that's my story and I'm sticking to it!!!
Sent from my MB860 using xda premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Does that work even if usb debugging is off? If so, that's fantastic! I'll keep that in mind next time I'm in a horrible jam.
It wasn't market apps though that was my concern though... rather it was messing with system/apps and build.prop that had me concerned. Any wise tech would know that my problems weren't caused by some error on Motorola's part, but rather a silly girl who's breaking things from within.
Thanks though

I once told the **tech repairs specialist** that I bricked my phone installing a custom rom and got asked " what kind of customer was on the phone?"
Try and find NFHimselfs atrix mods apk it will help a lot
sent from my Atrix via XDA premium

LAG since updating to 4.0.4

I just got my update to ICS 4.04 and it's made my xoom worse! Things have got really laggy, it sometimes freezes when selecting things and typing has become a nightmare again! Has anyone else experienced any problems :-(
Iam a bit annoyed now, might just go and root.
Sent from my Xoom using Tapatalk

Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks

Hmmm mine went to 4.0.4 and I was thinking the opposite! it seem alot smoother and faster

Mines seems to run slow too after the OTA, but i'm not sure if that's the tTorrent app, when it's running it makes the xoom lag out like crazy, when its off everything runs fine.

burt_ie said:
Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks
Click to expand...
Click to collapse
You could go into Developer settings and switch off animation or set to .5. That should help with lag. I never use live wallpaper either. A big download may also make it lag .

Well the lag didn't last long because I actually had a complete failure after installing 4.0.4. My Xoom went to sleep and would not wake up, had to do a soft reboot and then could not get passed the motorola boot screen, was stuck on it for hours! Tried to go into recovery to wipe and reset but that would not work either. Tried to push a rom image from my pc but then my xoom decided that it didn't want to be detected by my pc anymore so it looked like my xoom was bricked :-(
Luckily I had some help from some great people over at xoom forums who helped me to get it back up and working by using RSD Lite and a stock Rom SBF file.
I now have a working xoom updated to 4.0.4 with no problems at all
Not sure but I think it may have been a freak accident that just happened to me.... I just hope it doesn't happen to anyone else
Sent from my Xoom using Tapatalk

My Xoom went to sleep today also, couldn't get it to power up for anything, I then held power and Vol up and down all at same time and she booted right up.
Bone stock wifi Xoom by the way, incase happens to anyone else
Sent from my SCH-I500 using Tapatalk

Mine has gotten really bad with scrolling lately...
Seems that I can only scroll either up or down (or both) for no more than a couple seconds. Ive been able to move my finger up and down on a scroll area and it only lasts a couple seconds and seems to "lose" my finger press even though my finger never left the screen or the area. I have to wait a couple seconds before I can scroll again or else it doesnt recognize the finger press.

Sometimes I think the lags just android its never constantly smooth. You'd think dual core would be as smooth as butter but it really makes no difference. Still waiting for Google to fix it. I've had months of smoothness then the odd time something slows it down

I agree, 4.03 was great with no lag issues then nightly 90 had some lag again with scroll issues, so far on #91 I'm not having any issues. I had the biggest problem when I was trying the OC @1600, I slowed it back to 1408 interactive and all is smooth as glass:thumbup:
Sent from my DROIDX using Tapatalk

Turning back on

Hi Everyone, I just got my Droid 2 back after loaning it to a friend. He did a factory reset to wipe his data off and now all I need to do is activate it by dialing the number I wish to use. My problem is that I have a new phone and and I just want to be able to have it for wifi and mostly just to root and play around with the different roms. I don't know what software version is on here because its been sever months since it was in my hands.
Am I going to have to turn off my current phone to activate the D2 and then turn off so that I can turn service back on my everyday phone?
Thanks in advance for any help
Sent from my MZ604
happy to be running
Team EOS Nightlies #103
with the great support from the XDA community...Thanks!!!

No. When you turn the D2 back on just skip the activation step that has you dial *228

MissionImprobable said:
No. When you turn the D2 back on just skip the activation step that has you dial *228
Click to expand...
Click to collapse
When I turn phone on the only 2 things it allows me to do is an emergency call or touch the green droid on the screen. When I touch the green Droid it automatically dials (doesn't even show me the number) and I have no opportunity to skip entering my number. Only problem is that my only number is on my everyday phone. I hope by the additional info added someone can help me to turn phone on.
Worse case scenario is that I can deactivate my good phone then run through the activation only to turn my good phone back on. Oh well I was hoping to play around with a new rom tonight.
Sent from my MZ604
happy to be running
Team EOS Nightlies #102
with the great support from the XDA community...Thanks!!!

bypass startup
Touch the four corners of the screen
Top left
then top right
then bottom right
them bottom left
Then touch the green droid
This will bypass the auto dial

glennsardone said:
Touch the four corners of the screen
Top left
then top right
then bottom right
them bottom left
Then touch the green droid
This will bypass the auto dial
Click to expand...
Click to collapse
Thank You that worked great! All I need to do now is read a bit to figure out which way for root and which rom is best for me.
Sent from my MZ604
happy to be running
Team EOS Nightlies #103
with the great support from the XDA community...Thanks!!!

Just don't upgrade to 2.3.4 whatever you do.

hondateg91 said:
Just don't upgrade to 2.3.4 whatever you do.
Click to expand...
Click to collapse
Ok thanks for the heads up! Can you recommend a rom and or which way to root. I have only been able to read through the development section for a limited amount of time.? I am currently on 2.3.3
Thanks again
Sent from my DROID BIONIC using xda premium

If you guys are looking for a newer rom where pretty much everything works without any issues. I would suggest Miui 2.2.10 cause i have been using it for months now and its leagues better than stock. Its prerooted so no need to worry about that. You do have to sbf to stock GB and root it so you can use bootstrap to flash a custom rom. Once its flashed though you're good to go, and i have not run into a single app this rom wont run just as well as stock. After using it for some time now there is no way i would go back to a stock rom. Its a GB rom but there is also a true ICS rom on this site.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/

I will second the above poster's praise for Galnet MIUI 2.2.10. It is super stable.
As for Rooting, just use Pete's One Click Tool:
http://dl.dropbox.com/u/6643359/Software/Android/PetesMotorolaRootTools_v1.06.zip
Here's the thread if you have any issues:
forum.xda-developers.com/showthread.php?t=1258599

Hello all, hopefully someone could help a guy out. So last night I rooted my DROID 2 using Petes one click tool and it was successful. I had installed Bootstrap for D2 and then wiped data, dalvik,and cache then flashed Miui 2.2.? From sd and all looked like it was going well until the phone rebooted. When the phone came back on it now just keeps cycling through the boot animation.
Could someone please help me out I am completely clueless as what to do next.
Thanks in Advance
Sent from my DROID BIONIC using xda premium

try wiping data again
when you wipe delvik, it can take a couple of mins to boot, the first time

Word. It can actually take up to 10 minutes for a first boot.

Thanks for the help.. It took me a few but remembered how to get back to bootloader. I pulled the battery then power and volume down to get back. I wiped data, cache, and dalvik reflashed the rom and now have Miui on my D2. It did take a few minutes for the initial boot up. Since this is an extra phone I plan to setup and use it mainly as a mp3 and streaming music player for in garage/outside.
Just wanted to say thanks again!!!
Sent from my MZ604
Team EOS Nightlies #107

Down here in Aus CYANOGEN MOD9 HELP!!??

Hi all, Noob of xda here,
I've been reading the forums as a non registered user and used some of the tutorials to root my samsung android device, I'm now running ICS 4.0.4 on my GT-S5660 and running 1096mhz instead of underclocked 800mhz from the shop. I spoof my devices imei number on a regular basis due to localized phone jackings from authority figures, lets just say I like my privacy and here in aus I have the right to keep it this way. I'm an Unlimited customer for calls, sms/mms and mobile internet data access. No there is no cap on my unlimited, and as far as I'm aware I'm probably 1 of very few customers in this country that have purposely done this, because we all know it.. phone companies are ripping people off all around the world, and some of us just happen to know it all to well.
Hopefully somebody will read this topic, bcuz I need a little help with ICS 4.0.4 bugs :/ My mobile internet data usage limit is programmed to be unchecked and "hidden" therefore do NOT have red and orange data warning and data limit "lines" and cannot access the checkbox to tick it and just raise bar 999###gb, I can hard reset or recover to the base copy I custom edited *to suit my own needs* and it will reset all data counters. I got the base from cyanogen mod 9 and it appears the project was unfinished. I get data warning limit at 2gb...... I have downloaded over 450gb in the last month and have just put up with the warning in notification bar. I have several other bugs that are getting annoying.. but would be simple if i had a larger knowledge of java script and open source code or the time to learn it. I have everything working perfect except camera display auto focus on screen was incorrect or uncompleted. few other bugs with on off switching of bluetooth and wifi though 90% of time works after reboot. I have no bootscreen and on phone start from being off it will not load any picture except my SAMSUNG *which is a mainboard bios image* when it first turns on, screen hangs black bcuz screen timeout settings, I changed my screen timeout to 15seconds and now it hangs on black screen for 15s then goes into sleep mode *turning screen and button lights OFF* as soon as I push menu or power button it loads up and starts working PERFECTLY, when beforehand main settings were set to never turn off screen therefore it constantly hangs with no onscreen image display and eventually freezes entire OS bcuz it seems to think its running perfectly when its not. Lots of reports of other device noobs saying "my phone is bricked" when really you are just a noob.
Can anyone help with the bugs I have or somehow get someone to finish the project using the original projects files or similair??????
Oh and I swear to god if noobs post dumbass unrelated s**t comments on this post...

Camera issue - no idea? sorry
Data limit notifications
My wife had this issue on her phone after I flashed it (CWM, Cyanogenmod7)
Needless to say I got the blame!
I updated to the latest cyanogenmod7 nightly
Hers is a Galaxy S2 which we got here in the UK
After that update it seemed to be working ok
Appreciate that my phone is different, I guess what Im saying is, try another rom or a nightly?
Apologies if this didnt help
Good luck

elPaulio said:
Camera issue - no idea? sorry
Data limit notifications
My wife had this issue on her phone after I flashed it (CWM, Cyanogenmod7)
Needless to say I got the blame!
I updated to the latest cyanogenmod7 nightly
Hers is a Galaxy S2 which we got here in the UK
After that update it seemed to be working ok
Appreciate that my phone is different, I guess what Im saying is, try another rom or a nightly?
Apologies if this didnt help
Good luck
Click to expand...
Click to collapse
As far as I read in the forums the project on samsung galaxy gio gt-s5660 wasnt finished or mastered whatever one of the project workers stole money from account and project ended? my baseband version is S5660VXXKQ4 4.0.4 ics i dont know what other roms there are other then gingerbread n i dont like gingerbread much its what it came with preinstalled n it had heaps of annoying keyboard bugs n app crashes. Maybe there is another rom like ics that is fully operational on my gio????? i want to install rom from zip file on sd card like i did with ICS.