Related
Accidently updated my atrix 2 to 2.3.6. I then severely wanted root so I tried to flash back. I kept trying to install rsd lite but kept getting error 2738 when it was almost done installing. I googled for fastboot tools and found one on this forum. When i tried to flash an img, it apparently did not work even though I choose this fastboot tool because it said it was for atrix 2 and had atrix 2 img's with it. Now, my phone is stuck in fastboot mode and my computer can't recognize it.Any tips or help are greatly appreciated.
Did you take out the battery and see if it will reboot?
Sent from my DROID3 using XDA App
a lot of times, I did. Jim is doing his best to help me via pm but I have stumbled onto a small yet major issue. EDIT I have fixed this issue and found another. I have rsd lite working on my old, crappy laptop. However the usb port isn't giving my phone enough power to even turn on.It only turns on when charging through the wall.
Atrix 2 stuck in fastboot mode
I update my atrix 2 to 2.3.6. OTA when it was released. I then update my phone to Supercharged V5 update 2. I hated that my phone could not run most games other phones with similar specs can run. I decided to install the drivers for chainfire 3d, the phone then rebooted past the red moto logo onto a blank screen. Ever since that happened i've only been able to boot into fastboot mode. I tried using the modified .xml file, and replacing the boot.img, cdt, device_tree etc. I don't know what else to do, this happened yesterday. This is also a warning to be careful with chainfire3d after update to 2.3.6. I used it before on 2.3.5 and i had no problem with it.
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
ok i have a demo unit 32gb moto xoom that was on display at walmart until it was discontinued so now ive been trying to upgrade to cm9. it had stock 3.0.1 and a demo kernel so i rooted and flashed recovery with the Lordaio program and worked fine could do all of that normal but it wouldnt let me flash a rom, kept giving me a cannot mount sd card error all the time because i believe the demo rom/kernel was keeping the sd card from mounting while booted up but in cwm it would mount but wouldnt flash any roms still. so i flashed an old version of the timait kernel for 3.0.1 and it then let me flash cm9 but now wont boot up after the nexus like boot screen and if i hold power and vol up and reboot it and push vol down i get nvflash, fastboot and rsd none of with get me anywhere but fastboot make windows read the memory when i have a usb cable attached. but i cannot seem to get into recovery or anything else. while connected to usb the lordaio program wont go past the looking for attached devices screen unless i let it attempt to boot and then it says its disconnects before i can do anything like boot to recovery. any suggestions? fyi the only reason im doing this is because its likely mororola wont request it back at this point so its pretty much free for us here alought walmart will kill me if i were to try to take it or buy it lol
EDIT: solved! ok so i had to wait till it booted up and in adb type"c:\adb reboot recovery" and idk why i had to do it that way but low and behold it worked and fyi idk why but the cm9 nightly didnt work so i used this one http://forum.xda-developers.com/showthread.php?t=1437358
Do not see a section for the A200..... Someone in A100 said I'd have better luck here.....
OK, so I soft bricked my A200 and need to USB connect to it, so I can use fastboot or some other recovery tool.
Problem is that when I plug the A200 into my computer, it grinds away for a bit then gives a driver failed to install red "X" message.
I've reloaded the Acer USB drivers a couple of time, but no joy there. I've tried two different computers, I've tried XP and W7, nothing seems to help. Looking in the device manager shows an error 10 (device can't start).
Since the PC at least recognizes the A200 when plugging in, I think if I can get the USB talking I can easily unbrick the A200.
When I power it on, it boots to the IconiaTab screen, but no further. It's been rooted and bootloader unlocked using HBWelch's Simple Tool. I can get into fastboot mode by using a convoluted (to me, at least) procedure, that takes 6 fingers to accomplish.
After rooting and UL'ing BL it worked fine for over 6 months. Tried to flash back to stock over the weekend, and that's when I bricked it.
I posted this same message over on Acertabletforums, but so far no response's. Moderator, if you don't mind, please merge my other thread over in the A100 section with this thread.
Help??
Boowho??
Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot
success anyThan
Shreps said:
Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot
Click to expand...
Click to collapse
Fastboot appears to need a working USB connection (thru drivers). When I run it on the PC, it hangs with the message "waiting for USB connection". This is with the tablet booted in "fastboot" mode.
I CAN get it to read from update.zip on the SD card. The update.zip I'm using is the completely stock firmware (ROM, recovery, etc).
It starts the update (Android with spinning wire frame ball), gets about 25% done and then the update fails with the "dead android" symbol.
Thanks
Boowho??
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
One damn thing after another!!!
boowho said:
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
Click to expand...
Click to collapse
Everything did work fine for a day. Now I cannot enter recovery using the hardware buttons.
Using an APK called "Quick Boot" I can easily boot into CWM from the home screen and everything is fine. Root is fine, bootloader unlocked properly, etc.
Everything acting as I would expect.... BUT....
Unfortunately, not being able to enter recovery from HARD boot pretty much makes any recovery worthless, right??
Anything besides hardware that could be causing this?? The volume rockers work just fine as volume controls.
Thanks
Boowho??
This problem solved too....... Brainfart!!!
Boowho??
Hi,
I got this tablet from a friend, and it's stuck at the boot logo. I've tried hard reset, reset via recovery, nothing seems to work.
How can I flash the latest official rom?
Can't seem to find a tool for it, and Asus suggest to flash with the tablet itself, but that's not possible for now.
Anyone?
Thx!
http://forum.xda-developers.com/showthread.php?t=1688012
Easyflasher to flash TWRP recovery > copy ROM to MicroSD card, flash ROM
Thanks! I can't seem to get him into APX mode, what is the exact procedure?
Connect the tab to USB > PC first
Power Off the Tab
Hold Volume Up & Power
Nothing will appear on the Tab screen, but the PC should sound the USB connect noise / device manager will show it has connected - only takes a few seconds to enter APX mode
I've tried that, doesn't seem to recognize it . Would you help me via IM of some sort?
It`ll be the drivers most likely, open device manager when its connected and in APX mode, and manually update the drivers using the Universal Naked Driver from the Easyflasher site
I don't have any IM installed unfortunately but I`ll help you out here
Ok, that would be wonderful. The problem is, I don't know when it's off. I can't get it to shut down, it keeps rebooting. I'm monitoring dev manager with sound high, but it's not coming up. Cable is working, because it will charge. Using the original cable. (Windows 7 x64)
Best thing to do would be connect it to the PC, then press and hold Power until it shuts off, then try for APX mode - you might even be able to enter APX from a powered on state by holding the same button combo, but Ive not tested that myself
And a cable that charges doesn't automatically mean it will work for Data, they use different pins, some for power and some for data, if the data pins are damaged, it will still charge
I can't seem to get it working . Any other ways to flash it?
Not without being able to get it to boot - you'll need APX mode to do anything in the state it's in now
A bad cable is a common problem though, might be worth grabbing another one from eBay
To bad. I'll try and let it drain till it's empty, and fully charge it then. Just ordered another cable.
Thx for the help!
If the System / Data partitions are corrupted, which generally causes the boot loop, then draining and recharging won't help
Plus be careful not to drain the battery to 0%, their design prevents them from recharging if they hit 0% - many people have had to buy new batteries after not using their tab for a few months and letting it drain completely
Good luck, so long as there is no hardware damage, once you have a working cable it should be pretty straight forward to get TWRP recovery and a new ROM flashed to it
Might be worth trying your current cable on another PC too
Thanks for the headsup! Will try!
Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of a couple of days ago it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TEAMWIN logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle.
I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. Tried different installed drivers as well. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a days now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Jayster0966 said:
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Click to expand...
Click to collapse
Have you tried a different / new cable in-case that's the reason all the flashing attempts and computer recognising the unit are failing ?