Related
So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?
D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.
clockwork recovery installs a boot hijack, which might be the culpirt
srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!
I was in a hurry and upgraded my GF's Rogers Captivate to the leaked 2.2 ATT some time ago. It seems now that the backup I performed (via Titanium) was not the full backup I required and therefore I have no backup to revert to my Rogers stock 2.1.
Her phone is operational, it's an improvement from 2.1 Rogers stock but I've now realized that if the phone isn't actually mine to play with, its not worth playing with.
With Rogers 2.2 released there is indications that it fixes things that I/she would like resolved (mainly the SMS timestamp? and better GPS functionality?)
I would like to return to a normal state of Rogers 2.2 and then stop playing with her phone.
There is a thread here on how to return to Rogers 2.1 but it is large and has multiple solutions and warnings enough to make it seem like its not the easiest path to venture...
http://forum.xda-developers.com/showthread.php?t=846501
Then again there is other threads showing how to just simply flash to a Rogers 2.2 ROM....
http://forum.xda-developers.com/showthread.php?t=905655
Will there be disadvantages to taking what seems like the easy route and flashing simply to Rogers 2.2 without going through a convoluted process to revert and kies update to 2.2? Clearly I'm not fully competent regarding this and its difficult to get better when you don't yourself actually own an android phone (hence why I'm trying to bail). I just want to find the easiest way to essentially get out of the mistakes I've made, and make them as forgettable as possible. Any advice would be appreciated.
I don't see anything wrong with flashing straight to Rogers 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
I use Odin to flash stock 2.2 most simplistic way to do it. Saves you the hassle of having to deal with Kies.
I used the odin flashable file from here. No need to get the kernal/moden file it's already in the .tar
Do I need to save the APN settings or anything?
Assuming I have no interest in any personal data will flashing via odin the above mentioned I896UXJL1-HOMEBINARY.TAR bring me back completely to Rogers?
My APN settings and everything will be back to default rogers?
Will the AT&T symbol still be there on boot?
If I want to try a custom ROM in the future will I be able to do it from here, or will I need to flash to 2.1 or some other stock ROM?
I can't seem to install CWR in my current state, will this potentially change that?
Uc an use ODIN to flash back to 2.2 Rogers but I am afraid u will stll see At & T logo when u boot it up
There is a thread to replace that logo as well
The AT&T thing doesn't really bother me.
I left this problem and didn't deal with it because her phone was working fine and I would have rather not touched it. The problem now is that Rogers in Vancouver had some massive downtime a few days ago and now her phone refuses to run data. Voice is fine, I modified and played with the APN settings to no avail.
After testing the SIM and some other options it seems that I'm left with no other choice but to conclude that this is my fault and I guess going forward on flashing a stock 2.2 Rogers hopefully will resolve this.
I can't decide, and I'd appreciate your advice. I'm kind of noob. I flashed a custom ROM on my mytouch 4g. And I only did it once. Afterwards, I kind of regretted it because the ROM seemed to be more buggy than the stock. Now, I'm waiting to get ICS on my sensation, but I keep looking through the threads at the ICS ROMs that are already out there and they look sweet. I'm not sure if I want to wait for the ICS OTA, or just flash a custom ROM. The only things that are stopping me from rooting my phone are the fact that I am kind of a noob, and I don't want to flash then have the OTA happen the next day, and have it screw with my stuff. Would I be able to go back to stock after the OTA, and then just have tmobile push the OTA? Also, I have a mac... and I'm pretty sure I can't use a mac for flashing new ROMs. I don't mean to be redundant and I hope this doesn't piss anyone off, cause I see a new thread everyday about the new ICS release. Thanks for any feedback.
You can revert back by flashing via RUU, after this you can receive the official OTA when it gets pushed. Now the part about you having a make may cause some problems. I suggest you do some Googling and find a good virtual machine to run Windows with on your Mac.
i would flash
i think you should definitely flash a custom rom. since the sensations release many roms out now have fixed issues of being buggy/ slow and battery draining. im using the newest insertcoin rom and had android hd revolution before that. both are super smooth and fast. as for reverting to a stock rom, i believe all you would have to do is find the update RUU file for the stock rom to go back, this will cause you to lose root, but after you flash a rom you'll probably feel no need to go back. and always make a backup
btw 1st post
I came from the mytouch 4g as well. If you rooted and flashed on that phone you will do just fine on the sensation. The sensation is about 100 times easier to root than the mytouch.
Sent from my HTC Sensation 4G using XDA App
Hello everyone,
What exactly does Clean Rom do? How is it different from what comes with the phone stock? Will Clean Rom mess with the updates that are pushed to our phones? Any big differences between layout?
Sorry for all the questions. I'm just not familiar with modifying my phone.
Must read more. Spend as much time as you can reading in the dev section. Clean ROM removes all of the ATT bloat and adds functionality like the FM radio and remapping the 3 dot menu button that takes up screen real-estate to the recent apps softkey. The recent apps can be accessed by holding down the home button, like we're familiar with. It also has performance and battery tweaks (says so in the changelog, haven't been using it long enough to notice). I flashed it the day before yesterday and I'm liking it.
Sent from my HTC One X
Clean Rom doesn't use profane language, think of it as the Will Smith of Roms...
Sent from my HOX running WCX
Did you bother to go to the Development forum, and read the CleanROM threads? They very well describe the features of each version of CleanROM.
You don't ever want to install an OTA update once on a custom ROM. It won't be compatible. Either it won't install, or it will remove root, or it will totally bork the system. The devs typically keep their ROM updated to the newest firmware base, and often long before the OTAs go out. So there is virtually never a benefit to updating via OTA (even if it did work).
Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
To the OP, if you want to flash custom, just do it. Spend a few days on Clean, try out Smokin's ROM, too. Just find something you like. Worst that can happen is you RUU back to stock.
Sent from my HTC One X using Tapatalk 2
SoberGuy said:
Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
Click to expand...
Click to collapse
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.
redpoint73 said:
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.
Click to expand...
Click to collapse
I don't think att can see your on a custom ROM, it has to do with if the developer is able to include that ability or not.
Thank you for the replies!
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone? Any disadvantages of using Clean Rom?
I'm just curious about how it works because I tried jailbreaking my iPhone and that made it very crash prone. It's a bad example but it's the reason why I never tried using custom software again but I'm interested in giving this a try. I only get about 2 hours screen time and about 12 hours of screen off time for my phone to die.
I did the HTC battery test and my phone went down to 92% so I'm pretty sure it's not the battery that's wrong with the phone.
RPTheLefty said:
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone?
Click to expand...
Click to collapse
It appears you need to do more reading to get a better understanding or root, ROMs, etc.
Root is just a change of permissions on your phone. It allows the user and apps access to system files that are normally restricted. Nothing more, nothing less.
Clean ROM (or installation of any custom ROM) is a total replacement of the firmware or operating system of the phone (also called a "ROM"). Clean ROM in particular is mostly based on the latest stock firmware version, but cleaned up to remove bloat, optimizations to make it faster and smoother, and some cool added features. There are 3 different versions of CleanROM. Just read the threads for each version to learn the differences.
I don't really keep up with iPhone stuff. But my understanding is that jailbreaking adds functionality, but makes the system less stable.
Whether a custom ROM on Android makes the phone more or less stable depends on the ROM. Some are ported from other phones, to give new UI look or functions, but can be a bit buggy at first. But any good ROM will be stable once it reaches "maturity" and the bugs are worked out. They can be very stable, and even more stable and smoother than the stock ROM. Which is one of the points of running a custom ROM.
CleanROM in particular is based on stock firmware, just cleaned up. So its very stable. Just as stable as stock, a bit smoother in some places, and with some awesome added features. Any disadvantages? Not really. But you need to unlock the bootloader to install any custom ROM, which voids the warranty. nd flashing anything to the phone has the risk of damage if you don't follow the instructions properly. Thats the only downsides I can think of (for any custom ROM, not just for CleanROM).
Redpoint had an excellent summary.
If you're looking for battery life improvement, there are significant advantages to a custom ROM. Some will allow you to adjust the clock rate for the processors. So you can turn the up a bit (overclock) to get incredible performance, or you can turn them down a bit (underclock) to get better battery life.
If that's your main goal, I personally suggest Sick Sense from Smokingl337. He has incorporated this into his ROM, and the reports I've seen have been positive. I had used his ROM before, and I did like it. The day I flashed CleanROM due to a minor bug, Smokinl337 updated his ROM to fix that bug. Figures! But I'll be going back to Sick Sense pretty soon, I'm sure.
Hopefully you can find something that works for you.
Sent from my HTC One X using Tapatalk 2
Different kernel or different radio may also help battery life.
But you need to root, SuperCID, and unlock bootloader to do any of these things (including flashing custom ROMs). So head over to Development and start reading:
http://forum.xda-developers.com/showthread.php?t=1671237
There is also a clean rom developers edition that takes out most of the HTC sense... there is the cm9 alpha 4 rom that seems very stable...
Sent from my HTC One X using Tapatalk 2
OP, I was in your shoes last week. New to android/roms etc. I rooted, unlocked the bootloader and flashed Clean Rom. Just follow the instructions in the associated threads and you'll be fine.
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: