Database Info

[Resolved] [Q] I've made a mess of my Nexus S...

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

[Q] Unrooted stock bootloop - need help

Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?

iglu said:
Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?
Click to expand...
Click to collapse
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.

And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
You think it might be a result of ICS upgrade ?

iglu said:
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
You think it might be a result of ICS upgrade ?
Click to expand...
Click to collapse
Yes factory data reset only deletes all data on your phone not the SD card.
Sent from my Galaxy Nexus using xda premium

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
Okay, so i did factory reset and i'm still stuck on the bootloop. Need to remove the battery and turn back on until it doesn't bootloop.
Actually what happens is the google logo appear, then for a moment it turned off and comes back again.
simms22, why do you think it's internal sd damage ?
TheMatrix246, what's ODIN ?

Guys, you think if i root and switch ROM it could be fixed ?
I would appreciate some help here a bit lost.

One last thing before you contact Samsung:
Download Nexus S [i9020T/i9023] 4.0.3 Full ROM and copy to sdcard as update.zip
Go into bootloader
Recovery
Data/factory reset
Install update.zip (reflash all files of ICS)
Reboot and hope it works out fine
If this doesn't work for you i highly doubt rooting and changing ROMs will. This will reinstall the entire OS (format and install /system), bootloader, radio, kernel and recovery.

Do i need to be root user in order to do that ?
And just to make sure, this Full ROM is for i9020T ? correct ?
(mine says only GT-i9020 on the back, bought in Carphone Warehouse in England).

Yes, i9020T. If you get 3G with Orange, and you have the SAMOLED screen, you have the i9020T (and to my knowledge, 9020 on the back signifies i9020T).
Also, i don't believe you need to be root to do that. I'm pretty sure you can flash the same version ROM from stock recovery as long as it is signed, just not older versions.

First, thanks guys for the help.
After first doing the factory reset, it seemed the bootloop happens less often. At first i tought it was solved but then it rarely (1 to 5 reboots) yet happened.
Today i installed the Full ROM Harbb suggested and so far i have no reboot issues.
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?

iglu said:
First, thanks guys for the help.
...
...
...
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?
Click to expand...
Click to collapse
You're welcome. Also, all that file does is replace everything in the /system partition (OS). All apps besides the defaults that come from the factory are not in that partition so are not affected. Hopefully your problem is fixed permanently

But it's generally recommended to do a full wipe when switching ROMs. It could be that you encounter other problems because of the ROM change without wipe. But you could also be lucky to have no problems. Just to remind you, when you encounter something wierd.

Problem is still there ....
Hi guys,
First thanks for all the help, but the problem still there.
I did the upgrade using the Full ROM as Harbb suggested. For the first 10-12 times i rebooted (i rebooted again and again) it was alright, booting successfully ... but then it stated occasionally to bootloop and now it does it almost everytime. usually takes up to 10 times i remove the battery and start the phone so it will start up and not bootloop.
Also, I'm sorry the taking so long to respond, the nature of the problem compelling me to test it for a few days so i will know if it works or not.
Should i root the device ?
If so , how do i replace / rewrite the boot program ?
I would much appreciate any suggestion.

I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.

BlatDinger said:
I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.
Click to expand...
Click to collapse
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?

iglu said:
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?
Click to expand...
Click to collapse
Most likely its a refurbished one, as is the way of sending devices for warranty
Sent from my ice cream powered Nexus S

Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium

BlatDinger said:
Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hey, thanks for the replay.
What does is mean to flash it ?
How do i do that ?
You noted it was returned unrooted, was it rooted before ?
Again thank you all for the help.

To be honest I'm a novice to these terms but know that they unlocked it(it was not unlocked when sent off) and reinstalled os 2.3.3 after a complete wipe. Details of how to unlock and flash (install a different os) are on the forums. If you follow the forum advice precisely the instructions work. I am now running a CyberGR rom of ics 4.0.3 that runs smoother than stock ics . Again found on these forums. Hope this helps.
Sent from my Nexus S using xda premium

Who still has the "Turning Off" problem and who solved it?

After my phone got back from repair I had the "phone turning off" bug, I tried almost everything but can'T solve the problem at all. Who else suffers from the problem and who solved it so far?

What android version are you on I thought it was fixed with gb
sent from my acidhazard thrill

no, the problem started with gb, the reboot problem was on froyo

Ahh I thought that's what you meant my phone has never shut off
sent from my acidhazard thrill

Have you ever used overclocking?
Are you on a custom rom or on stock?

GentlyCriminal said:
After my phone got back from repair I had the "phone turning off" bug, I tried almost everything but can'T solve the problem at all. Who else suffers from the problem and who solved it so far?
Click to expand...
Click to collapse
I have the problem on both froto and gb, and drain battery when the problem occur, i really want to know if there is a solution
Sent from my LG-P920 using XDA

Mostly when I get into that problem, I'll backup all my application+data and wipe factory reset the phone and fresh install custom firmware. Then restore app and certain important data only such as contacts, sms etc.

cyclonmaster said:
Mostly when I get into that problem, I'll backup all my application+data and wipe factory reset the phone and fresh install custom firmware. Then restore app and certain important data only such as contacts, sms etc.
Click to expand...
Click to collapse
I have the problem no matter which rom i have used
Do you think the problem the setting related! ? i think it is hardware related
Sent from my LG-P920 using XDA

Suck, i have lost 25% of battery when i encounter this turning off problem again!! plx help, should i sent back the phone to lg !??
Sent from my LG-P920 using XDA

things really get crazy somehow ! as i was sure that the problem was hardware related, I remembered that the phone never shut down on froyo, so I downgraded to 2.2, but no matter to which version i revert back, I just don't have signal !

GentlyCriminal said:
things really get crazy somehow ! as i was sure that the problem was hardware related, I remembered that the phone never shut down on froyo, so I downgraded to 2.2, but no matter to which version i revert back, I just don't have signal !
Click to expand...
Click to collapse
How did you revert back your ROM? And how do you do an upgrade? Is it by flashing .zip from recovery of by KDZ method? If by .zip from recovery I believe you did it wrong since ding it that way is not include flashing baseband.
Wipe dalvik cache, Wipe battery stats, wipe cache partition and full wipe/factory reset from recovery. Then flashing.
Proper method to upgrade/downgrade is using KDZ method: http://forum.xda-developers.com/showthread.php?t=1287236
It will install the ROM and the baseband. After that don't restore any application yet. Check it first, is it still shutdown? Is it still no signal? Is it still have battery drain problem? If it is, then it's a hardware failure. Send it to LG Service centre.

cyclonmaster said:
How did you revert back your ROM? And how do you do an upgrade? Is it by flashing .zip from recovery of by KDZ method? If by .zip from recovery I believe you did it wrong since ding it that way is not include flashing baseband.
Wipe dalvik cache, Wipe battery stats, wipe cache partition and full wipe/factory reset from recovery. Then flashing.
Proper method to upgrade/downgrade is using KDZ method: http://forum.xda-developers.com/showthread.php?t=1287236
It will install the ROM and the baseband. After that don't restore any application yet. Check it first, is it still shutdown? Is it still no signal? Is it still have battery drain problem? If it is, then it's a hardware failure. Send it to LG Service centre.
Click to expand...
Click to collapse
Man nothing against you, I know you wanna help, so thx for that, but I'm trying to get advanced help, all these common things aren't any problem and I know almost everything about them. I am asking if anybody succeeded to get rid of the shut down problem and if anybody else had signal loss after reverting back to froyo ? And the main reason why I started the thread, is because I know that there was the reboot issue on froyo and the shut down problem on ginger and this was a serial bug

Can't access media anymore

So I'm not sure when this happened, but I can't access the media on my internal storage anymore. For example, all the songs I've moved to my phone or my pictures I've taken. If I mount the phone in recovery, all the files are still there. When I just plug the phone into the USB (not in recovery), the internal storage comes up, the space is taken up, but the files aren't there. It's weird its like the phone can't access the internal storage when its not in recovery.
I'm S-OFF
Hboot 2.14
latest Viper XL
latest Elemental X kernal
I have been getting android.media.process errors since I upgraded to the latest Viper XL, tried all sorts of fixes like reflashing to no avail. But even while those were going on I could still access my media
Everything was working fine for a while, I'm honestly not sure when this happened. Any help would be appreciated.

Are they correctly named? Like .jpg for pics and such?
Sent from my HTC One XL using XDA Premium 4 mobile app

pandasa123 said:
Are they correctly named? Like .jpg for pics and such?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't touched the names of them. It looks like it. Basically the internal storage looks different if I just plug in my USB ->My Computer -> internal storage vs if I go to recovery -> mount -> My Computer -> explore the phone

When you upgraded did you do a clean flash?
Sent from my Evita

timmaaa said:
When you upgraded did you do a clean flash?
Sent from my Evita
Click to expand...
Click to collapse
During the Viper installation it gave me the option to do a wipe with installation, and I did that.

Ok, but did you wipe everything? The media force closes suggest a dirty flash possibly.
Sent from my Evita

timmaaa said:
Ok, but did you wipe everything? The media force closes suggest a dirty flash possibly.
Sent from my Evita
Click to expand...
Click to collapse
I remember initially when I was researching the problem, it sounded like a few people got it when they upgraded HBoot and the new ViperXL. It was suggested to just reflash Viper, when that didn't work I did do a factory reset. I'd prefer not to do a factory reset at this point but I will if I have to/when I have time.

Don't do a factory reset through bootloader, that'll corrupt your sd card. If you didn't do a factory reset in TWRP when you flashed the ROM I can't almost guarantee that's what is causing your problem. The correct protocol when flashing a new ROM is to wipe cache/dalvik cache/factory reset/system. Especially when coming from a different base / Android version, which you were.
Sent from my Evita

timmaaa said:
Don't do a factory reset through bootloader, that'll corrupt your sd card. If you didn't do a factory reset in TWRP when you flashed the ROM I can't almost guarantee that's what is causing your problem. The correct protocol when flashing a new ROM is to wipe cache/dalvik cache/factory reset/system. Especially when coming from a different base / Android version, which you were.
Sent from my Evita
Click to expand...
Click to collapse
Could it cause an issue with my media a few weeks down the line?

style2burn said:
Could it cause an issue with my media a few weeks down the line?
Click to expand...
Click to collapse
I'm not disagreeing that there was probably a problem with the flash, but anything less than a factor reset reflash would be nice.

I don't think you have another option. Why the hesitation? I always clean flash and it only takes me like fifteen minutes to set up my ROM.
Sent from my Evita

Currently on the road for a few weeks, can't risk bricking/running into battery issues on the road. Thanks for all the suggestions everyone I guess factor reset -> reflash is my only option

style2burn said:
During the Viper installation it gave me the option to do a wipe with installation, and I did that.
Click to expand...
Click to collapse
I always stay away from the wipe options in AROMA, as they have been known in the past to cause issues. Always flash from TWRP.

Can't run "system settings"

Hi. I have a Oneplus one bought few years ago, never updated. Since few days I can't run "system settings" app : when I click on the wheel or on "system settings" nothing happens!!!!!!! So I can't pair a new bluetooth or wifi device .......:crying:
Any "easy" solution?
Thank you.

unlock your bootloader maybe, flash twrp and flash new rom, it might be rom issue, maybe
Sent from my A0001 using Tapatalk

Thank you, but is there not a easy way like downloading an system settings app?

Can't you just factory reset? It will reinstall system apps hence fix the issue.

Thank you.
When I read things about OPO factory reset, I can't understand what it erases exactly. I'd like to keep my apps and personnal datas.
Do you somethings about that?

ziaziung said:
Thank you.
When I read things about OPO factory reset, I can't understand what it erases exactly. I'd like to keep my apps and personnal datas.
Do you somethings about that?
Click to expand...
Click to collapse
Well, you could "dirty flash" from fastboot by flashing everything but userdata.img it will keep all your data and fresh install the OS. But only if you are running stock COS.
https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/

Ok. But how can I know if I'm running stock COS (I can't access system settings)?
What I know is that I've bought the phone 3 years ago and done nothing on it (no flash ......) so I think I run an official three years old OPO OS.
So is it a stock COS? (stock OS?)
Thank you for your help.

ziaziung said:
Ok. But how can I know if I'm running stock COS (I can't access system settings)?
What I know is that I've bought the phone 3 years ago and done nothing on it (no flash ......) so I think I run an official three years old OPO OS.
So is it a stock COS? (stock OS?)
Thank you for your help.
Click to expand...
Click to collapse
Ah, so you have the bootloader still locked, which means that to unlock it you would have to factory reset.
You should really backup your stuff and factory reset your phone. I do it once a month or even less.
One more thing I can suggest you is to delete cache, either system app cache or the whole system from the recovery.
Boot to recovery and wipe cache.
Hope it works, if it doesn't I really advise you to factory reset.
COS = CyanogenOS