Database Info

[Q] Thanks! (and HELP!)

Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.

From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!

still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance

You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk

Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87

feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...

Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.

still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.

Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot

UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.

Stuck in APX mode

powered up with PWR and (-) key and wont come out of it

Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).

still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.

skip this, finally woke it up...on to next problem thanks all

When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev

ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...

my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help

georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.

I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.

Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev

butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim

blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.

roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.

nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...

[Q] Okay need some serious Help

ok i know this has been mentioned already just not sure if those topics/posts apply to me.
before i did the below, i tried the tnt lite enhancement pack and had upgraded to 3588 from viewsonic, don't know if that mattered, but i reinstalled clockwork .8 afterword and started to flash zpad
was flashing zpad and zpad enhancement pack (though i don't think i needed to) and i flashed the mdpi tegra gapps now i have a borked tablet.
at first when i was trying to flash zpad and the enhancement pack it would restart with viewsonic logo and then it would just be blank black screen that was lit up so the screen was on. and it took atleast 5 seconds of holding power button to get it off, but it was still able to go into recovery.
so i figured something i was flashing was causing something to go wrong, so i just flashed zpad and the gapps no enhancement pack and it booted, read that pershoots kernel was best so i downloaded it from his site, maybe it was the wrong one, idk but after flashing that all that would happen is the screen would turn on to the viewsonic logo, did not recognize the command to enter recovery by holding volume button.
so i was like wth turned it off and literally touch the button for like 2 seconds and it would turn off. tried going into recovery no dice. wth do i do, i just passed the 30 day mark from sears. (i was gonna return it but after seeing honeycomb, hells no)
any advice???

Instructions if you have a brick.
http://forum.xda-developers.com/showpost.php?p=11230514&postcount=1

http://forum.xda-developers.com/showthread.php?t=861950
Try that before you take apart your machine.....It sounds like you flashed the zpad kernel for the zpad. That kernel is for the malata zpad not the zpad rom on the gtab. If you can get to apx mode then you can nvflash stock and start over.

Don't even have nvflash or how to use it.
Kinda lost....I downloaded pershoots kernel for zpab/gtab of his site.....
Sent from my PC36100 using Tapatalk

your gonna have to read that thread...it tells you how to get and flash nvflash

K thanks ill update later once I get a chance to try the fix
Sent from my PC36100 using Tapatalk

get on the irc channel at freenode.....#tegratab....someone there is usually around to walk you through it

Hehs never used irc
Sent from my PC36100 using Tapatalk

well crap i did the nvflash stuff and some last part or something failed and now it really is a brick

got back to stock now how do i get clockwork working? i have the right update.zip, but i get the android txt then a triangular sign with a ! any suggestions

thorpe24 said:
got back to stock now how do i get clockwork working? i have the right update.zip, but i get the android txt then a triangular sign with a ! any suggestions
Click to expand...
Click to collapse
Have you followed the instructions in the following thread? Sounds like you're missing the recovery folder, or did not extract the the clockwork.zip which would have an update.zip file and the recovery folder with command file. You need both on the sdcard for clockworkmod to install from stock recovery.
http://forum.xda-developers.com/showthread.php?t=865245

yeah realized that myself. well i finally got it working right except that now when i try to restore with titanium or download something from the market etc. the damn thing restarts.
would that be a kernel or rom probem, trying to run zpad. was on vegan 5.1 for forever but i need to play around with stuff to find what is the most stable and quick, i use it for work and now i can't it's really irritating.

what did you do to get back from the brick state? Nvflash ran for me, something at the end failed and now it looks like I have no APX mode because the tablet wont turn on at all. I have done apx and nvidia flash before so I think I know when the tablets turns on and goes into apx mode. My pc also tells me by attaching the device when I enter APX mode. So no APX mode, no turning on. Whats does the internal pushbutton really do? There is another post about touching/bridging two contact points together but no pictures. I think its talking about the place next to the interal pushbutton but I am not sure nor do I know which two contacts to bridge/short together. Is the second pushbutton location something like a flash recovery. I used my nvflash bat file and folder that I used before to do recovery so I am not sure why nvflash failed and screwed my tablet but this not looking good.
Any help recovering from this would be appreciated because this is not looking good. I am hoping its a dead battery so I am charging now and when I get back from work I will check again and then maybe take it apart.

nvflash crash, gtab is dead
charged the battery and still no apx mode, the gtab appears to be dead. nvflash errored out, and either rebooted this gtab or crashed it immediately but I have no signs of life and not sure what the disassembly can help with at this point.

EVERYONE SHOULD SETUP NVFlash NOW!!!!!!!!!!!!!!

I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.

I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc

steve1040 said:
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
Click to expand...
Click to collapse
No its not a replacement for cwm. NVFlash will help you recover if you every brick your device and need to go back to stock image.
Couple of scenarios where it will be helpful is if you update to the new stock update from VS and decided you want to go back to one of the custom roms like Vegan GB RC1, then you will need nvFlash to go back to stock, otherwise you will brick your device.
Also I have noticed that I have to use nvFlash if I want to go from GB rom to FORYO rom.

Cannot get NV Flash to finish?!?
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike

nvflash unsuccessful or wrong version
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
Sounds like the nvflash wasn't successful. The message you are getting when you boot to recovery...Power + vol(+) indicates that CWM is installed. If you nvflashed a stock version, cwm would not be there (unless you nvflashed a stock version with cwm preinstalled). Are you sure you flashed with the correct bootloader version. You should have used the 1.1 b/l version. Here is a link to b/l 1.1 version 3588 with cwm preinstalled http://www.mediafire.com/file/picrzt9pdkuqbj0/gtab.nvflash.1.1.branch.20110422%20with%20cwmv8.zip. Nvflash this & see what happens. By the way. when doing the nvflash, the cmd shell output should look something similar to the attached file...won't be exact since this was for a bl1.2 4349 version I nvflashed yesterday.
Al

sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
My website linked in signature. You're a code red.

Hello, thanks for the response! I am downloading now and will let you know shortly...
Mike

goodintentions said:
My website linked in signature. You're a code red.
Click to expand...
Click to collapse
What is a code red?

Code Red is the condition of your G Tab. If you follow the link in the signature of Goodintentions post (Viewsonic G-Tablet for Dummies) you will find complete and simple instructions on how to recover your G Tablet. You can also find links to the files you will need. It's a great site for anyone having problems with their tablets. It's where I got all my information when I first started.

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.

So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike

Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.

DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!

It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.

well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.

DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.

okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.

Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!

farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.

DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?

Thanks for that important tidbit, solarnz. I'm going to file it away for future use.

OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!

Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk