Database Info

Steady State Xoom - No Wipe, No Flash working

First of all I'm sorry because of my english.
But i got a huge Problem with my Xoom.
A couple of days ago a mentioned that my Xoom is like in Steady State.
Every changes (Install Apps, uninstall, Move Widgets etc. ) I made are lost after reboot.
That was the Point I decide to wipe and flash a new Rom.
But it doesn't work. After reboot I'm back on my state before wiping, with all Apps and settings.
I tried wiping with CWM and via Fastboot from PC.
I also tried to install the StockRom from Motorola.
http://developer.motorola.com/produ...pportforums&utm_term=unlockboard&pubid=987654
But nothing works.
Please give me a Hint how I can make my Xoom useable again
Greetz
Crackmaniac

Is it the wrong Subforum or is it not intelligible enough?

First of all you need to know the version of your Xoom(MZ601,MZ604...) in order to know which is the fastboot executable file that you have to download.
Try this GUIDE

Hi,
thanks for your answer.
I have an MZ604 with Team Eos ICS 1.0.0 on it
http://forum.xda-developers.com/showthread.php?t=1484770
i already tried to lock an unlock the Bootloader.
Its done without an errormessage but after reboot nothing changed.
It looks like, that i haven't any rights to write the Flashmemory.
Every changes i do seems to be only on RAM and are undone after a reboot.
Its the same with formating the partitions, flash ROMs or even install/unistall an app

Root/Install ROM first time - I think I screwed up.

The basic deal is I got bored of the software and decided that I should root an install some custom ROMs on my Nexus S.
I used the One click method posted I believe in the general forum and everything went smoothly. I downloaded the latest AOKP and CM zips, put them onto my phones memory and went on with my day.
So today I began to put on the AOKP ROM and it got stuck at the initiating swagger screen. And was stuck there for a good 20minutes. I didn't know what to do, so I battery pulled.
I thought I had some backup saved from the day before, but that wasn't the case. So now I'm essentially stuck in thee boot menu for clockwork and my phone has been rendered useless. If any of you guys know what I should do, please tell, I'm extremely pissed off at myself for letting this happen.
I deleted the Cache partition and Dalvik thing when I was first getting ready to put on the ROM. I didn't to a factory wipe, so that might be an issue? I don't know. I've also tried plugging the phone into my computer, but because I cant turn on USB mass storage, I can't look through that either.
Any help would be greatly appreciated. Thanks

Hi,
If ur in the bootloader screen scroll down until u see recovery. Then press the power button.
From recovery scroll down to mounts and storage to connect to computer via USB.
From here u have a few options bjt i would just download another ROM and its gapps or a ROM that already contains them.
Just be careful to get the correct zips for ur type of phone
Good luck
Vs Nexus S4G using tapatalk2

Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!

Chillingly Based said:
Wow. Thanks a lot. Do you think I should do a factory reset before I install a new rom?
EDIT: Hey vidaljs, thanks for the help! I got the CM10 ROM up and running, apparently I was running some really old version! That USB mount thing really helped!!
Click to expand...
Click to collapse
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
And always follow what the developers suggest in their thread since they created it.
But when I go to a new ROM, I always do a factory reset, wipe cache and wipe Dalvic.
If u haven't found it yet, use titanium backup for ur apps so its easier to apply them to ur newly flashed ROM. The free version is fine but I've heard that paid version has some extra useful benefits.
Good luck and happy flashing.
Vs Nexus S4G using tapatalk2

vidaljs said:
No worries
Next thing u should do is make a backup of this working ROM so u can always go back to it in a pinch.
Click to expand...
Click to collapse
Yeah I should have done it first
Hi guys,
Almost same stroy, I tried to Root & install Cyanomodgen 10 on my Nexus S, but boot isn't working quite well, and I'm stuck at a circling image preparing the launch.
Recovery isn't working I got stuck at the image with the robot and the back and the exclamation mark on top of it and like 5 minutes later it launch the cyanomodgen ring again - and can't get in download mode.
I pretty don't get what I should do.
Any idea?
I feel I lack some info on my problem, I'll create a fresh post for it
thanks

[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!!

Random lockups, new roms failed to install

Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.

rvenes said:
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
Click to expand...
Click to collapse
Yes, that can be the reason.

_that said:
Yes, that can be the reason.
Click to expand...
Click to collapse
LOL
Yes, that and wrong recovery, no or insufficient wipes before flashing the new rom - lots of possibilities.
Before you fire into the trash send it to me! I could use a tablet to recklessly experiment on

rvenes said:
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
Click to expand...
Click to collapse
No trash! The TF700 is an awesome tablet.
I would start over. Go to the Zombi-X thread and install that rom, *after* making sure you've got the boot loader mentioned in the first posting in that thread. Then, install TWRP (the latest version rather than the 2.6 one mentoined in the thread -- I think it is up to 2.8.01 or so). Then install Zombi-X. If you have an external micro-sd card, go for the ROM2SD install as well. If not, no worries. You'll be so glad you did. But again, the Zombi-X thread will step you through the entire process. They've done a fantastic job. And your tablet will impress.

I haven't had time to look at it yet! So many other gadgets to use.
Will find time sometime this xmas.

If you were on CleanROM, you're bootloader is probably way too old.
Also you HAVE to do a clean install = wipe of cache, Dalvik and data before installing a new rom.

[Q] Phone never boots after flashing new ROM

Hi!
I am currently running CM12-20150314-NIGHTLY. I am still using this old version because every time i flash a new rom the phone won't boot. It will ALWAYS get stuck on the splash screen. It will still be possible to access recovery mode, but it won't help wiping, reflashing the new version or reflashing the old version. To solve the problem i have to re run the guide for "root, ulocking bootloader and flashing recovery" to get the phone to boot again.
Do someone have an idea why the phone won't boot after upgrading to a newer rom? I have performed the process three times with different versions of the rom so i know it will happen if i flash a new rom again.
//diddi

Bump

Couple of questions. What roms are you trying to flash and where are you getting them? How long do you let it sit at the splash screen before giving up? When you say wipe, do you mean a complete data wipe? Or just a cache wipe? My thought is that it could be any of the following:
1. You just need to let it sit longer. The first boot after a new flash can take a really long time.
2. The rom may not be complete, or it could have been a bad download.
3. You aren't wiping everything and there is something conflicting.
If it's not any of those, let us know. But we need more details.

Thanks for your response!
This time i have not tried to flash a new rom, since it have not worked the past three times. Last time i think i came from CM12 20150210 to about 20150215. But that did not work, neither the previous flash between to ROMS.
1. I have let the phone load for at least 20 minutes one time, shouldn't that be enough?
2. No, really don't think that's the case, since i can't even get the phone to bot with the rom that i was previously using.
3. i have tried to wipe cache and a complete wipe, no difference
/diddi

It seems like you know what you are doing. For good measure, I would try instead of installing a nightly, just do a nandroid backup, and try a completely different rom designed for the the OPO. If that won't flash, then it may be something wrong with the recovery or bootloader.

Thank you! Will try that tomorrow when i got some spare time! I'll come back with the results!
//diddi