Related
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
try this, i just did it and works great. you basically need to download the stock images and use adb to push them. btw i assume you have a us version wifi only xoom. i would skip the last step about relocking it, if you plan to upgrade your kernel after your on 3.1.
http://developer.motorola.com/products/software/
once your back to stock everything, you can safely update to 3.1
I appreciate your help. Problem is I don't know how to do the things you are talking about. I've downloaded the images and the sdk. I'm not sure where I should put them on my zoom. Also when I try to run fastboot I get a device not found message. I also get a AdbWinApi.dll not found. I have no idea how to fix any of this. Yes I have a U.S. WIFI. I used the one click rook method. Is there a one click method out there that would help me?
If you're using windows, open the SDK folder and browse to the tools folder. Copy the img files to that folder.
Now open a command prompt and browse to the SDK Folder\tools folder (this folder as the fastboot.exe file that we're going to use and now the img files are also here!)
Now reboot your XOOM into fastboot mode (turn off the xoom, then turn the XOOM back on and while at the "Dual Core" logo, start pressing volume down until you see "--> Fastboot" up on the top left corner then press volume up to start the fastboot protocol).
Once you're in fastboot mode, in the command prompt, type fastboot devices to make sure your xoom is listed on there. If not, check to make sure your system isn't missing drivers, if so, download the xoom drivers again or if you have the Motorola Mobile Drivers installed already, open the Motorola Mobile Driver Installer and do an update to make sure you have the latest drivers).
Once you've confirmed that fastboot can talk to your xoom, run this commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Your xoom will then relock itself, format, and reboot.
This is as clear as I can be.
If need to, re-run the SDK Manager and make sure you have the correct packages installed needed.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
I'm betting the reason your wifi isn't working is because you didn't push the .ko files. Think of those as driver files. You probably just flashed the boot partition.
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
Well I tried to install ICS, and right after the reboot, within 10 sec. the adroid w/ a exclamation mark came up and I cannot do anything. I can adb into it, but I do not know what to do after that.
I tried to do a fastboot reboot command, but it only says waiting for device.
I have unlocked and rooted the xoom, but I have not done anything else custom to it was was running stock honeycomb. Thanks for any help!
I was able to get it back up and working on honeycomb, however, it says the software is up to date... where did the ICS update go? Thanks.
I also took the ICS OTA update while my Xoom was 'rooted'.
- Wanted to see what would happen... and I also got the 'sick' android with '!'. Was more/less expecting it to fail though.
Workaround is to go back to stock/locked and then let the Xoom update itself into ICS (via OTA). Takes a few updates getting there.
Here's what I did:
Going back to stock:
--------------------------
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path to recovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
fastboot reboot
NOTE: The images came direct from Xoom (motodev)
An easier way... (for me at least) was to jump over to a custom ROM - from xda.
- I also 'wiped' the Xoom prior to loading the new ROM (per instructions).
Now running EOS IML74K Nightly 61 and getting better battery life as a result.
Thanks, and is the following:
http://forum.xda-developers.com/showthread.php?t=1049485
the right place for the stock images?
My xoom being a wifi only, I think the HWI69 should be right? Thanks.
I got mine direct:
http://developer.motorola.com/products/software/
MZ604_HWI69.zip
Build HWI69 for US Retail
MD5 Sum: 3f52762e56474070fa71bdf34ba9afd1
Requires that you sign-up to "motodev"
Assuming you already have the toolkit and USB drivers (since you rooted).
It'll take a few updates before you get to ICS. And, I think Xoom (stock) still has some issue with SDCards. I had to go back to original just to get CWM re-loaded - though I think CWM has an update that doesn't require SDCard access (it's late).
- I have a US Xoom, wifi only (refurb deal from NewEgg).
If you have unlocked your device then don't do the OTA updates as they have a chance of bricking your device...
I would recommend you to flash a recovery image (which you might have already done) then flash TeamEOS's rom onto your xoom. It works wonders on mine.
ACTUALLY I GOT THE ANSWER TO THESE QUESTIONS (ignore this thread)
I've been reading through this guide: http://forum.xda-developers.com/showthread.php?t=1249798
Question 1: When they say wipe everything, do they mean media too? (like music and such) Because when I had a samsung vibrant, they also said that but it never wiped media.
Question 2: Will I have to run a nandroid backup if this is my first time rooting, or will it be unnecessary?
Question 3: After finishing doing everything (unlocking and rooting)
do I just directly flash this http://forum.xda-developers.com/showthread.php?t=1484770 or is there something I need to do beforehand?
Also, in the guide, it says something about green android of ! if you have received an OTA. Which I have received many from Moto before. Will I have to download the original motorola files (HC or ICS, I'm currently on ICS)? If so, where do I put it? I'm confused
okantomi said:
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
Thanks so much! I'm new to this, it's so much different from rooting my Samsung Vibrant phone
cmd hangs
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
rosystreasures said:
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
Click to expand...
Click to collapse
There may be something wrong with my instructions...they've gotten convoluted over time. Try one of the other guides in General..there are a couple of newer ones that might work better. Mine still gives a lot of information but I think I'll retire it 'cause I don't want to cause issues.
I recently rooted and flashed a rom on my xoom. I'm a simple point and click windows user and I didn't have much trouble, so it's not that hard to do.
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
http://forum.xda-developers.com/showthread.php?t=1477024
is the thread I used. Follow the instructions exactly and read the entire thread before you start, it'll save you a few headaches. This'll get you in (I think) ICS with superuser and all that jazz. If you want a rom, like me, then you'll have to head over to the development forum and take your pick. I'm running EOS 2.0, still deciding what to do with my xoom atm.
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
rosystreasures said:
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
Click to expand...
Click to collapse
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Quickboot vs. ROM manager
okantomi said:
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Click to expand...
Click to collapse
I started out with the standard 3.2 on my Xoom Wifi
with a nagging system message to update (I am guessing 3.2.2)
So I followed thread 1249798 and now am unlocke & rooted!
I am also using Recovery: Eos Recovery R6
I still get the nagging system message to update.
I would like to load a custom ROM, probably Moray.
My questions are this:
1. Will the Nagging system update message cause a
problem loading a custom ROM?
2. I could use the process as described in thread 1249798
to load the ROM, but I have read that since I am rooted
I could use Quick Boot app. Is this true? What about the
ROM Manager app, could I use this to load Moray? What is
the difference?
3. Since my base is 3.2 I am guessing I cannot load any
EOS ICS Rom's, is this correct? I need to bring my base
to 4.0 right?
4. Both Hammerhead and Moray state that they are both:
"Pre rooted with su and Superuser". Does this mean I did
not have to root my Xoom, I could have just loaded either
of these Roms and become rooted?
5. I have read some comments about:
/system/etc/install-recovery.sh
If I remove this file, will this stop the nagging System Update message?
6. Do I need to back anything up prior to loading a ROM?
Thanks!
Still with that, you can flash TEAM EOS ROM ICS. just boot into recovery and flash the TEAM EOS ROM. Mine was 3.2.1 as well. GOOD LUCK
Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Clumzie said:
Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Click to expand...
Click to collapse
OK, is there another way I can approach this as I need to get back before sending the tablet off to be fixed.
1) Can I push the ROM somehow using adb? If so, how?
2) What about installing CWM to flash the ROM and restore custom recovery? This would be my last resort as if it didn't work I'm stuck with root files & CWM!
Any help gratefully received as I need to send it back this week.
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
TomONeill said:
First off, I have some questions:
1. Are you unlocked? No
2. Are you root? (Doesnt really matter) Root files (su and busybox) but not superuser.apk due to JB OTA
3. Android 4.0 or 4.1? 4.1.2
4. At which point is that error showing up? After Finding/opening/verifying package
5. What about the stock beta ROMs? No, just the 2 official ones on the Acer site
6. Did you rename the ROM to update.zip and to what place did you copy it ? The downloaded files from ACER are a zip file with a pdf and update.zip inside. I copied update.zip to my SD card. Am I supposed to extract a particular file from it and create an archive out of that that or use the entire thing as I did?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
/system/bin/sh: push: not found
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
I'm a bit hesitant about installing CWM as I'm not convinced I won't encounter the same problems as I did with stock recovery.
Thanks again Tom
TomONeill said:
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
Hi I have question. If my phone USB can't working with PC anymore because the terminal cut out and my Gionee e3 phone stuck on boot logo or bootloop, how can I get it back to normal? Is there a flashable zip files can solve it? If there was please help me. Thanks.
Hey cryingbee,
Can't you get to the recoverymode by pressing volume down and the power button? If not, try booting into fastboot, which I think is volume up + the power button. If those combinations won't work, google for your phone name + fastboot mode. If you can reach fastboot, you can boot into a recovery by using fastboot commands or install new roms etc.