Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
ermito said:
Hi folks, this is my first thread in this section of the forum, because i was using my old device LG p500 and now i moved to this wonderful smartphone. So, i'd like to solve this problem which is happening now. Basically, the phone unexpectedly stops, and reboot. It happens a couple of times, i guess 3 times in a week. It wasn't happening in ICS, just now that i upload from OTA to Jelly Bean. Note that this was happened while my phone was Unrooted and with Locked Bootloader, the same occured with root and unlocked bootloader. So, any clue? Maybe i should just change the rom, or clean everything as fast as i can.
Thank you.
Click to expand...
Click to collapse
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
mentose457 said:
If you took the OTA then you are sol and will not be able to unlock your bootloader to flash a custom recovery or a rom the traditional way. There is safestrap but thats less than optimal for flashing. As far as the reboots go, it is probably an app that is causing the issues. I would do a factory reset and be selective about the apps I re-installed.
Click to expand...
Click to collapse
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
ermito said:
What are you saying? I'm already unlocked bootloader and flashed a custom recovery and it's been working normally.
Click to expand...
Click to collapse
Sorry I must have glazed over the part about you having your bootloader unlocked.
Hi, i changed to the SlimRom since then and the reboots still happen, i'm very frustrated. It freezes, then reboot into the bootloader screen and stays there for ever until i press the power button for a while and the phone vibrate 3 times and after that it boot normally.
Related
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
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2046439
Reciprocate said:
My main question is are there currently any working methods to root my phone from 4.1.1
BackStory:
I rooted my phone about 4 months ago successfully. about a month ago i started getting update notifications from VZW to update to 4.1.1 Which would have been great since i was looking forward to jellybean.
Unfortunately their update kept failing. so i decided this morning to use Synergy and just run a custom rom. Followed all the instructions and everything went very smoothly while playing around with my new rom i decided to reboot to test the speed of the boot time. upon reboot im greeted by the VZW soft brick screen.
So i then followed the instructions listed here: http://forum.xda-developers.com/showthread.php?t=1840030
To restore my phone to factory default. which was fine i don't really mind losing my data nothing that isn't backed up on Google.
I decided to fully update the phone and then try to re-install the synergy rom but i cant seem to find any detailed threads on the subject.. Help?
Click to expand...
Click to collapse
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
wingtytn said:
hey guy my question is did u unlock ur bootloader before rebooting also remember if u can manually boot into cwm u can redo the rom its either the up volume or down plus multi function button and power button at same time to go right to cwm
Click to expand...
Click to collapse
I think i actually locked it after i finished the install. And then restarted, do softbricks occur when you re-lock your bootloader?
Also another question..is there any way to check the /system /data partitions from inside the phone (terminal app maybe?) are correctly set to r/w over r/o (i don't like unplanned installs )
Soft bricks always occur on a locked bootloader. There are file managers that can do that like solid explorer.
jmxc23 said:
Soft bricks always occur on a locked boot loader. There are file managers that can do that like solid explorer.
Click to expand...
Click to collapse
Ah dully noted in the future the boot loader will be left unlocked! and thanks for the app recommendation i downloaded it and checked all my permissions I'm slightly less terrified to restart my phone now
thanks for all you help
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device
I have had nothing but issues with this phone upgrading. Every time it bricks, the first time I got it working by reformatting DATA partition. The other times basically gave up and 2-3 days later I come back and it magically starts working again. The day that 5.0.1 came out I downloaded the FUU, well everything looked good the it gets stuck at the Android is upgrading starting apps. Since then I have redownloaded all 5.0.1 files I could find on XDA, and the same results. I tried different roms, using TWRP to wipe and rewipe and format and do it again and again. I have tried to downgrade to 4.4.2 and 4.4.4 but i get the process system isn't responding when it boots up. I am unsure what to do now, anything will help.
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
berndblb said:
You flashed this RUU???
http://forum.xda-developers.com/showthread.php?t=3047103
After flashing that do a factory reset from hboot. That should get you back to a healthy stock system
Click to expand...
Click to collapse
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
dab1414 said:
Yes, that was the first thing I tried, but I just downloaded it again twice and did factory reset both times and I still get stuck on the "Android is upgrading... Starting apps."
Click to expand...
Click to collapse
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
andybones said:
So after it upgrades all apps its just sits on starting apps?
Can't hurt to run RUU again. Perhaps even4.4.4 then take the OTA for 5.0.1
Click to expand...
Click to collapse
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
dab1414 said:
Yes It gets stuck there everytime. Seems like no matter what I do for 5.0.1. When I tried to downgrade ( I did both 4.4.2 and 4.4.4) it gets the process system isn't responding error.
Click to expand...
Click to collapse
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
andybones said:
that's very strange. What method are you going about with the RUU?
using adb?
perhaps maybe try going through hboot with the sdcard?
not sure it will make any difference what-so-ever, just brainstorming.
Click to expand...
Click to collapse
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
dab1414 said:
Yes, it is very strange. OK so I have done nothing with adb for the upgrade. I have tried the FUU.exe, and the RUU through fastboot, fastboot flash all files separately, and put on an external drive that is fat32 to use HBOOT method. and I just downloaded the firmware and did the HBOOT again twice, doing a factory reset after each one. But in bootloader screen all firmware numbers match up and I never get any errors, just gets stuck on starting apps.
Click to expand...
Click to collapse
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
andybones said:
Are you S-OFF?
If so are you wanting to run a ROM or just be on stock + rooted?
Click to expand...
Click to collapse
Yes I am S-OFF since the day I got the phone. And I have been using RKND roms, but I downloaded and tried all the 5.0.1 roms to see if anything would help. At this point I just want my phone working again, but preferably with the ability to change roms when i want to which is about once a month or two.
So I had tried everything I knew how to do again with no luck. Then I just let my phone sit for the last week. Then I decided to turn it on last night and it works fine. Is there any reason why I had to let the phone stay powered down for days for it to start working? This is the second time I had to do that when upgrading the firmware.
Thanks for bringing this up and I'm glad to hear it worked out for you even tho it took some time. My bro just ran the vzw update while on viper 4.1.0 and now he says his screen is unresponsive. He said it ran through all the normal start up procedures but the welcome screen is shaded (like it's in the background) and he says it won't respond to any touches whatsoever. I won't get a chance to see it until I return to work on Wednesday but if it does the same as yours maybe it'll fix itself by then. :fingers-crossed:
Edit: I just realized that you ran the FUU. He went and said yes to the stupid OTA! Hopefully I'll be able to do something with it when I get back but I'm thinking that running the OTA while rooted and S-Off'd might've screwed it up.
Update: I'm a moron! :silly: It didn't do anything to his phone. I just had to reinstall the recovery and viper 4.3.0 and it's working fine again. I think actually it might've been a good thing he did cause now the phone had the right firmware on it for LP so it all worked out. Sorry for cluttering up your thread.