Apology: Hello, I'm Dan and I am an old n00b. I've been a member of this forum for quite a while now and I don't think I ever posted with a problem. However this time I can't seem to able to find a resolution with my normal methodes (searching) If the solution to my problem already exists I have to blame my age
Hardware:
Motorola XOOM Wifi
Software:
ROM Team_Eos's Jellybean build 3 (which worked for me in the last month)
CWM: being the (old) idiot that I am, I "upgraded" CWM to 5.8.3.1 through ROM.Recovery (I now know that was a bad idea)
USB_Debug: No idea of that is on or off, can't check because I can't get into the ROM because of bootloop
Computer: I do have the motorola developer USB drivers, and android SDK. I have successfully installed custom ROM's for my S3 and for my Xoom so I think everything is correctly installed
Problem:
1. Bootloop
2. At fastboot I don't see the device through "adb devices" (during normal boot(loop) i can see the device but as soon as i "adb reboot fastboot" i lose it.)
3. CWM works but I can't mount SD-Card
I hope my problem is clear and I hope there's a solution. I do apologize for my bad english and my poor computer skills
Thank you in advance
Sorry to hear that bud, if you can get the twrp img eos edition and fastboot it your problem will be solve, http://forum.xda-developers.com/showthread.php?t=1782235, runandhide05 has a few edition post here but my favorite is the eos one..
tumpy said:
Sorry to hear that bud, if you can get the twrp img eos edition and fastboot it your problem will be solve, http://forum.xda-developers.com/showthread.php?t=1782235, runandhide05 has a few edition post here but my favorite is the eos one..
Click to expand...
Click to collapse
Thank you for the quick reply.
I am not able to follow the instructions on the post as
1. I can't mount SD-Card in CWM
2. Don't have adb in fastboot
Thank you
EDIT:
I am sorry, there is a way (the 4th method) to install and it worked flawlessly.
This thread can be marked as solved
Thank you again!
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Help me, i followed this thread
http://forum.xda-developers.com/showthread.php?t=1074609
upgraded my 3.01 to 3.1 but forgot to do the step 5. i am using wifi xoom..
now i'm stuck at the boot flashing screen. have i bricked my xoom?
i feel like crying..
its so silly i forgot to do the wipe data/factory reset. i went straight to reboott he thing.
please there must be something i can do.
mankidal said:
its so silly i forgot to do the wipe data/factory reset. i went straight to reboott he thing.
Click to expand...
Click to collapse
i´m sure about this is the problem... when you changes your rom by another.... you must to do full wipes because the apk´s must "zipalign" again and busibox its new too...
can you enter to recovery menu????you can recover your sistem from here....
EDITkay i´ve just read your xoom post...
enter into recovery menú flah the rom again step by step but DO FULL WIPE BEFORE FLASH AND AFTER FLASH
i am able to connect it to my pc and run commands via the fastboot protocol support.. but i am not sure what to do. can you help me from here?
i am using the wifi only xoom, which i think dont have the recovery menu however i have fastboot protocol support which i dont know if will work flashing files, although i could do a reboot from command line now
EDIT
Boy oh boy am i a happy person today. after all the things thats been going on with my xoom;. i thought i nearly bricked it.
i am very fortunate of 2 things mainly,
got it to reflash via fastboot, (downloaded US stock flash files from motorola site)
reboot and voila!...
not just that.. moments later. i got OTA 3.1 update via wifi!!!! yay... i am so happy i nearly cried
after all the hassle wanting to upgrade to 3.1 without the OTG cable, i went and flashed 3 or 4 tiamat versions today before soft bricking the xoom.! phewwww that was so close
if anyone wants to ask me in detail of how i recovered. pls feel free to PM me...
thanks all
not i guess its time to install clockworkmod and lets see if tiamat 1.4.2 will be a successfull install
Finally you solved it or you haven't the fastboot parameters??your last thread its too harsh for to me,dificult i've a poor english...
If you need suport for recover your xoom i'm going back to home in a few hours.. 3-4.... And nicely i will answer your SHORT QUESTIONS lol
sent from my amstrad CPC powered by LOL..(premium xda)
mankidal said:
reboot and voila!...
not just that.. moments later. i got OTA 3.1 update via wifi!!!! yay... i am so happy i nearly cried
after all the hassle wanting to upgrade to 3.1 without the OTG cable, i went and flashed 3 or 4 tiamat versions today before soft bricking the xoom.! phewwww that was so close
if anyone wants to ask me in detail of how i recovered. pls feel free to PM me...
Click to expand...
Click to collapse
I'm just curious - what are your thoughts on the new 3.1 now that you're up and running?
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
Hi everybody,
after unlocking my bootloader and rooting my HTC One S, I installed the Cyanogen 10 custom ROM.
Problem is that I got stuck in a bootloop, so I tried to fix that problem by resetting to factory settings in CWM; but now it doesn't detect the sdcard folder of my One S ("Can't mount /sdcard/"), and I can't adb push another ROM from my computer ("device not found")...
So I searched on that forum and found this thread : http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
The author of this thread had the same problem as me and solved it by himself (look at post #8), so I tried his method and installed the One S All-In-One toolkit to flash the TWRP recovery. BUT there are 3 versions of it : the S3, S4 and Special Edition.
I know that my phone isn't the Special Edition but i don't know if it has the S3 or S4 processor :S
So i would like to know if there is a way of seeing if my processor is S3 or S4 considering that i can't boot on an OS...
Thanks for the answers (and sorry for my bad english, i'm french)
Forget about it, I solved my own problem too XD
I forgot to flash the boot.img of Cyanogenmod 10 !!
What a noob I am
Anyways, thanks to myself and I hope you won't do the same error as me xD
Switch to twrp as soon as you can... There will be more problems...
Sent from my HTC One S using xda premium
Hello everyone!
I have problems with Recovery for my tablet. I have no way to fix it. I hope people help me
My tablet is running fw 4.2.1 Asus, I am root but everytime you want to load CWM, the tablet show ERROR. Although I have tried to follow the instructions on the forums but have not been.
I find when in fastboot mode on tablet and see "not driver or no key,.." (I do not remember)
Help me fix it and sorry for my english.
Thanks
butoon said:
Hello everyone!
I have problems with Recovery for my tablet. I have no way to fix it. I hope people help me
My tablet is running fw 4.2.1 Asus, I am root but everytime you want to load CWM, the tablet show ERROR. Although I have tried to follow the instructions on the forums but have not been.
I find when in fastboot mode on tablet and see "not driver or no key,.." (I do not remember)
Help me fix it and sorry for my english.
Thanks
Click to expand...
Click to collapse
I think CWM is not working well with 4.2.1. I would try TWRP as custom recovery, but be very (as in VERY) sure to install the TWRP version meant for your bootloader. In General section you can find a very good how-to written by pjc21, which also list which bootloader and TWRP versions match. The guide is here: http://forum.xda-developers.com/showthread.php?t=2195883
Use that and don't forget to thank pjc21.
Good day,
I have a tf101 with stock rom (4.0.3)... I recently purchased a Nexus 9, so I figured it was time to start playing with my tf101. Would someone have a link that shows a step by step *How to* to update from stock 4.0.3 to stable KatKiss 4.4.4. I've never done any of this so I need some guidance, if a Youtube video exist that show what to do from start to end I would appreciate the link, otherwise a detailed how to with all related pages would be great.
Thank you in advance for your help,
Albatorak
Use EasyFlasher to install custom recovery and root your tablet. Follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1688012
Make sure to install the correct drivers before you begin. Choose TWRP. The version bundled with EasyFlasher is probably outdated, so flash the one from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
You're good to go after that. Download latest Kitkat or Lollipop Katkiss by timduru, or try OmniROM by sidneyk. Here are the links:
http://forum.xda-developers.com/showthread.php?t=2592890
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560
http://forum.xda-developers.com/showthread.php?t=2584265
Instructions are provided in the first post of every thread.
Duchman said:
Use EasyFlasher to install custom recovery and root your tablet. Follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1688012
Make sure to install the correct drivers before you begin. Choose TWRP. The version bundled with EasyFlasher is probably outdated, so flash the one from this thread: http://forum.xda-developers.com/showthread.php?t=2434422
You're good to go after that. Download latest Kitkat or Lollipop Katkiss by timduru, or try OmniROM by sidneyk. Here are the links:
http://forum.xda-developers.com/showthread.php?t=2592890
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560
http://forum.xda-developers.com/showthread.php?t=2584265
Instructions are provided in the first post of every thread.
Click to expand...
Click to collapse
This instalation with EasyFlasher is not clear for a layman ;( where do I put this EasyFlasher? on my computer or on my tablet? it is not clear for me... ;(
Thanks in advance for help
HankaW.redna said:
This instalation with EasyFlasher is not clear for a layman ;( where do I put this EasyFlasher? on my computer or on my tablet? it is not clear for me... ;(
Thanks in advance for help
Click to expand...
Click to collapse
Install APX drivers from here: http://forum.xda-developers.com/showthread.php?t=1514942
Then download EasyFlasher to your PC and run it. Prompts will guide you on how to put your device into APX mode. Make sure you have TF101, because this method won't work on TF101g or SL101.
Duchman said:
Install APX drivers from here: http://forum.xda-developers.com/showthread.php?t=1514942
Then download EasyFlasher to your PC and run it. Prompts will guide you on how to put your device into APX mode. Make sure you have TF101, because this method won't work on TF101g or SL101.
Click to expand...
Click to collapse
I have one more question just to be on the safe side
When I have installed this easyFlasher and put my device (definitely TF101, thanks for pointing out!!!) int APX mode I can root from where? Let's assume I am in this TWRP and want to continue with KATKISS Lollipop, do I need to root first? or ROM (meaning the KATKISS lollipop?) and then SuperSU
is SuperSU from Timduru going to be enough to root in the order shown by him?
Thank you in advance for any help!!
Yes, I am VERY green but I am trying my best to do everything properly and enjoy the speed and functionality
HankaW.redna said:
I have one more question just to be on the safe side
When I have installed this easyFlasher and put my device (definitely TF101, thanks for pointing out!!!) int APX mode I can root from where? Let's assume I am in this TWRP and want to continue with KATKISS Lollipop, do I need to root first? or ROM (meaning the KATKISS lollipop?) and then SuperSU
is SuperSU from Timduru going to be enough to root in the order shown by him?
Thank you in advance for any help!!
Yes, I am VERY green but I am trying my best to do everything properly and enjoy the speed and functionality
Click to expand...
Click to collapse
After flashing the recovery, boot into it (power+vol.down until a screen shows to choose vol.up for recovery.)
If everything went right, you should be greeted by twrp.
Now go to the KatKiss - Lollipop thread, download the ROM and Gapps. Get the latest supersu.
Read installation instructions carefully.
Short version:
Put all three .zip on sdcard. Boot twrp.
Wipe dalvik, cache and system . FORMAT data (important if upgrading to lollipop. A wipe won't do).
install katkiss then gapps and last install supersu. Now reboot.
The supersu.zip is always the last to flash, because it installs the su binary and the helper-app into the presently installed ROM.
doppelhelix said:
The supersu.zip is always the last to flash, because it installs the su binary and the helper-app into the presently installed ROM.
Click to expand...
Click to collapse
This is indeed correct in most cases, but Tim explicitly states that supersu should be flashed before Gapps on Katkiss Lollipop:
timduru said:
Also just to make sure: you tried a full wipe and install in the specific order listed in the 1st post ?
rom-supersu-gapps ?
Click to expand...
Click to collapse
---------- Post added at 01:04 PM ---------- Previous post was at 12:57 PM ----------
HankaW.redna said:
I have one more question just to be on the safe side
When I have installed this easyFlasher and put my device (definitely TF101, thanks for pointing out!!!) int APX mode I can root from where? Let's assume I am in this TWRP and want to continue with KATKISS Lollipop, do I need to root first? or ROM (meaning the KATKISS lollipop?) and then SuperSU
is SuperSU from Timduru going to be enough to root in the order shown by him?
Click to expand...
Click to collapse
EasyFlasher will both let you put your device into APX mode and flash recovery/acquire root, but you don't really need root for flashing recovery or ROMs.
Duchman said:
This is indeed correct in most cases, but Tim explicitly states that supersu should be flashed before Gapps on Katkiss Lollipop
Click to expand...
Click to collapse
Yeah, I trust timduru, he is an excellent developer. Although I think he is trying to make a point here, so he can give reliable support. In the KitKat thread there where a lot of stupid "doesn't work" posts, just because people forgot to install gapps. From a technical point of view it doesn't matter which comes first, as long as it is done. Quiet frankly, if the gapps would change something that superu did, that would be really strange.
Thank you all!! So, today is THE Day when I shall try... and how do you add LIKE in tapatalk? i can't see this option. I sooooo wanted to like all your helpful hints and instructions!!!
Will do it from my comp later on but THANK YOU!!! really appreciate your help!!! Everything seems clear now!!!
HankaWredna said:
and how do you add LIKE in tapatalk? i can't see this option.
Click to expand...
Click to collapse
Just tap the post you like. The topbar will present some options
Thank you i never stop learning
I started with easy flasher but it only flashes TWRP2.2 something, so a very early version ;( and TIMDURU advises to use much higher version like 2.8 something for his Lollipop
How do I put this one on my Asus?
Thank you in advance!!!
I decided to give it a try, put the 2.8 sth version in the internal memory, went to TWRP, pressed install, found this 2.8 sth and slid for flashing... now I am going to check the version... if it worked (fingers crossed) I shall continue with the rest
the task went smoothly, I started working on KatKiss,
I am sooooo shocked how powerful this thing is now!!! THANK YOU ALL!!!
but I can't find developer options to turn on debugging mode ;( and I think I need it because my computer cannot see the device ;(
HankaW.redna said:
but I can't find developer options to turn on debugging mode(
Click to expand...
Click to collapse
Go to Settings>About phone and hit the build number 7 times to unlock developer options
I can't believe how fast eerything is now... and loud thank you all again with all my heart for helping me bringing to life my device
I have one more huge request, I can't find the link to working YouTube, Timduru says an older version will work... Where do I Look? I find a link for KatKiss 4.4, is that ok?
tapped from asus with Kitkass lollipop by Timduru
HankaWredna said:
I can't believe how fast eerything is now... and loud thank you all again with all my heart for helping me bringing to life my device
I have one more huge request, I can't find the link to working YouTube, Timduru says an older version will work... Where do I Look? I find a link for KatKiss 4.4, is that ok?
tapped from asus with Kitkass lollipop by Timduru
Click to expand...
Click to collapse
You can find a lot of older versions here: http://www.androiddrawer.com/22783/download-youtube-app-apk/
Congratulations on your "new" tablet
and someting went sooo wrong and I have no idea what to do now
Yesterday my device was all fine and fully fincional, I watched sth on it, played some radio online and then wanted to checksomething on the internet
My device froze, the screen was unresponsive, the back key on the keyboard as well
I pressed and held power and it returned
I decided to check this net thing again but this time it didn't return, it showed something like "... unable to encrypt" or encryption unable to"... and I could only press one thing, OK, so I did
the device froze on ee pad screen
I tried power volume down, blue screen from twrp appeared and it got stuck
I have no idea what to do now???
if anyone can help me, please PLEASE write step by step including things like connect youf TF101 to our PC, because i am the layman of all laymen in the world...
thank you in advance for any help
as for now the device is charging because I remember that there was very low energy level in tablet and above 90 % in keyboard.
After analysing few posts I came to conclusion that my device is bricked. How that happened I have no idea but I decided to un-brick it with easy-flasher and it worked so I repeated steps from previous posts but with version 17 and now I can see KatKiss sweet doggie
and
Android is updating
let's connect with WIFI and life should be good again