Hey guys,
This is my very first post, just to let you all know, so please have some patience! Thanks!
Anyway, so I have a Nexus S 3G (Canada) and I have rooted it, unrooted it, installed roms and everything. I works...for the most part. It's giving me all sorts of different little errors and what not. So I was wondering, how can I COMPLETLY start ALL OVER, as in, factory new, like when you buy a new phone (without the carrier stuff). I wanted to start fresh, fresh out-of-the-oven kind of start, do you understand what I mean? FACTORY FRESH. Thank you all so much in advance!
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
[email protected] said:
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
Click to expand...
Click to collapse
Thanks for the reply, I've already done that, and I'm still getting errors and other weird things, like not going out of airplane mode, failing to download the OTA 2.3.6 Update (I'm on stock 2.3.1 unrooted, I think), and I don't know if this is normal, but ClockworkMod Recovery is still there. Am I still rooted or something? Plus, when I try to flash a restore, from let's say Gingerbread 2.3.6 Stock, it says MD5 mismatch! How about if it's an ICS AOSP Build, it gives me the normal white Google logo like normal, but then just stays stuck there.
Is the anyway to erase EVERYTHING and start over like NOTHING was ever done to the device? Like when they are first distributing the the device and no one has ever touched it? Is there anyway to do just that?
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
lodxcol said:
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thanks for your excellent reply, but I have also already done that, EXACTLY that, multiple times too. Dalvik, battery stats, factory reset/delete all user data, wipe cache partition and fix permissions. What else is there left to do?
Thank you all so very much!!!!
I have fixed my Nexus S!!!
HeroKhar said:
I have fixed my Nexus S!!!
Click to expand...
Click to collapse
how did you fix it?
lodxcol said:
how did you fix it?
Click to expand...
Click to collapse
I reinstalled the newest update with the vanilla recovery
Sent from my Xoom using XDA Premium HD app
Related
Does anyone have the htc phone.apk??? i accidentally and very stupidly deleted mines from my system applications using root explorer. i cant make calls without it.
chrisw491 said:
Does anyone have the htc phone.apk??? i accidentally and very stupidly deleted mines from my system applications using root explorer. i cant make calls without it.
Click to expand...
Click to collapse
if you have a custom rom, either flash the Nandroid back up or else Flash a new rom or else you can strip a rom of the Phone.apk file
ok i have a MAJOR problem. im kind of a noob at this stuff so im still learning. i was messing in my system files trying different phone.apk. i think i may have deleted something essential. when i turn my phone on it doesnt get past the boot animation. my phone was rooted with unrevoked 3. but everytime i try to install a new rom using clock work recovery, it gets to the part where it "opens update pakage" and just stops and goes back to the first menu screen of clockwork. i dont have a nandroid backup either so i cant even restore.
chrisw491 said:
ok i have a MAJOR problem. im kind of a noob at this stuff so im still learning. i was messing in my system files trying different phone.apk. i think i may have deleted something essential. when i turn my phone on it doesnt get past the boot animation. my phone was rooted with unrevoked 3. but everytime i try to install a new rom using clock work recovery, it gets to the part where it "opens update pakage" and just stops and goes back to the first menu screen of clockwork. i dont have a nandroid backup either so i cant even restore.
Click to expand...
Click to collapse
try wiping the phone in the recovery, wipe everything then install a new rom, sometimes not wiping screws up the installation
Diamond_dawg said:
try wiping the phone in the recovery, wipe everything then install a new rom, sometimes not wiping screws up the installation
Click to expand...
Click to collapse
yea i tried wiping the cache and wipe data/factory reset but I still get the same results. im willing to try anything.
chrisw491 said:
yea i tried wiping the cache and wipe data/factory reset but I still get the same results. im willing to try anything.
Click to expand...
Click to collapse
try posting this in the Evo forum, they will help you better
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
King350z said:
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
Click to expand...
Click to collapse
Lol I think you over clocked it on the minimum ... try the minimum at 800m ... or if anything flash a new rom.. its probably the rom itself
Sent From In between Your Moms Boobies
Try another (stable) rom? (no development rom)
Wipe everything.
And yes, probably its underclocked/overclocked too high.
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
King350z said:
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good news, you flash your ROM from recovery. Download the package, boot into recovery. Mount the SD card and push or push using adb push. Flash the zip from CWM.
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
3mar84 said:
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
Click to expand...
Click to collapse
Wipe data/factory reset from recovery if it's a used phone.
If he just bought it return it... thats easy
If he rooted it and changed the rom -- put it back to stock or put a new rom on it
I personally found that most of my restarts were due to me trying to pull the stock launcher into an unfamiliar rom. Make sure (if you are using Titanium backup) to only load apps not system *unless you are trying to go back to the same rom*
good luck
First check if he overclocked too much or underclocked too much. Put it to normal.
Alternatively you can just flash another rom. Before flashing remember to wipe everything
Goodluck!
I recently bought a nexus s and once rooted the keyboard dissapered. It was fine until i flashed a rom unsuccessfuly, then turned the phone off. Once turned back on the keyboard was no more. If anyone could help me find a zip. to flash or a way to put a new keyboard on the phone I would appreciate it. the phone is basicly useless without the keyboard now, ive tried recoving to factory condition, flashing from an earlier point, and so forth. Please help!!!
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
jojoost said:
You probably didn't flash gapps, you can find them on www.goo.im
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Billchen0014 said:
i never knew keyboard was in Gapps, i thought it's included in all ROMS since its absolutely necessary as the OP stated.
here is a dump
UPDATE: uploading
Click to expand...
Click to collapse
Dictionary http://db.tt/3echUtSP and IME: http://db.tt/EUAXXcsR
re: i flashed gapps
Sent from my Nexus S using Tapatalk 2[/QUOTE]
I flashed a gapps zip from the site you linked me to and now when the phone turns on it says setup wizard is not responding and give me the option to force close. Nothing happens from that point its just stuck in a force close loop. I hope to god i didnt brick this thing. Is there a way to fix this problem? I didnt backup before flashing gapps and ive tried to restore the phone and wipe it clean but no luck. Any help would be greatly appriciated because i just got the phone, mainly to use it as a fun project seeing as smartphone customization has become my new hobby, and Im usually very good at it but now I am just afraid ive bricked the phone and I bought it unlocked so i paid a fair amount of money for i. Please help if there is a solution. Thank You,
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Thank you
Oogway13 said:
Do you still have access to CWM? Can you make a clean install of any ROM? Wipe dalvik, cache, factory reset, format boot, system, data, cache and install ROM.
Download another ROM (and follow instructions from OP) which is not the one you initially had problems with (or download again - might be a corrupt zip file).
Click to expand...
Click to collapse
Thank you very much, I followed and executed your instructions and now im running ice cream sandwich 4.0.4. not bad from going from almost a bricked phone to running one of the best versions of android. I downloaded offical roms this time instead of custom ones, first a version 2.3.4 and a 4.0.3, flashed the ics rom first and worked like a charm. Thank you very much, even got an update 5 min after i flashed the rom. You saved me 200$ and the embaracement of having a worthless phone. Im sure ill have more questions in the future, so glad there are ppl out there with the same passion for smartphone customization that i have. Much obliged. Omar
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Shamrock13 said:
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Click to expand...
Click to collapse
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
MrMeester said:
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
Click to expand...
Click to collapse
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Ya, cm 10.1 has better bat life. I liked liquidsmooths settings better though. Carbon doesn't seem to be as stable atleast for me. But it seems like no one else is having the problems I'm having. I recommend twrp recovery. Run it, see what you think. PM me if you need help.
Shamrock13 said:
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Click to expand...
Click to collapse
Yes you are right, it is the update one.
Sent from my DROID RAZR HD using Tapatalk 4
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Shamrock13 said:
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Click to expand...
Click to collapse
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
I took an xt 925 today, but i have some knowledgment from my Razr I, which is + - the same procedure/flash.
I want to install some custom roms, so basically all i have to do is unlock my bl, install a custom recovery and try out?
I'm asking that, because i'm on jelly bean, but its a carrier based firmware, and i dont know if this model got any limitation which break me up.
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Shamrock13 said:
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Click to expand...
Click to collapse
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
The thing is, I couldn't get back into recovery at all. I had to try like 50 times holding down the buttons to finally get it to even boot to the recovery select screen, and even then it wasn't a sure thing if I were going to get it to boot into recovery. I flashed another ROM, and it still didn't work. I read on the Droid forums that you need to mount system first and then flash, so I tried that and my phone booted up right away.
was kicsnia
mentose457 said:
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
Click to expand...
Click to collapse
Yeah, the brave little toaster! Old school and under rated. Ha ha!
Disable Moto Services. No root, no unlocked bootloader needed. You will never see any update nagging. Even when you turn off/on your phone.
Sent from my DROID RAZR HD using xda app-developers app
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....