have i bricked it?? - Xoom General

hi, i have been reading up alot today on how to root and install a rom on my xoom, i rooted it fine then i went to the ics thread and downloaded the latest build, v17... put the zip on the sd card and went into recovery mode, choose to install zip from sd and installed it, then went to reboot device and it rebooted but came to a black screen that says android across the middle, its been on that screen for 20 mins now, help please lol
sorry... sorted problem, im guessing its bcos i wasnt installing google apps from zip too, sorry again

Honestly I have run into the same issues...hold down the volume up button + power...your Xoom should reboot.
Then you see the red Motorola logo wait 3 seconds and hit volume down...you should see "Android Recovery Mode" in the upper left corner.
Hit volume up to select....your device should enter recovery mode.
From here wipe data factory reset...wipe cache partition...then go to advanced...and wipe dalvik cache.
Then go to install zip from SD card and reinstall the ROM and Gapps and you should be fine, the first boot can take up to 10 minutes so don't panic...
XOOM Running Team EOS latest ICS build v.17 OC'd @ 1.5Ghz
Sent from my DROIDX using xda premium

Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium

Boarder277 said:
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
No, don't be sorry. That was a great explanation.

I know you got it fixed but I will say this:
Always do a full wipe when flashing a new rom. In this case, the ICS build was a new ROM and you should have wiped.
Usually you do not need to do a full wipe if you are just flashing a new build of the same ROM (if you go to a new nightly for instance). Just need to clear cache/delvik and reinstall gapps.

Related

CM 6.1 Stable

Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com

[Q] Flashed cm7 & getting lots of force closes??

Im on mytouch 4g permrooted s=off,gfree method,i searched through the forums and couldnt find anyone with this issue?? Wiped data,cache,& delvik flashed cm7 and jt wrked fine for about 10 min then everything wss forcd closing,i couldnt open no apps or anything so I pulled the battery out & rebooted then everything happened again so I just flashed back iced glacier anyone had this issue??
I had an issue like that when I first got started, I found that all I needed to fix that was to fix permissions.
Sent from my HTC Glacier using XDA App
Did that then rebooted wrked for a lil bit and did the same forceclosing,i dnt knw whts wrng... Tried last night & then after it did the forceclosing I had to pull the battery then went to clockwork and got all errors couldnt mount cache or data,phone went crazy,but managed to keep playing with it & got it running again on iced glacier,i also have clockwork 3.0.0.6 forgot to put it out there lol..
I know this problem. There is an issue about the permission problem.
1)You turn your phone off
2) hold VOLUME DOWN and POWER switch to go to the bootloader
3) go to RECOVERY (to the clockworkmod recovery)
4) in the cwm recovery, go to the ADVANCED
5) in ADVANCED go to the FIX PERMISSIONS
6) wait until it is finished
7 ) restart your phone and nothing bothers you with crashing.
Did you flash gapps with the cm7 rom? You supposed to flash gapps every time you flash a cm rom. Also, did you do a full wipe? Not just cache and dalvik but a full full data wipe since you're coming from a different rom than cm.
Sent from my CM7 Glacier using XDA App
Yeah I forgot to say that also,i did install gapps also,did the full full wipe,@fosunite ill try that when I get off wrk & let u knw how that goes,thanks to all for the quick replies...
Am I the only one with this issue?????
wiped data,cache,delvik,formatted boot & system,flashed cm7 again,installed gapps,then fixed permissions,then rebooted everything booted fine then went to put my account info,phone started forceclosing everything again and at that point i cant press any apps or anything,always have to pull battery out then wipe everything and flash another rom.... i would really love to use this rom!
That s wierd, did you try without using gapps ? maybe it could be that you downloaded the wrong gapps version which is not compatible for 2.3...
i used that one which was provided with the cm7 download link.
Try this:
When you first boot after installing cm and gapps, let it sit at the google sign in screen. Don't sign in and don't hit skip. Just let it sit for two full minutes while the dalvik is rebuilt. Then reboot from the sign in screen by holding down the power button. Once rebooted, let it sit again at the sign in screen. Then SKIP sign in so you go to your home screen. Let the phone chill again. You shouldn't have any more fcs after that. Sign in to google by opening the market app.
Sent from my HTC Glacier

Savaged-zen(mod) reboots

Anyone else having random reboots in the savaged-zen roms? I've tryed flashing it a couple times used a few different versions of their kernels and I still get random reboots. It also reboots whenever trying to install any apps. If anyone else is experiencing these problems or has a fix. Feel free to comment
Sent from my CyanoEVO 7 using XDA App
you fix permissions?
NewZJ said:
you fix permissions?
Click to expand...
Click to collapse
yeah it didn't help at all.
someone posted this fix in another thread but i have no clue how to do it myself...
"I did a full wipe with Calk's Format All script and installed the RC3 with the SZ gapps from the first post (after a reboot, per an earlier post).
Couldn't install anything from the market or via File Manager. It would download, then hot restart the phone. Found out that the permissions/owner of /data/app (and/or data/app-private) were incorrect. Changed perms to 771 and owner to system.system and now all is well with the world again."
Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app
detcup4evr said:
Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app
Click to expand...
Click to collapse
The problem with that is that it wont boot with out the gapps being flashed. Ill try again doing what you said when I get home tho. Do you think its leftover files from other roms messing it up? Because when I first rooted I was what you would call a flashaholic haha and there is a few folders from other roms on my SD "miui, etc"
Sent from my PC36100 using XDA App
That is what I thought also, but it was a last ditch attempt before giving up and going back to his old nandroid, but the phone booted fine, and I was even able to make calls without gapps.
Sent from my Evo using the XDA app
ive had this issue with cm7...if i flash rom...then flash gapps...and then flast titanium backup
if i dont flash titanium back up it works fine.

