I was attempting to apply a backup to my xoom 3.2(rooted) and, after i saved the back up to my SD card. I did a factory reset (suggested by Google because of a market error i was having). After i booted it back up and went through the google services i downloaded rom maneger and tried to restore. Booted up, got stuck on dual core, and the dual core symbol jumps around the screen.
Clockworkmod is fully accessable so hopefully there is hope, whenever i attempt to restore it says /system error.
I've factory reseted and that didn't help(<---- Thats why i'm worried)
Do i just need to download a stock image and apply that?
Please get back to me, I'm in first period now and i have a reaseach paper due in 4 hours i really need my tablet.
You should be able to download stock images from motodev as per this thread : http://forum.xda-developers.com/showthread.php?t=1108505 and flash your Xoom back to normal using fastboot.
Its the best way to solve your problems, the only downside being that you'll lose whatever you had on the tablet (unless you synced your stuff with Google).
Good luck there !
Thank you !
Do you get a system error when trying to do a factory reset? Like does it say it can't wipe data?
Sent from my Xoom using xda premium
Related
hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up
Hello everyone, this is my first post on your web site. I have spent the past 6 hours nosing around xda's web site trying to find a simple straight forward answer. Heres my situation, I unlocked the boot loader and installed tenfar cwm. I re-booted my phone and everything was fine. I then continued to download the gingerblur .zip file and copied it from my pc to my atrix on the internal sd card. I shut my phone down and went into android recovery and created a backup of my current oem rom right after I gained superuser access. I assumed it created the entire back up since it was date and time stamped as this website said it would. I then re-booted my phone and went back into recovery and installed the .zip gingerblur file from the recovery program. Once I did that it installed through the recovery program and gave me an option at the top of the recovery program to install from internal sd, install from external sd, or back. I selected back and kept clicking back until I got to reboot the device. Once I clicked reboot the device from android recovery mode my phone went to the dual core screen and stayed there for approximatly 45 minutes before I pulled the battery. After that I can not get past the dual core screen. I have "unlocked" still displayed at the top left corner of my screen and I used the automatic unlock script to re-install tenfor cwm. I cleared all of the cache, data and tried to restore my phone from the backup I performed earlier... it says it successfully loaded the boot load image but all of the other images it gives errors. Needless to say I have a phone with essentially no operating system. I read a thread on XDA's website stating it could be a problem with the version of cwm I am using and with that there is a link to another thread stating to download a recovery.img file and flash it through fastboot. I can not find out how to flash it through fastboot. Any help from anyone would be greatly appreciated. I am sorry this is so long, but I would rather someone trying to help me have the whole story then just a portion of it. Please help me!!!!!! Thank you for taking the time to read this. My question is simple, how do I get my atrix back to the state it was in before I decided to try to install a gingerblur rom.
I've fixed this problem by wiping everything and installing a fresh copy of gingerbread 4.5 beta. Up and running again!!!
Sent from my MB860 using XDA App
Hey,
Rooted my Galaxy Tab plus, then backed it up with TB, then tried to transfer the backup to the external sd... which didn't work. I then very precisely (I thought) followed the instructions for creating permissions to write to the external sd, and as per those instructions, rebooted.
And so my Tab has. Rebooted, and rebooted, and rebooted, and rebooted.
I've got it in recovery mode at the moment... but does anyone know how to get this thing out of circular reboot mode? I'm leery of doing a factory reset from recovery until I know if that will have the desired effect--mainly, getting me back into my Tab. I have the stock firmware and ODIN, if that's what's needed. I just need some advice on which is the best to try.
Or, if there's an altogether different solution, then please share...
This may not be useful to solve your problem. However, FYI,...
I was able to applied the permission mod previously, and afterwards, I did a factory reset. It did not remove the permission mod that I applied. That is, after the reset, it was still able to write the the external SD even though all my data and apps were gone.
So chances are the factory reset is not going to solve your problem.
factory reset doesn't mess with the system partition - it basically just wipes the /data partition. So it won't fix your problem.
If you have ODIN, just find a replacement image and re-image the device.
garyd9 said:
factory reset doesn't mess with the system partition - it basically just wipes the /data partition. So it won't fix your problem.
If you have ODIN, just find a replacement image and re-image the device.
Click to expand...
Click to collapse
I initially downloaded the stock firmare for the US version, after discovering for myself that doing a factory reset from it's semi-bricked state did no good. The original firmare download was somehow incomplete; it reached an "unexpected end" while extracting and so would not work in ODIN. Then my Tab wouldn't connect to the computer I was using at all.
Fortunately, I was able to re-download the firmware and use ODIN on another computer, so I was able to get back to stock. Even after that, however, I had to do a factory reset; for some reason, my Tab downloaded the first update from Samsung, but would not make the leap to LA3. Once I did the factory reset, though, all was well.
Then, of course, I immediately re-rooted and manually made the changes that let me write to the external sd--correctly, this time. No trouble at all on reboot.
Thank God.
I rooted my phone and replaced all kinds of things and a installed a new launcher, but the startup time was unbearable. I let my friend tinker with it, and from the SuperMaid app, he apparently froze the Android OS (I guess he thought my launcher was an OS) before I had a chance to back anything up with Titanium. When the phone died, it won't of course won't load. It's a Samsung Mesmerize, so I have the the one file from ClockModRecover, and that's it. I tried to restore that file, and it won't. Is my phone bricked? I'm kicking myself for all of this.
Well...did you install clockwork mod recovery? Not the manager app in android, but the actual recovery? If so, did you do a nandroid backup? If you did, restore it. If you never bothered to do a backup but do have cwm recovery, do a factory reset. If no cwm then last thing is boot into normal recovery and try a reset from there. You will likely lose root, and will need to root the phone again, and keep your friend out of your OS.
Tapatalked from my A100 - Flex Reaper RF1.
recovery isn't working
When I tried to restore the nandroid backup, it repeatedly failed saying it couldn't (I can't remember if it was mount or unmount) the system. So I did the factory restore as you suggested, and when I turned on the phone, I received a text message. However, I'm getting a force close message that's preventing me from doing anything: "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly...") When I click Force close, it just pops right back up, cutting off functionality of the phone.
Ok reboot back into recovery, wipe cache, go to advanced, wipe dalvik, fix permissions, reboot.
Sent from my LG-P999 using Tapatalk 2
didn't work =(
I did all those things and the system repeatedly wouldn't unmount. I had to just go back to Froyo 2.2 with Odin. The good news there is now I can install Ice Cream Sandwich. I figure I can't do too much damage, and if I do, I still have the backup
I said to reboot not restore or flash, but I'm glad you got it all figured out. The fix permissions and caches being wiped was to try to fix the current install, not prep for a new rom or restore. At least I assumed flash or restore since you mentioned system not unmounting which only happens for that.
Sent from my LG-P999 using Tapatalk 2
Sent from my LG-P999 using Tapatalk 2
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden