Related
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?
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/showthread.php?t=2317986, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.2.6.3.0(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
Code:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?
~Fake
Status 7 errors
Those are usually caused by either a not-so-compatible recovery image. Some TWRP versions have issues with certain ROMs. I had this happen to me with my Asus TF300, ended up trying a few different TWRP versions before I found one that worked right.
The other cause is an invalid ROM image, if you open the ROM.zip file on your PC, does it look ok, did you check its MD5sum???
Were you able to wipe the Xoom from TWRP without error???
-Mike
When I got it, it had been wiped completely, so I presume that twrp wiped okay.
Not sure about the MD5sum, just that twrp didn't find one during the adb installation. Do you think flashing cwm might help?.
I got it worked out, opened up the HWI69.zip stock image and fastboot flashed the individual .img files, and it booted right up. Thanks!
I have been using chromi-x 5.2.4 w/ rom2sd for a while http://forum.xda-developers.com/showthread.php?t=2425383&page=178. I just realized today that my tablet's TWRP wasn't working properly and if I were to pull my sd card, I couldn't boot from my internal storage so I decided well I might as well try the new 4.4 http://forum.xda-developers.com/showthread.php?t=2686235. So I see it needs the newest bootloader (which is already on there I am using 10.6.1.27.5. but I realize I am running twrp 2.5.0.0. I go to the website and quickly update it TO THE JB VERSION....NOOO WHY DID I DO THAT! ( o well too late now).
I can get my tablet to recovery, but nothing will mount. Now i try to go into fastboot and neither of my comps that previously recognized the device are able to do anything (will not bootload from sd or from internal). Can't get my tablet to appear after dling univeral drivers. Anyone have the asus drivers that I can dl? Saw a few posts about unzipping two packages. I could only find the suite on the website and that is not recognizing my device. My comp tries to find them, but it fails by the time my tablet bootloops. I believe I can dig myself out of this and will read in the meantime, but I've already spent too much time on this tonight and the US lost in the last minute so I am not a happy camper!
If i type fastboot devices, I do see my serial (which I thought was a good sign and it would be a quick fix just flashing the new twrp). Doesn't recognize any commands in this post like I was trying to follow http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
[UPDATE] since twrp was asking for a password after flashing so many different versions (not sure where it went wrong) I decided to flash cwm recovery and all was well. Wiped everything. Got CM up and running in no time. Now onto crombi-kk to try it out.
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?
I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.