Related
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...
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
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately ROM Manager does not work with the TF700 and you are not the first one to find out the hard way...
If you cannot find a way to boot into the bootloader to have fastboot, there's nothing you can do anymore without the NVflash blobs.
Did you try holding Vol - and then pressing the reset button in that little pinhole on the side of the tablet?
If you have ADB drivers installed on your PC you could try if you can establish an ADB connection at any point. If you did, you could issue the command: "adb reboot bootloader", which would enable you to flash a recovery and/or bootloader. This probably won't work since you need to be in the recovery or have Android booted for ADB to work, but worth a try anyway...
Admittedly these are very thin straws - but what have you got to loose?
Also: Just a few days ago a user here was stuck on a bootloop to recovery and couldn't get out of it. He left it alone overnight and all the sudden the bootloop sorted itself out... I have no explanation for it and it is unlikely to happen in your case, but you never know...
Good luck!
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Quentin2 said:
Thanks for replying.
Yes, I did keep Vol-Down (means Vol-Left) pressed while pinching the reset button. It did not help.
I will experiment a bit more. It's not really a boot "loop" - it gets stuck at the ASUS logo and this does not change anymore. Not overnight.
So far I could only see it being recognized as USB device in APX mode. Can you give me a bit background here? I have nvflash here. The blobs are not available anywhere on the net? Or why is that all a big fuzz? I used to have a Notion Ink Adam and APX saved my life several times, but the blobs were available to everybody. Nobody has the blobs here? Or are they device-specific?
I cannot believe that a today's device with a non-bricked bootloader and working APX is totally lost and even the manufacturer will only offer a costly RMA to replace the whole mainboard!?
Best regards,
q2.
Click to expand...
Click to collapse
For the TF700 the nvflash blobs are device specific - sorry.
Damn. That was the only answer I didn't want to read
Thanks a lot. So chances are gone, only RMA could help... I will ask friendly at Asus what costs they will charge...
q2.
Update:
Reply is here.
They only want to exchange mainboard. They of course know (and it seems that this is the only thing they know) that my bootloader was unlocked, therefore this is no case of guarantee for them. I know, I wrote to them that I just want to know how much they wanna charge me to fix this issue.
But: they don't want to tell me how much. They say they do not even know which revision and what hardware is inside my tablet, not even from my serial number. And I must first send them my tablet and they will charge me 95 Euro to check what's going on. And then they will tell me how much it will cost (and according to other threads I saw prices of over 400 Euro for a mainboard change - the TF701 successor model cost 450 Euro new in store)...
I somehow feel the need to reply that if they would've put only half the energy the put into logging who has unlocked the bootloader into the fact of making APX usable as a emergency recovery (as obviously not even Asus is able to generate a working blob for my device), they would have higher customer satisfactory statistics. I still just cannot believe a today's device lacks of all recovery options after a bootloader fails for some reason - as well as I cannot understand why Koush did not display a warning in ROM manager if problems are known to the community with this specific device (I mean the problem did not arise last week and ROM manager had tenths of updates since then).
I know that in the end all was my fault. And all flashing is done on our own risk. I will have to deal with it.
Phew...
Unlucky. It should be be stickied here somewhere that ROM Manager bricks the TF700 but then there is no guarantee it would be read. It is well known on this forum but that doesn't help people that don't visit frequently.
You can replace the mainboard yourself fairly easily. Watch the you tube vids on how to do it,. That is what I would do if I was in your position.
berndblb said:
For the TF700 the nvflash blobs are device specific - sorry.
Click to expand...
Click to collapse
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
zeddock said:
Is there a way to backup my blobs before I leave all stock then?
Thanx! Zeddock
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Any Solution?
Quentin2 said:
Hi.
I own a TF700T and seems to have bricked it. Last status was: I had the latest stock ROM with root running and wanted to get a CM11 based 4.4.2 image from here. I downloaded it and used rom manager to get it installed. But the install script failed at some point and I thought the recovery might be outdated. So I used ROM Manager to update recovery... I tried CWM and TWRP option. Finally I booted up into recovery trying again to install those damn rom - I used the option to wipe all data / settings from the main menu and tried again to install the ROM which again failed (I do not remember the error message clearly). I gave up. I used the "reboot" option.
Now:
- Powering up gets me into the screen with the ASUS logo (left upper corner says "the device is unlocked"). Here it is stuck forever.
- Power + Vol-Down is same as just Power - I do not get into flashboot with those 3 small icons... I just get the ASUS logo and nothing else happens. Reset hole does not change situation. The device is pretty much "always on" now (till battery is exhausted) as long-press Power turns off and immediately on again
- Only thing that seems to work: Power + Vol-Up ends up in APX mode - my computer recognizes the device via USB at this point
Unfortunately I never did any set up to nvflash.
Do I have any chance to get this thing alive again?
Thanks a lot in advance,
q2.
Click to expand...
Click to collapse
Unfortunately I'm stuck in same boat I tried to wipe out settings completely and clockwork mode was stuck and I was able to wipe recovery with TWRP or so I thought tried to reboot into recovery got stalled and now stuck on asus screen. I'm not opposed to buying a new motherboard but I find it very hard to believe that no one has come up with a solution to flashing the mainboard with the original firmware. I'm tempted to ask asus but I know the bill will be more then the tablet. Did you find an easier solution or do I just have to swap out the mainboard?
sbdags said:
http://forum.xda-developers.com/showthread.php?t=2455925&highlight=nvflash
Click to expand...
Click to collapse
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
zeddock said:
Thanx, but it seems like to backup blobs I have to do the very thing that will risk me needing backup of my blobs? ... install a custom bootloader before I have a backup?
Is this right?
Is this a safer method?
zeddock
Click to expand...
Click to collapse
That's correct. You have to flash a modified bootloader and recovery. Done correctly this is not risky at all. But if there is a single line in the instructions you are not sure you understand, you are not quite ready.
There are quite a few tutorials on flashing in fastboot on this forum. Read them.
But generating your nvflash blobs you have to do without a safety net. It's worth it though! I have become much more adventurous with my tablet since I have the blobs squared away...
berndblb said:
Done correctly this is not risky at all.
Click to expand...
Click to collapse
How do you define risk?
Flashing a bootloader (without having nvflash access) is always risky by my definition, it *can* permabrick your tablet if something goes wrong at the wrong moment. But it's the best we have.