I rooted my phone (at a friend's house, I'm all Apple unfortunately) and all was well and good until I purchased Rom Manager and tried to download MIUI. Since then it goes through the MIUI United Worldwide splash screen infinitely. I went the rom manager route instead of manually installing in the hopes that i wouldn't fail. But here we are.
Pull the battery and hold power and volume down and boot into recovery from there and manually wipe everything and reinstall the ROM
Sent from my HTC Inspire 4G using XDA Premium App
Thank you for the speedy reply! as far as wiping everything, im in clockworkmod recovery v3.0.2.6. , should i wipe everything through this? I'm coming from the jailbroken iphone world so I am a tad new at this. Mostly just following steps right now.
all has been solved, thanks again. (if anyone is curious, wiping cache and data fixed it.)
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
so I bought this MyTouch 4g from this guy at my job. He rooted and messed up some things (deleted important files i guess), and as I'm using the phone I get random force closes on certain applications. Turning on the phone takes forever, Loading pop up stays up for about 5 minutes before the homescreen is actually completely loaded. Sense Widgets are gone, when I try to load them, htc.RosieUtility.com has to force close. Email app force closes as well. When I try to recovery boot (Volume + Power), I get a ClockWorkMod screen.. which I am 98% sure is not stock.
He admitted himself he messed it up, so I bought it pretty cheap from him , but is there any way to reset EVERYTHING to factory settings, even though he deleted some things when he rooted and got into the system/app?
I could be wrong but try:
Home > Menu > Settings > Factory Data Reset
Unless you are comfortable with flashing a new ROM to the device.
Your right in thinking clockworkmod is nothing to with stock. But this is good. If he has messed up by deleting important apps and files the easiest way to solve this is to flash a new rom. Head over to the my touch 4g forums find a rom you like the look of download it to your memory card. Boot in to recovery, wipe data, wipe cache, install zip from sdcard and flash your new rom. This should solve all your problems and you will have a clean slate to start from.
I wouldnt worry about unrooting, i have heard of people Paying more for second hand phones that have been rooted. How ever if you did want to take it back to stock im sure there will be a guide in the my touch 4g forums
Sent from my HTC Vision using XDA App
try this out, there is a link above the 2nd video http://www.droid-life.com/2010/06/14/how-to-root-and-unroot-the-droid-incredible/
Hi,
I have a Nexus S I9020T, rooted and running MIUI.
Today I rebooted my phone (after applying a new font via Font Changer), and it got stuck at the Google logo.
I have tried rebooting via fastboot, to no avail. I have also tried pulling the battery several times. I have even tried doing a full wipe and restoring a Nandroid backup that I made via ClockworkMod after it got stuck, but it still refuses to go past the Google logo.
Can anyone please suggest something? Thanks so much.
Edit: I forgot to mention that the device was plugged into the computer at the time, and I am not sure whether or not the SD was mounted. Could this be the cause?
If SD isn't mounting you wont get past the Google logo. See if it is mounted in recovery
Sent from my Nexus S 4G using xda premium
I bet if you reflash the original miui rom you were on you'll be good to go. Sounds like the font package messed up the miui system. Good luck.
And no need to wipe most likely. I've bootlooped my miui applying themes and such and just reflashed with no wipe and good to go.
Sent from my Nexus S 4G using Tapatalk
Well it all started when I downloaded Boot Animations ★ root. I tried to install a bootanimation and it said failed. Thinking nothing happened , I had to restart my phone. Now my phone bootloops with an android bootanimation. I tried factory reset and that didnt work. I tried adb sideload and it would just say installation aborted. I have the system backed up on my laptop. Help... please?
Well.. Power +Up Button =recovery but Power+down button= testing (its in chinese)... how do I get to bootloader?
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
terris98 said:
Go to android recovery,
Format system, wipe cache, go to advanced, wipe Dalvik cache, reboot.
If that doesn't help, try slamming your phone through a piece of China brick, see if it helps.
Sent from my LG-E730 using xda app-developers app
Click to expand...
Click to collapse
LMAO Well.. The only way to get my phone back working is through Preloader but it connects and disconnects. I tried different cords and computers but nothing worked. It's really a big mistake I did. I should have installed a custom recovery and did a backup right after I rooted my phone.. Anyways.. I'm getting a different phone soon.
Chinaphone wont boot
Thanks to xda for all the help and I hope you can help me with this problem. My Chinaphone won't start, it gets to the android boot animation and sound but then nothing. The led comes on from the time the battery is inserted which is unusual.
I have the phone for about one year now, model:M-9125 (imitation of htc hd7) with dual Sim+TV and everything else that come with Android 2.3.4 gingerbread. The phones is rooted (with the MT6573 driver- and i use link2sd so everything except un-updated system apps are on the second partition. I have modified the rom with link2sd removing unwanted system apps like email, flashlight, music, browser and replaced them gmail/outlook, tinyflashlight, winamp, opera mini respectively. Tinyflashlight and opera were made system apps. I also use the go launcher which I made a system app after which I was left with only 1.5 mb of rom, (ram about 300 mb and both sd card partitions have over a gb free) but the phone worked fine. Then a few days ago the phone wont start. I thought the battery was dead but it could not charge. I tried both batteries (came with two, one of which was already drained) and they would not charge. So a friend took them to charge with a universal claiming that I Let the batteries drain out completely that's why. However I have the batteries I think they are charged cause at least now the led comes as soon as the battery pins contact those of the phone. The phone turns on, boot animation, sounds but then nothing. So I just wanted to know if its the batteries or if its the phone given that I have over-customized it. And how do I fix it.Cannot afford a new phone right now.
I know I am a noob and read your rules but I still really wants sure where to post this. feel free to move it if necessarily. thank you.
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