Related
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
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Drdandy said:
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Click to expand...
Click to collapse
You only flash pd98 files from fast boot not from CWM recovery. Boot in bootloader and it will find it
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Drdandy said:
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Click to expand...
Click to collapse
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
zelendel said:
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
Click to expand...
Click to collapse
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Since you can boot into recovery, adb should still work. Enter recovery then plug in your phone to PC and run adb reboot bootloader
Have you tried reflashing a rom in recovery aswell?
Drdandy said:
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Click to expand...
Click to collapse
If you are booting into CWM your not back to factory. As stated above you can use adb to boot into bootloader
Just making sure I'm doing this right as its the first time I've ever use adb commands to me phone. Do I need to downloand Android SDK to write commands to the phone?
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Drdandy said:
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Click to expand...
Click to collapse
OK looks like your bootloader is messed up. Go to the ace hack kit thread. There you will find a link foe the IRC chat room. Go there and tell them what you did. They maybe able to help you.
Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!
nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.
Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.
Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~
The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.
I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.
Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver
You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.
Got so frustrated with it I just went and bought a tf-300
c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one
Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...
People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
Okay Guys and Gals!
Now comes a mess.
Prestory: I was kinda disappointed by the performance of the stock 4.0 ICS and wanted to try out 4.2 or at least 4.1.
So I went flashing 4.2 and it didn't worked flawlessly. My Power button is somehow broken. I don't know if it's a hardware problem or software. Anyhow, I tried 4.1 and it didn't work aswell. My final conclusion was to send it back to ASUS to repair it. Of course not with a modded OS, so my goal was to flash the stock 4.0 again. Here, the trouble began.
I followed this manual [UNROOT]The easiest unrooting method (http://forum.xda-developers.com/showthread.php?t=1527931&highlight=status+7) and had a Status 7 error. One post assumed that it might be the TWRP (or so) Recovery and to try out a stock CWM.
So I downloaded the latest CWM which causes another trouble, because I downloaded the nonTouch version without possesing a dock. Well. After I got a dock I just thought: Thats it. Nope. When I try to flash a .zip from the SD Card it says, that it can't mount the SD card. So, that seems to be a dead end. I managed to install an older CWM (.13 i think) via ROM Manager but this one can't mount the SD either. The SD is accesible when the tablet is connected to the PC and through ASTRO File Manager.
I also tried Windows Tools like Easy Flasher (which fails because I can't enter APX mode for some reason), 1-Click Transformer Root (which seems to abort because of 4.1.2?) and OneClickrecovery (which also fails)
Some Infos: B40
Currently running on Cyanogen Mod 10-20130131_UNOFFICIAL-tf101 4.1.2
Well, I'm sure I forgot to mention a thousand things, so please ask.
And pleaaaase help me. The Tablet is right now pretty much useless to me and I'm really starting to miss using it.
So if you have any ideas?!
Regards from Germany, Michele
I would first try to reseat the power button by opening the device. That seems to fix the button issues for some. Then give easyflasher another try.
Or, keep trying to go into APX. It's tricky since the device doesn't appear powered on unless you have leaks on your screen, but just keep trying. Eventually you will hear the USB sound of your computer detecting it. Make sure you have the APX drivers installed too.
OK, if you have a recovery that will boot, you can try using PERI to flash Rogue Touch recovery.
The EASIEST way to flash back to stock IMO is this: http://www.transformerforums.com/fo...frederuco-s-guide-flash-tf101-back-stock.html
You can use CWM recovery to flash the stock firmware as well.
Keep in mind, if your tablet is OFF, you can hold VOL UP and then plug in the USB cord to your PC to enter APX mode (plugging it in will trigger the power on).
Same thing to enter recovery manually, hold VOL DOWN, plug in, then hit VOL UP when prompted to enter recovery.