Database Info

Xoom bricked

Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.

Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.

If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.

Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?

Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.

Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?

eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App

sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.

[Q] Please Help! Phone Bricked (Noob Problems)

Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!

Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app

luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.

Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!

fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.

Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!

fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.

Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?

fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.

Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again

fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?

Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.

fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.

Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?

fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?

Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!

fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.

[Q] Help with nvflash

So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.

Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
Haven't you seen This coming in?

Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
If your TWRP, fastboot, and adb are still working, then your bootloader and custom recovery are still good.... You may want to format your data partition and wipe everything on your internal SD and then flash your custom ROM again... You may need to check that your TWRP and your bootloader are compatible before installing the custom ROM... Good luck..:fingers-crossed:

graphdarnell said:
Haven't you seen This coming in?
Click to expand...
Click to collapse
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.

I don't think you need to use the nvflash files as you are not bricked. If you have a spinning wheel and can get to TWRP then make sure you flash the booloader package in the first post of CROMi-X first, reboot and then flash the rom again.

Chazzfazzle said:
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.
Click to expand...
Click to collapse
You know that you have to boot back into system after flashing the bootloader, do you?
The sequence is:
flash bootloader in TWRP
reboot system
boot back into TWRP
flash rom

TWRP install question..I'm on 4.4.2, Rooted, Unlocked

Ok, so I'm just looking for final confirmation before I install my TWRP2710-RAZR-HD_M-KITKAT image...going to just fastboot flash it on there using the files in my Motopocalypse folder, but do I need to rename some file in the system folder or something before I do this? Seems like I had to do that in the JB era and I can't find much for the KK version. Noob question I know. Do I just put my phone in fastboot mode and flash away or is there a step prior to that? Thanks in advance.

Just follow the directions here: http://forum.xda-developers.com/showthread.php?t=2776515

pothole said:
Ok, so I'm just looking for final confirmation before I install my TWRP2710-RAZR-HD_M-KITKAT image...going to just fastboot flash it on there using the files in my Motopocalypse folder, but do I need to rename some file in the system folder or something before I do this? Seems like I had to do that in the JB era and I can't find much for the KK version. Noob question I know. Do I just put my phone in fastboot mode and flash away or is there a step prior to that? Thanks in advance.
Click to expand...
Click to collapse
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!

iBolski said:
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!
Click to expand...
Click to collapse
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify

Thanks gents, just the info I was looking for.

pistacios said:
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
That's what I did. Worked great!
Sent from my DROID RAZR HD using Tapatalk

pistacios said:
Or you could just use flashify in the play store...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
The only thing about Flashify that I don't like is you need to be already rooted.
Otherwise, if you're not rooted, then you can't root until you put on a custom recovery, which means you need to use fastboot to flash CWM or TWRP and then sideload root. Then you'd be able to flash TWRP or CWM. Kind of the chicken and the egg conundrum.
Everyone should know how to do it via fastboot because you may not have root to install TWRP or any other custom recovery. It's always good to know how to do things from the command line because there may come a time when you have no other option.

running official kk on xt926 here.
can i install official cm11 nightlys after flash 2.7 twrp ?

I believe they can only be installed when they update them with the new kitkat bootloader. There are some builds by dhacker29 that I have tried that worked but are in progress. You would need to reflash back to JB bootloader to use the official CM11 nightlies.
aaki_rocker said:
running official kk on xt926 here.
can i install official cm11 nightlys after flash 2.7 twrp ?
Click to expand...
Click to collapse

yujikaido79 said:
I believe they can only be installed when they update them with the new kitkat bootloader. There are some builds by dhacker29 that I have tried that worked but are in progress. You would need to reflash back to JB bootloader to use the official CM11 nightlies.
Click to expand...
Click to collapse
how can i flash back to jb bootloader without bricking ?
edit : got it..

iBolski said:
Not sure why you think you have to rename something to flash a new recovery. Yeah, maybe the instructions had you rename the recovery image file or something, but no. Just flash it per the instructions the previous poster linked to. It's really that simple.
Good luck!
Click to expand...
Click to collapse
i think it is because back in the day, correct me if im wrong, you had to rename the old recovery file so it wouldnt re-install.
but now that development has progressed, that is no longer necessary.
thats why all the, do i need to rename questions are arising.

bweN diorD said:
i think it is because back in the day, correct me if im wrong, you had to rename the old recovery file so it wouldnt re-install.
but now that development has progressed, that is no longer necessary.
thats why all the, do i need to rename questions are arising.
Click to expand...
Click to collapse
yep, that's what I was inquiring about.. all sorted now and rocking the device as it's supposed to be used. thanks.

Please help me! Cant install any ROM on my OnePlus!

Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.

Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this

Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.

Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.

Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?

Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.

Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!