a little help, almost there

ok i am learning, i have my bravo rooted now, i have the ginger break on there and all i put the cm-72 nightly rom on the sd card. i booted up with the blue led and held volume down and this is what i got, reboot,boot,system,recovery ,tools and shutdown. how do i get to the sd card for the rom. i dont want to screw up . also is that a stable rom.
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Dr. Orange said:
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Click to expand...
Click to collapse
Yeah, pretty much that.
To answer your other question, yes, that nightly is a stable rom.
I also ported a CM9 release from yesterday over to the Bravo and its working really well in the initial first 24 hours. I'm also an ass who didn't post install instructions either, but they're the same as CM7's which is to install 2nd init, reboot to recovery, wipe data/factory reset, flash rom, flash gapps, reboot. If you're going inbetween releases (like cm7 0605 to say 0610) then all you have to do is wipe cache, wipe dalvik cache, flash rom, flash gapps, reboot.
And if you didn't know, skeevy420 is a freakin' boss and will help with everything you need.
Sent from my Bravo using XDA: Freshmaker

[Q] defy slow unresponsive, cannot receive texts? cm10 build

Apologies if this is in the wrong place. I have read through the guidelines beforehand.
I am a newbie so please be gentle....
I recently bought a motorola defy with cyanogenmod from ebay, the guy explained it ran faster etc and he was a computer wizz.
It has worked fantastic for the past 2 months. it was advertised as a motorola defy +.
It ran out of battery, I charged it then it got stuck in a bootloop. This has happened once before, A pull of the battery worked but not this time.
I scoured the internet and read about the power/volume button to get into android recovery, It said 'cant load cache'
I selected erase data and reboot.
I switched the phone on it came on, put my sim in and wondered why all day I had no calls or texts, no notifications. I started to play with the phone and it was very unresponsive, saying it wasnt responding. lagging touchscreen.
I pulled battery out, left it & started again.
Tried to download ebay app and it says not enough memory.
The phone comes on, looks like its working but is slow, cannot receive texts or download.
It came in original box which says motorla defy. originally on t mobile uk. I have a three sim. The sticker at back of phone under battery says MB525.
I got so confused looking online as there are many differences, red lense, green lense, defy and defy +'s i have no idea what I should do to get my phone back up and running.
The memory card in it is an 8gb.
This is the information you get when you go into 'about phone'
Model Number : MB526
Android Version : 4.1.2
Baseband Version: EPU93_U_00.60.03
Kernel Version:2.6.32.60-jellyX [email protected] #8 Thu Feb 21 00.25:47 CET 2013
CPU : ARMv7 Processor rev 2 (v7l)
Memory: 476 MB
Cyanogenmod version : 10_20130216_UNOFFICIAL-mb526
Build date: Sat Feb 16 20.56.42 CET 2013
Build number : cm_mb526-userdebug 4.1.2 JZ054K eng.frank.20130216.205551 test - keys
I have read so many posts, so many guides and watched videos on you tube, Iv downloaded some files but because of reading info such as cannot go back/downgrade im scared to do anything.
So my question to you skilled people is what do I need to do to get my phone back up and running again. what has happened is it a bug?
There doesnt appear to be any back up on the sd card? It wont let me download anything even though Iv wiped it?
Please may I have some simple, step by step instructions on what to do. I am not a whizz but am good at following instructions and basic pc.
You guys are absolute clever monkeys! I really hope someone can help.
The model number on the phone (on the sticker under battery) says mb525 and the same on the box. Is it the mod that has made it show mb526 in the about phone section under settings tab.
This is where im confused and scared about what to download or how to apply these to my phone!
There seems to be so many variants for example in the guide it talks about lens colours etc! im bamboozled!
When I press power and volume i get the android recovery. The message at the bottom says
E:can't mount CACHE : recovery/command
E:can't mount CACHE : recovery/caller
E:can't mount CACHE : recovery/log
iv wiped cache partition it says :
--- wiping cache.... Formatting CACHE .......... Cache wipe complete.............
E:Can't mount CACHE : recovery/log......
Iv wiped data it says :
Formatting DATA.................................... (lots of full stops!......)
Data wipe complete.
E:Can't mount CACHE: recovery/log
If I apply sdcard : update zip it says :
Install from sdcard..
finding sd card...
opening update package...
verifying update package...
..E..failed to open / sdcard/update.zip (No such file or directory)
E: signature verification failed
..
Installation aborted..
E:can't mount CACHE : recovery/log
So it appears I have no back up installed to save from.
Many Thanks & Kind Regards
If anyone can point me in the direction of files (that are a valid link) and a step by step of getting my phone back up and running I would be made up! I mss my defy
Can you enter custom recovery? I mean when you switch off your phone and back on, does blue led appear after about 4-5 seconds?
Sent from my MB526 using xda app-developers app
hiya thanks for reply, yes it does flash blue
Hi thanks for your reply. Yes blue led for a few seconds then straight to a red led whilst cyanogenmod loads this goes on for a while, it used to be very quick.
So download the rom you want to use, copy it to your sdcard, and flash it via recovery (press volume down when blue led comes on, select twrp recovery, install zip, wipe data and cache)
Since you are using a jelly bean rom, forget about model/green lens/red lens. Everything will work just fine
Sent from my MB526 using Tapatalk 2
thekguy said:
So download the rom you want to use, copy it to your sdcard, and flash it via recovery (press volume down when blue led comes on, select twrp recovery, install zip, wipe data and cache)
Since you are using a jelly bean rom, forget about model/green lens/red lens. Everything will work just fine
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for your reply!
Based on the build I was running which ROM do I go for? Any chance of a link pretty please?
If I follow your suggestions with sd card & ROM does that eliminate the need for the 'lite' software & gapps that I have read about?
Apologies for silly questions but Id like to be sure of what I am doing.... hehehe! Id like to come out of the bricked defy tunnel smiling
I have to say before my defy had its woopsie everything worked fast and like a dream
massive thanks again
Totally your call. You have options from 2.3 to 4.3. All links are in the development section. You will have to use lite gapps for roms after 4.1
Sent from my MB526 using Tapatalk 2
thekguy said:
Totally your call. You have options from 2.3 to 4.3. All links are in the development section. You will have to use lite gapps for roms after 4.1
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Massive update!! I have just been playing and pressed volume down when blue light on as you said and discovered a different recovery menu than the one I got a few days ago... I presume the first one was stock recovery??
So I wiped cache and then data reboot and I can now receive text messages, I can now download ebay app again (before it said not enough room)
So fingers crossed we are working. with MASSIVE thanks to you!
So my question now is.... As I am running a February 2013 build should I update to a newer or stay as I am?
Definitely update, newer builds are better
Sent from my MB526 using Tapatalk 2
thekguy said:
Definitely update, newer builds are better
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
hmmm i must say I am very impressed with all that goes on on here, i never realised what was behind the 'mod' on my new little superstar phone
So as I am a newbie I am unsure about the whole clockwork recovery etc so before I update anything how do I back up what is now eg I know it works....
In your wisdom which build should I go for? would it be a download it, put it on sd card and install from sd card as per your last instructions?
I have just put rsdlite on my laptop... So whats the gapps for & how do I put them on?
No worries if you havent the time to answer such daft questions, Im just a bit baffled when I read the pages as there is so much development I dont know what to follow... hehehe if there is clear instructions give me the link & I shall read
Massive thank you again for your time & patience I admire all the work that everyone does on here!
My last instructions should work, although you have to select clock work mod. (For twrp later on, doesn't apply to cwm) just wait for about half a minute when you enter recovery before going anything. Sometimes the recovery just crashes, so if you wait it out then you'll be on the safer side.
To backup your data: in upgrades of the same rom. Backup with titanium or others, and flash+ wipe cache. If it hangs on splash screen go back to recovery and wipe data+ cache, and restore using your application.
For different roms backup using the app and wipe data and cache after flashing and restore later.
As for the build: go for the latest of whichever rom you choose. FYI, Bluetooth headset audio doesn't work for 4.2 and above
Sent from my MB526 using Tapatalk 2
thekguy said:
My last instructions should work, although you have to select clock work mod. (For twrp later on, doesn't apply to cwm) just wait for about half a minute when you enter recovery before going anything. Sometimes the recovery just crashes, so if you wait it out then you'll be on the safer side.
To backup your data: in upgrades of the same rom. Backup with titanium or others, and flash+ wipe cache. If it hangs on splash screen go back to recovery and wipe data+ cache, and restore using your application.
For different roms backup using the app and wipe data and cache after flashing and restore later.
As for the build: go for the latest of whichever rom you choose. FYI, Bluetooth headset audio doesn't work for 4.2 and above
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Massive thanks for that I had been looking at the tiranium app... Phone is behaving at mo, sometimes a little slow but hey its working so I will take all you have said onboard & try to update to a newer version ROM.
Could you just explain what the first paragraph means in your reply.... 'select clockwork mod.. (for twrp later on, doesnt apply to cwm) please! thanks !
The remaining part of the paragraph is relevant to twrp recovery, which you will get after installing one of the recent builds
So, as of now ignore the part of the paragraph after the brackets
Sent from my MB526 using Tapatalk 2
thekguy said:
The remaining part of the paragraph is relevant to twrp recovery, which you will get after installing one of the recent builds
So, as of now ignore the part of the paragraph after the brackets
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
cool okay massive thanks I shall have a go over next few weeks thanks again. Have a top day

Categories

Resources