Hello,
I've had a rooted t-mobile g1 and mt3g for many months now without any problems, except one. My mytouch was really slow when trying to bring my home screen up, it would stay black for 1-2 min until the home screen would finally show up. I knew it wasn't right, because my g1 acted quite normal.
To fix this, I re rooted my device by installing drc83 base defanged.zip from the boot screen, then installed cyanogen 4.2.1.14.1. After both files were installed, I rebooted the device.
The real problem: now my phone is quite snappy, but I cannot open any google apps like market, gmail, and sync. I have searched the web, and posted elsewhere, but no help.
Please help!!
Thanks in advance.
-Blake
I forgot to mention, my device also reboots by itself now, like 3 times a day.
pkssauce said:
Hello,
I've had a rooted t-mobile g1 and mt3g for many months now without any problems, except one. My mytouch was really slow when trying to bring my home screen up, it would stay black for 1-2 min until the home screen would finally show up. I knew it wasn't right, because my g1 acted quite normal.
To fix this, I re rooted my device by installing drc83 base defanged.zip from the boot screen, then installed cyanogen 4.2.1.14.1. After both files were installed, I rebooted the device.
The real problem: now my phone is quite snappy, but I cannot open any google apps like market, gmail, and sync. I have searched the web, and posted elsewhere, but no help.
Please help!!
Thanks in advance.
-Blake
I forgot to mention, my device also reboots by itself now, like 3 times a day.
Click to expand...
Click to collapse
unroot your device, root it with the latest amon ra recovery for the MT3G. Use the recovery image to format your sd card to your liking. Then just enable usb in the recovery image and drag over the defang base and the latest cyanogen. just flash then both (first the base then cyanogen) without wiping. Change your ext2 into ext3 (not ext4 since some ROMs don't support it yet).
Also for your sd card I recommend at least 96 mb swap and a 512 ext3 partition.
Related
First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.
I bought the Gtablet yesterday and immediatley took it home to Install a Custom Rom.. I installed clockwork recovery, and then installed the cyanogen 6.1 beta 4..everything installed correctly and it rebooted, however it did not have the marketplace or flash support, and would not autorotate with the device smoothly, so I thought I might try a different ROM but when trying to access my device VIA usb it closes quickly and will not allow access .. also I am having issues with the SD card, I can mount USB in Clockwork and copied over Vegan 5.1...it said it installed succesfully but when it launches it still says cyanogen, but says vegan in the "about phone" section this did give me a few more icons including marketplace..but it launches and then has a white screen.then closes automatically...I am afraid I have really messed something up here...any help would be greatly appreciated ...I would like to move forward with a Custom ROM and right now I dont care which one as long as it works...
issues
1. no USB connectivity
2. Marketplace and Flash issues
3. mixed ROMS?!??!?
Jland said:
I bought the Gtablet yesterday and immediatley took it home to Install a Custom Rom.. I installed clockwork recovery, and then installed the cyanogen 6.1 beta 4..everything installed correctly and it rebooted, however it did not have the marketplace or flash support, and would not autorotate with the device smoothly, so I thought I might try a different ROM but when trying to access my device VIA usb it closes quickly and will not allow access .. also I am having issues with the SD card, I can mount USB in Clockwork and copied over Vegan 5.1...it said it installed succesfully but when it launches it still says cyanogen, but says vegan in the "about phone" section this did give me a few more icons including marketplace..but it launches and then has a white screen.then closes automatically...I am afraid I have really messed somIething up here...any help would be greatly appreciated ...I would like to move forward with a Custom ROM and right now I dont care which one as long as it works...
issues
1. no USB connectivity
2. Marketplace and Flash issues
3. mixed ROMS?!??!?
Click to expand...
Click to collapse
You may have to start from scratch.
Via recovery, wipe data andcache, then flash a more stable rom like vega.
Then flash gapps and adobe flash.
.
I also just realized I posted this in Devel and not general..if a mod can move it I would appreciate it...my apologies
thanks for the quick reply...I was reading and found out i installed the vegan supplement instead of the full download...i know have vegan 5.1 ...and its starting to function a TON better...the USB is working..im going to apply the update..I think it has market and flash...I will try that..sorry for cluttering...really happy with the way this tablet is turning out...extremley happy im not bricked!!!
I hope I am not wasting anyones time by posting something that may be and I hope is a simple fix, but I have a problem with my Verizon Xoom, a 602 (without the 4g upgrade- don't even have verizon service) that I can't figure out- and it's not for lack of searching. I have been rooting my devices and running custom Roms since my HTC Touch, (a big thank you to all of you here at xda for all the knowledge and instruction I have been able to leach) but I am very much still a noob with only the vaguest since of how Linux, android or the devices themselves actually work- and that is especially true of my xoom with all its post release changes in storage and whatnot since I bought mine, so please don't flame me to hard if this is just my ignorance- I promise you I'm not just being lazy, I just can't figure this one out. I have been running EOS for a while now without a hitch, and recently installed 150 when it became available. everything was fine until a couple of days ago when it started freezing on unlock which just took turning the screen off and back on to fix, but every app started crashing, some periodically and some such as android.process.acore, browser, and google play that won't open at all. I use Team Win's recovery and tried a wipe and reinstall, but same thing. When I try to fix permissions I get a failure with the message "E: Unable to chown '/data/app/com.google.android.youtube-2.apk' 1000 1000". Also when I try to wipe internal storage I noticed everything was still there even though my recovery was saying I had a successful wipe. I switched to clockworkmod recovery and tried to use eraseData file in the folder to wipe the old way but that didn't seem to work either (which I'm not even sure I did right but figured I better get some advice first anyway), and when I tried to flash EOS 3 stable it won't get past the EOS boot animation at all. If anybody out there knows whats up and has the time to point me in the right direction it would greatly appreciated... Thanks
Wowzers! When all else fails ... unroot / re-root. That will wipe everything.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
mclpl said:
Okay I've got this weird problem since updated to awesome recovery/kernel. Whenever there is CM/Omni involved, my phone starts acting weird. Okay, listen to this.
First of all, everything seems normal after clean install. Then I install some of urgent apps (total commander, whatsapp - that's all). After a day or two my phone starts to act weird - it's rebooting itself and bootloops. I turn it off and on again - boots to os, then after a few minutes another reboot into bootloop. Okay... I thought it was because I didn't have the ext4 partition. Formatted into ext4 from recovery, installed Omniroom from 2 sept. and suprisingly it went good for two days! I installed some more apps and used it regularly - but it happend again. Reboot, bootloop, manualy reboot, worked fine for a minute, another reboot into bootloop. I thought that my SD card was damaged. h2testw claimed that it was perfectly fine. Now I wanted to install some stock 2.3.5 into it... I couldn't even pass the HTC screen because it keept rebooting itself...
Tell me what can I do to make this piece of... functional again? I ordered new phone, but it will arrive within next 14 days at best, and I still need the functioning android phone. Any advice, help is appreciate: links to a flashable stock roms, links to a fucntioning omni/cm rooms, any help on how to install them... thanks in advance
Click to expand...
Click to collapse
if you want to install older roms or stock you`ll need to fastboot an older recovery check this out http://forum.xda-developers.com/showthread.php?t=1415223 you only need to do PART 3 : Add a Recovery section
now you should be able to flash non-aw3som3 roms cm10 RC2 and below/ICS/Jellybean/Stock jaggyjags roms either way will get a functioning phone back for you, remember to wipe everything apart from sdcard once in recovery then install whichever rom