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.
Related
I have rooted my phone, and have been trying to use Fresh ROM, but have been having issues.
I though I should try and unroot, and get back to stock. The trouble is I cannot now get HTC Sync to work, and so would not be able to use the program to unroot.
Does anyone know why I would be having issues with HTC Sync ?
I have uninstalled rivers and reinstalled HTC sync, but my phoen still does not recognise HTC Sync.
OK, tried restoring to stock using the RUU and I'm getting the bootloader error.
I've hunted the forums for answers, but cannot find anything. Am I stuck with a knackered phone ?
grifforama said:
OK, tried restoring to stock using the RUU and I'm getting the bootloader error.
I've hunted the forums for answers, but cannot find anything. Am I stuck with a knackered phone ?
Click to expand...
Click to collapse
Your error is caused by this: http://geekfor.me/news/sprint-ruu-fails/
I know the issues you've been having are kind of crazy. Do you have a nandroid backup that you can go to from when you first rooted?
I do jhave nandroid ackups, but I'm kinda thinking it's something to do with some apps I've installed maybe...
It's really odd, it only happens when I'm on Fresh. I get apps hanging, HTC Sync keeps rebooting...Force closures...really odd.
I would like to go completely back to stock, and then add minimal apps and then reroot and put Fresh on.
I'll see what I can do today.
Nope
RUU still won't do anything
I've gone back down to Fresh 0.2...still nothing.
I have a nandroid backup that I'm gonna go to, but it's post root. I guess I'm stuck with a rooted phone and no ROMs
grifforama said:
Nope
RUU still won't do anything
I've gone back down to Fresh 0.2...still nothing.
I have a nandroid backup that I'm gonna go to, but it's post root. I guess I'm stuck with a rooted phone and no ROMs
Click to expand...
Click to collapse
Yea, flashing back to an older rom won't fix RUU. Have you tried clearing your cache and/or doing a factory wipe yet?
I'm having the same problem. Want to get back to stock. How do I do the factory wipe you mentioned? And knowing how to clean the cache would be useful as well... Actually I'm not having the same problem. My phone came with the 1.29 firmware. I tried using the RUU straight from MoDaCo, but that failed, so I used my backup that is from just after I rooted it and still can't get HTC Sync or the RUU to work.
EZ2Hate said:
I'm having the same problem. Want to get back to stock. How do I do the factory wipe you mentioned? And knowing how to clean the cache would be useful as well... Actually I'm not having the same problem. My phone came with the 1.29 firmware. I tried using the RUU straight from MoDaCo, but that failed, so I used my backup that is from just after I rooted it and still can't get HTC Sync or the RUU to work.
Click to expand...
Click to collapse
Boot into your recovery (power off phone, Home+Power back on). Once in the recovery select Wipe.
Will that remove the custom recovery so I can get back to stock?
Phew... it did... I was starting to get worried for a second...
Crap... no it didn't... but it did let me install the 1.56 update, but the custom recovery stopped it from completing on reboot. And HTC Sync still doesn't work... grrr... frustration...
Ok, I'm going to take a deep breath and try running the 1.56 RUU. I don't know if its going to work considering I still can't get HTC Sync to work but its the only the I can think of at the moment.
AH HA!!!!!! VOLUME UP PLUS POWER ON!!!! BRILLIANT!!! PROBLEM SOLVED!!!! Sorry for the caps, but resolving tech issues is a bit like crack.
So I managed to get back to stock.
Fresh 1.0 applied.
And I STILL get the odd HTC Sense reboot.
It's infuriating.
The last time it happened, I was in my voicemail, changing my details, and when I went back to the home page, it rebooted.
I have uninstalled Advanced Task Killer. Uninstalled Battery Indicator, and yet I still get these Home screen reboots.
Sick of it.
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
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
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.
Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?
Why not flashing a stock firmware to go back to STOCK?
joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.
I agree with bwen diord...aint never see anyone recover from that, least not yet.
cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA