Related
Hi,
i have seen many people got problem after installing a new firmware or Rom.
Even though the next update might fix the error, but it feels annoying right?
So do you prefer to stay on stock rom or update if there is a new update?(not custom rom, official one.)
I prefer leaving stock. But i have an SE phone, and they don't do a good job imho of updating/supporting their products. It's a safe answer, but go with what works for you. Our devs are really good, though.
Sent from my rooted tomato using xda app
cascabel said:
I prefer leaving stock. But i have an SE phone, and they don't do a good job imho of updating/supporting their products. It's a safe answer, but go with what works for you. Our devs are really good, though.
Sent from my rooted tomato using xda app
Click to expand...
Click to collapse
Thank you
But i afraid if i update and have a problem, and have to change back to previous rom it might affect my warranty, since i still have my phone's warranty i will not root and install custom rom, i afraid it might be affected even though it can still back to stock rom.
I say go ahead and update to a new firmware / rom . It usually shouldn't cause any problems if you follow the steps closely . Also you can always reinstall stock rom and then un root your phone to get your warranty back
I would like to use custom ROM for my HTC to enable Bluetooth file sharing, but it seems like very complicated process.
On my previous smartphone (Blackberry) I always used hybrids.
im abcd said:
I say go ahead and update to a new firmware / rom . It usually shouldn't cause any problems if you follow the steps closely . Also you can always reinstall stock rom and then un root your phone to get your warranty back
Click to expand...
Click to collapse
I did install a custom rom before to my previous rom and ever heard about getting warranty back by reinstall to stock rom, but i didn't have a chance to do it, so i am not really sure.
maya79 said:
I would like to use custom ROM for my HTC to enable Bluetooth file sharing, but it seems like very complicated process.
On my previous smartphone (Blackberry) I always used hybrids.
Click to expand...
Click to collapse
I had a LG before, and did try some custom rom. It was not so complicated.
But maybe other phone procedure might be a little different.
I've never left any of my Android phones alone ever. When I got my Motorola Droid (my first android OS phone) I rooted it a few hours after activation, a new ROM a few hours later while at work then put it all back to stock and got it replaced with a HTC Droid Incredible with the 30 day swap thing VZW does.
Flashing a custom ROM or staying stock is the whole reason XDA-Developers exists. Stock firmware are solid builds, but they are also very, very limited in what they allow you to do. I say allow because that is exactly what your carrier/manufacturer is doing with their firmware. With a custom ROM, you open the door to so many more possibilities, (ie tethering, mobile hotspot, Superuser access apps,...)
Now whether to stay on a stock FW or go custom, that is going to be up to you and what you want to get out of your device. My wife and I each have a phone and a tablet. All are Rooted. My Phone (Samsung Vibrant) is running a custom ROM by me, her phone (Motorola XT720) is running a custom ROM, her tablet (Nook Color) is running CyanogenMod 7.2, but my tablet (Asus Transformer) is running stock ROM but custom kernel.
Personally, I do not like Touchwiz from Samsung or Motoblur from Motorola, hate the bloat that both manufacturers put in there that I do not use. I also bought my wife a tablet that was Barnes&Noble branded android based FW, but I completley scrubbed it off and put a custom ROM on there for her. So now she has a full on tablet instead of a simple reader. See where I am going with this?
My tablet is fast, has all I need on it and since I am considered a power-user, I tinker with it but at this point I am satisfied with it as stock. Now, that is not to say that I have not altered it. I put a custom kernel on it and frozen some of the bloat that Asus provided. It came out with Honeycomb and then updated to ICS. Since I have had it on HC, it has seen 6 FW updates and every one of the ICS ROMs were terrible and left most users with a useless piece of machinery. Myself, I was able to keep it from de-evolving into that and have been happy with it ever since.
Hopefully this shows you that there are plenty of options for why to use a custom ROM but also to stick to stock firmware. It really just depends on you and what you want. Flashing is easy. Just read the OPs, search and read some more and above all, learn to make a Nandroid Backup.
Personally, I prefer to stay as close as possible to AOSP, with custom ROMs like Cyanogen. You don´t feel bounded by the locks imposed by the manufacturers or, even worse, the carriers.
In my experience, they are not as stable as stock ROMs (currently, I´m having some random reboots with cyanogen 9 in my Galaxy Note) so, if you don´t feel adventurous, stay stock.
Regards,
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good
=phatreno;49148087]For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good[/QUOTE]
Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms
kieso said:
=phatreno;49148087]For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good
Click to expand...
Click to collapse
Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms[/QUOTE
I know that there' one out there you can flash and maintain a unlocked bootloader but reading the thread sounds like there's a lot of issues with it I use my phone for work so need something 100% eliable Liquid is almost there but still have to do battery pulls get f/c's ,I did have another phone so it didn't matter now this is my only phone
let me rephrase that didn't mean take the ota but flash the official 4.3 which would lock boot loader to take the ota I would have to revert to stock then take the ota easier just flashing 4.3
After a long time flashing custom rom and kernel on my wife S3 and always hear complaints about issue, I decided to flash stock 4.3. Now she's happy with her phone, everything is working smoothly and the phone is pretty fast and snappy, battery life is the best. I have to say, 4.3 is a great improvement over 4.1.2. My recommendation is if you like to play around with flashing custom rom and ok with all the bugs hear and there then it would be fine, but if you want a daily driver, stable phone then stock 4.3 is the way to go. While she's on custom rom, many times when we at a party and when she tried to take picture the camera FC, or displayed weird color, the gps acting up, phone lockup needed to pull the battery to reset etc...Again, if you want a stable, good battery life, go with stock 4.3 and with just root.(I need root to install wifi tethering). Now she has a perfect phone and no more complaints.
buhohitr said:
After a long time flashing custom rom and kernel on my wife S3 and always hear complaints about issue, I decided to flash stock 4.3. Now she's happy with her phone, everything is working smoothly and the phone is pretty fast and snappy, battery life is the best. I have to say, 4.3 is a great improvement over 4.1.2. My recommendation is if you like to play around with flashing custom rom and ok with all the bugs hear and there then it would be fine, but if you want a daily driver, stable phone then stock 4.3 is the way to go. While she's on custom rom, many times when we at a party and when she tried to take picture the camera FC, or displayed weird color, the gps acting up, phone lockup needed to pull the battery to reset etc...Again, if you want a stable, good battery life, go with stock 4.3 and with just root.(I need root to install wifi tethering). Now she has a perfect phone and no more complaints.
Click to expand...
Click to collapse
that sounds like what I needed to here,did you flash 4.3 or revert to stock and take the ota not sure if there's a difference I already downloaded the stock 4.3
I've had zero issues on the 4.3 rom.
Make a backup and give it a run.
Sent from my SCH-I535 using xda app-developers app
phatreno said:
that sounds like what I needed to here,did you flash 4.3 or revert to stock and take the ota not sure if there's a difference I already downloaded the stock 4.3
Click to expand...
Click to collapse
It's depended on what apps you installed on your phone, most of them should be fine with 4.3. When ever I upgrade to a new version, I like a clean install. Do a factory reset (this will wipe all your installed apps and reset your phone back to factory condition, make sure you have a backup of your apps), then let the upgrade run. Once done use saferoot to root.
from crack flasher to stock
i've been a crack flasher since my DX days, having flashed just a couple days after getting my S3. I've been on Hyperdrive, Synergy, AOKP, OSE, stock and various versions of CM to include the best, Mastamoons unofficial.
had to get a replacement phone, and as i was setting it up, the damn thing updated to 4.3 itself.
now... i still get that crackflashing urge, but i will admit, i like having the phone stock. i can make it look like its on any of the other roms, just with minor alterations.
antenna's on the latest is the best i've ever seen, everything works great, and don't see the lag on 4.3 TW as on others.
guess i can live with this for a while, and i do have faith in the DEV community that someone will break the latest, just as in previous versions. But for now, i can live with stock as everything works great!
:victory:
buhohitr said:
It's depended on what apps you installed on your phone, most of them should be fine with 4.3. When ever I upgrade to a new version, I like a clean install. Do a factory reset (this will wipe all your installed apps and reset your phone back to factory condition, make sure you have a backup of your apps), then let the upgrade run. Once done use saferoot to root.
Click to expand...
Click to collapse
ok thanks
Please go here for any further...http://forum.xda-developers.com/showthread.php?t=2575661
I'm currently on a custom kernel and rom for 4.3 but I'm having terrible battery life and I'm tired of flashing new roms to get the same result. As for some of my friends that have a verizon S3 phone, they get better battery life and don't have all the problems that I continue to have.
Is there a way to go back to complete stock and let my phone do the OTA update and not have to worry about this phone anymore?
I know I must sound crazy for wanting my phone to go back to normal, but I'm tired of having all the problems and trying to find new roms to have them fail on me, even though everyone else seems to be having good luck with them.
So again I'm a Verizon S3 on 4.3, Baseband VRUCML1. Ktoonz kernel on CleanRom 8
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.