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.
Hi, I have been experiencing substantially longer boot time on my Desire S after having updated to FW 2.10.401.8, using RUU method.
Fast boot is obviously enabled, i am 100% stock, S-On, Unrooted. I also tried a factory reset last night but it didn't change anything.
The RUU flash completed flawlessly and did not get any error during the update process.
Has anybody else noticed something similar?
I always suggest that you Disable fast boot, it saves seconds but brings no real benefit while being dangerous
How often do you restart your device and why?
What does seconds on restart boot matter?
I Suggest dropping into custom recovery and perform a full format on all partitions, then install custom ROM and report back
Edit
Just re read you say stock soff and UN rooted, this doesn't add up
Swyped from my Desire S using XDA Premium
Ben, I made a mistake while writing the post, I am S-On. I know a few seconds doesn't make a big difference but I would like to understand if the update introduced longer boot times for everybody or if anything in particular is causing this on my phone.
I do not want to root yet as I am still under warranty.
Ok, it seems now the boot time is short again. I think that the only change I made has been removing and updating some apps...
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
just use the one click root tool by kennethpenn, work perfectly thanks. use titanium back to do a backup of all the app and system then took out all the att bloatware. i have few questions at this point.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
3.
what other things i can do after i root the phone at this point?
thank you for your help
no one can help me with those questions??? anyone???
i am sure a lot of people have the same question.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
I'm not 100% sure on this, but as long as you're running an actual AT&T ROM (not an Asian or Rogers ROM), you'll be notified of the OTA's. Now, if you're not using the stock Recovery image (that is, if you've installed CWM Recovery), you won't be able to apply the update. OTA updates get applied via the stock Recovery image.
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
If you do a factory reset from CWM or within the phone's UI, you're fine. Root will remain in place, and you won't brick it. It just clears the user data from the phone, and should leave "sdcard" intact. However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
3.
what other things i can do after i root the phone at this point?
You ca use apps like AutoKiller to change your memory management, for one. That's about all I'm doing with root right now. If we ever get custom kernels, you'll be able to overclock your CPU. If you search the Play Store for "root," you'd doubtlessly find some other root apps that you may be interested in.
Hope this helps!
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
craig0r said:
However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
Click to expand...
Click to collapse
I can confirm that it's OK. My phone was rooted and stuck in a boot loop. I did a factory reset. It was reset and still rooted after the fact. So you can do it.
thank you all
redpoint73 said:
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
Click to expand...
Click to collapse
Just to clarify, pre-rooted versions of the official ROMs (which often get posted on XDA, as I mentioned) may need unlocked bootloader to install, so this will possibly not be an option for a while. Although there may be alternate safe ways to update (but not OTA). For instance, a leaked 1.83 firmware version is already available as an RUU in the Development subforum. Apparently, its okay to install via RUU, then re-root.
In general, the safe thing to do is to read up on here when updates are released, and see if there is a safe way to update on a rooted phone.
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode
I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.
halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk