Database Info

[Q] Transformer Stuck in Recovery

Alright guys I need help.
As always, a little background here first. So I've been running Android Revolution HD 3.1.0 without problem for quite some time now, but today I wanted to try flashing a couple ROMs. So I installed ROM manager, flashed CWM (I was using Roach's recovery before, but decided to switch for whatever reason), and did the usual. I wiped data, flashed CM9 & gapps, didn't really like it more so then I wiped data again, flashed AOKP 1.7 & gapps, and then everything fell apart.
Once it installed (without error I might add) I hit reboot device now and it went straight back into recovery after showing the ASUS splash screen. So I wiped data, flashed ARHD3.1.0, and the same thing happened.
Now, no matter what I do, I can't get my Transformer to boot into anything but CWM. What do I do???
EDIT: Fixed. I found the thread about the recovery that was giving people issues. Thank goodness for XDA!

Same here. Idk what is the problem and it is frustrating.

Sean-El said:
Same here. Idk what is the problem and it is frustrating.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1530337
This thread saved me. Hopefully it'll do the same for you.

This was a lifesaver for me too.

[Q] Problems with most Roms

I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:

Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks

I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?

I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)

Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.

Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard

Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I

sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.

Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun

touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?

Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.

Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.

Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app

[Q] Need Help!...Hope this isn't a brick...

I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?

mrchocklit said:
I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?
Click to expand...
Click to collapse
It is more likely that you have a bootloop.. As long as your bootloader is working, you can do a lot of things that can bring your tablet back..

Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?

sbdags said:
Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?
Click to expand...
Click to collapse
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.

mrchocklit said:
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.
Click to expand...
Click to collapse
Just follow the instructions in the CROMi-X first post
I don't know how other ROMs set themselves up.

[Q] Help! Can't get past M logo after EOS4 installation on STINGRAY

Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?

199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.

airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.

Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.

Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.

Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.

punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))

Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app

SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!

[Q] XT926 Stuck on 11/07 CM 11

I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?

Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.

CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?

I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?

iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!

lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.