Boot Loop Error, RESOLVED!!!!

[JungleJiujitsu]

Before it was noted that the theme was for 3G only, I went ahead and pushed both the framework-res.apk and systemui.apk of the BigDX Theme into my Xoom Wifi. Now all I am able to do on my Xoom is stare at the boot animation. I need some help please!...UPDATED:I did the one-click unroot and now Im stuck on the Dual Core Tech. Screen, doesn't even get into a boot loop now!...FINAL UPDATED:I manually rebooted into fastboot(Vol Down + power keys) and then reapplied the instructions from the root thread(adb and fastboot method) and I am back in baby!!! So if any of you get stuck in a boot loop, feel free to hit me up! PM or Gtalk(same as)!

 

[B Dizzle]

Did you install the Tiamat kernel at any point?

Sent from my Xoom using Tapatalk

 

[JungleJiujitsu]

Before it was noted that the theme was for 3G only, I went ahead and pushed both the framework-res.apk and systemui.apk of the BigDX Theme into my Xoom Wifi. Now all I am able to do on my Xoom is stare at the boot animation. I need some help please!

I should note that immediately after pushing both the themed apk's:

1) I pushed the stock files/images back into my Xoom.
2) I performed the instruction in the root thread(unlocking and rooting through fastboot and adb)
3) And I flashed the stock system.apk

 

[JungleJiujitsu]

Did you install the Tiamat kernel at any point?

Sent from my Xoom using Tapatalk

Yes, its the kernel included in the root zip files...http://forum.xda-developers.com/showthread.php?t=1010568...I can post the logcat now if you'd like, but its MASSIVE!

 

[B Dizzle]

Just attach the text file instead of posting the whole thing.

Sent from my Xoom using Tapatalk

 

[JungleJiujitsu]

Just attach the text file instead of posting the whole thing.

Sent from my Xoom using Tapatalk

How do you create a txt file of the results again?

 

[sangreal06]

use ddms or:

adb -d logcat > logcat.txt

ctrl+c to stop it

 

[JungleJiujitsu]

use ddms or:

adb -d logcat > logcat.txt

ctrl+c to stop it

My bad, Im gonna need a few mins, cmd is not recognizing device any longer, have to reboot PC

 

[JungleJiujitsu]

use ddms or:

adb -d logcat > logcat.txt

ctrl+c to stop it

I keep getting device not found now!

 

[JungleJiujitsu]

I keep getting device not found now!

Nvmd, I got to mount and I was able to run logcat, but now that I typed adb logcat > logcat.txt its just sitting there.

 

[JungleJiujitsu]

Nvmd, I got to mount and I was able to run logcat, but now that I typed adb logcat > logcat.txt its just sitting there.

Ok, my bad again, I just check and its there, just had to do crtl + C there too lol ....its says it exceeds for this file type so I had to rar it.

 

[B Dizzle]

Ok, my bad again, I just check and its there, just had to do crtl + C there too lol ....its says it exceeds for this file type so I had to rar it.

I am no expert but it looks like there is a boot.img - system.img mismatch.

EDIT:
Just noticed this is resolved. What was done to fix the issue?

 

[arrtoodeetoo]

Please detail how you fixed this. I did the same thing, except I accidentally installed the wifi version on my 3g.

also, did it wipe your data?

 

[JungleJiujitsu]

Please detail how you fixed this. I did the same thing, except I accidentally installed the wifi version on my 3g.

also, did it wipe your data?

I apologize for only now getting back to you, but for future reference, the steps I took to get out are in the OP. Yes it did wipe data.....And if you are still having issues, please feel free to PM me, probably the best way to get my attention!

 

[graklore]

Ok I got in the boot loop after trying to apply the UI string, here is the way to fix it 100% of the time.

1. power off xoom
2. power on xoom, while at dual core logo press vol down wait a few seconds and press it again doing so will give you option to reboot into recovery
3. press vol up to boot into cwr
4. apply 3.1 update, apply bootfix update (if on wifi), factory reset
5. reboot and it will boot up fine

 

[drahyrt]

Ok I got in the boot loop after trying to apply the UI string, here is the way to fix it 100% of the time.

1. power off xoom
2. power on xoom, while at dual core logo press vol down wait a few seconds and press it again doing so will give you option to reboot into recovery
3. press vol up to boot into cwr
4. apply 3.1 update, apply bootfix update (if on wifi), factory reset
5. reboot and it will boot up fine

+1 exactly the same here. Except didn't reset as I had already 3.1 installed, but if you haven't definately factory reset. I didn't lose anything except my Google accounts, but adding those quickly resolved everything.
UI string dilemma, just so attractive to have a fix yet that was a unfortunate detour

 

[kojcookies]

Newbie stuck in boot loop !!!

I appreciate you guys help, I'm pretty much a tech rookie. gotta explain this to me like I'm an 8 year old...

How do I apply "3.1 update" in CWR? where is it located?
How do I apply "bootfix update" in CWR? where is it located?

I have a rooted wifi xoom. tried to flash the UA string and now stuck in a bootloop!

any simple, non-tech-savy help would be appreciated! --never shoulda went this far if i didn't totally know what I'm doing!

 

[epinox]

I just rooted in adb and fast boot method on 3.1 xoom wifi 32gb. I am now stuck in boot loop. I can go into recovery but I cannot get past the boot video screen..


what do you guys suggest I should do?

 

[kojcookies]

Well........ there may be other solutions...but I eventually bit the bullet and went back to stock....

device was wiped... all downloads and info gone... pretty much back at square one...... eh well... at least i'm back in !!