Database Info

Can you unroot a My touch 1.2 aka LE to receive OTA updates

ive been looking for this answer in many forms but still cant seem to find the answer
If i root my my touch 1.2 with the goldcard method can i go back to stock to get OTAs?
I know you can with the G1 ive done it many times and also the orignal my touch you can with the sapping file but what about the 1.2 ?

No, You cannot.

so i should wait for the ota 2.1 before i start unrooting this phone because then im a the mercy of waiting on roms that may or may not come around

I would like to ask why it was stated that it was not possible to revert back to the original?
I intend on rooting my phone in approximately a week (once i receive the 2gb kingston that i ordered) and from what I've read up until now: I assumed that as long as we made sure to nandroid backup, we would be able to reinstate it.
While on topic of the OTA though, is android 1.6 unrelated to the rom used? I always assumed the two were the same and thus to get the 2.1 if and when it comes out: replacing the rom would do it. (In my case, i'd like to use CM if and when it becomes usable)

If you're using the Stock rom for rooting, then you should still be able to receive OTA updates. Its only when you use a custom rom when you run into problems.

kutsuki said:
I would like to ask why it was stated that it was not possible to revert back to the original?
I intend on rooting my phone in approximately a week (once i receive the 2gb kingston that i ordered) and from what I've read up until now: I assumed that as long as we made sure to nandroid backup, we would be able to reinstate it.
While on topic of the OTA though, is android 1.6 unrelated to the rom used? I always assumed the two were the same and thus to get the 2.1 if and when it comes out: replacing the rom would do it. (In my case, i'd like to use CM if and when it becomes usable)
Click to expand...
Click to collapse
Course how can you do a nandroid backup without first flashing a new SPL and recovery?

Is there a place to get the shipping rom? Im having an issue where my paid apps dont show up for download.

bubonik said:
Is there a place to get the shipping rom? Im having an issue where my paid apps dont show up for download.
Click to expand...
Click to collapse
Seems to be an issue for non-rooted 1.2 phones as well if you follow the t-mobile and google code bug reports.

Yea I solved it. I pushed superD 1.10.2 build.prop to /system. All apps are good now. Im sure other build.props work. Not build.sapphire.prop, just build.prop.

[Q] Need advice about flashing a new ROM?

Hey everyone. First of all, thank you very much for your help here if you're able!
Now, on to this:
I have a Droid 2 Global right now, rooted and running Fission ROM. (Recovery is ClockworkMod v5.0.2.3) Fission is, well, out of commission as it would seem, and I'm looking to upgrade to some Gingerbread.
Thing is, I haven't flashed more than one ROM onto this phone before and I'm coming from the HTC EVO 4G -- so I'm a little nervous about messing anything up as there was a much heavier amount of steps involved in rooting and flashing to this D2G than there was for the EVO!
Needless to say, I'm terrified of messing up. Here's my question:
1. If I load a new ROM onto my SD card, do a factory data reset, clear cache and dalvik, can I flash a new ROM from the recovery, no problems? Or would there be more steps needed?
2. This isn't as relevant I guess, but is it possible to unroot this phone safely and update to the VZW OTA Gingerbread? I'm probably not gonna worry about this if it's possible to just flash another ROM as asked in my first question, but it's worth noting.
Thank you guys so much, I've been super antsy with this phone lately. Any help is completely appreciated!

If you really want Gingerbread, with corresponding kernel patches and stuff, you have to update to VZW's latest firmware (4.5.608) as all modern Gingerbread ROMs use it as the base. They won't work on Froyo base.
The safest and cleanest way to get the phone to update is to flash an SBF image and then update to 4.5.x. Do note that this will clear any CDMA programming you probably have done to get it to work on Sprint Nextel. You'll need to reprogram the phone while still running 2.4.x.
Please also note that using custom ROMs is always a risk as there's always chance you'll need to flash an SBF to recover from a bad build, etc., so if to flash the phone to Sprint you need to contact Sprint themselves (i.e. you cannot do it yourself), this might turn into a real hassle.
Stock 4.5.608 is very stable and fast, especially with bloatware frozen.

Ah, sorry, I should have clarified further! It's on Verizon Wireless right now, so it's operating on Verizon still and has not been flashed to Sprint. (I had to go and change my provider logo -- if only I could have two!)
Also, thank you for your quick reply! I do have two more questions now, though;
1. If I flash another Froyo ROM, would I be able to do so in recovery off of the SD card? Rather, is it only Gingerbread that would need to be done with an SBF?
2. I was reading about SBFs earlier and was about to try the process, but I found that it was in .exe format. Would I need to be using a PC to do this? I have a Mac currently, though I would have access to a PC certainly if it were necessary (since it seems like this might be my best bet).

Regarding the OS question: there's sbf_flash utility available for both Linux and MacOS X. It's more easy to use, and is overall more “sturdy” (no problems with missing drivers leading to SBF process aborting in the middle).
Going through SBF is only required to update to Gingerbread (which is indeed highly recommended; Froyo ROMs are mostly outdated), because for that, you need a clean 2.4.330 system. If you can access ClockworkMod on your Froyo ROM, you definitely can install any Froyo-based custom ROM.

Thank you again. I think I will flash an SBF and update through VZW, it sounds like my best plan!
I'm searching to see if I can find the right SBF utility to download (for MacOS X), but I'm having a bit of trouble--do you happen to know where I can find it or have a link? In the meantime I will keep going through the forums!

http://blog.opticaldelusion.org/2011/04/universal-binaries-running-same.html

New I9020A with 2.3.6 - No Cellular service - Can I fix while staying unrooted?

Hi guys,
There are threads on this and I have taken a look. Most solutions to this issue (apparently a radio file that is incompatible with certain devices rolled out with the 2.3.6 update) require a flash (radio, rom etc.).
My phone is unrooted and since I still have the return policy, I don't want to disrupt too much and spend too much time rooting/unrooting just to get it to work.
I'd like to try either a radio flash or a full wipe back to 2.3.5 or 2.3.4 in order to see if this is actually a hardware defect, or a software issue as above.
Can anyone advise on whether or not it will be possible to do a full wipe back to 2.3.5 or earlier without having a rooted phone?
I tried the other thread on flashing the radio but I believe it is not possible without root access.
I apologize for the noob thread, but I could not find an answer to this problem specifically for those with unrooted phones..
Thank you.

Hi there,
There's no way to return to an older version with stock recovery. You would need to root and install a custom recovery. Then you will be able to rollback to the older version of the update.
Since you don't want to do that, the only option is to return the device and get another.
Root is extremelly easy with SuperOneClickRoot (just in case you're afraid of loose too much time on this).

Thanks for the prompt reply.
I guess I was just grasping at straws.
I was following a guid eon nexus hacks for rooting and the process seems relatively quick and painless... would I need superuser installed if all I'm doing is the recovery tools for now?
Its not the rooting part I'm worried with, or the unrooting as there's guides for those (and its quite a simple process) its just the possibility of something messing up along the way

Actually the fastboot unlock and recovery install is pretty painless. Just make sure you have the correct custom recovery for your phone model.
You don't need superuser if you're just running the recovery and have all the roms you will need in you phone's "sdcard"

Fair, I guess if all I'm doing is unlocking fastboot and then am able to "relock" it, it is relatively painless.
This might be a very stupid question and it is a bit OT but since you're active in this thread for the moment, customer recovery... I am a bit at a loss on how to retrieve that from? I was merely hoping that by unlocking fast boot, I can just "flash" in a radio file, but I assume I should backup those radio files first...

You are correct. Just flash the correct radio and you're good to go.
Sent from my Nexus S using XDA App

[Q]Revert to stock bootloaders?

Subject pretty much says it all.. I'm familiar with various flashing, rooting, and recovery methods, but I haven't found a way to get back to the original bootloaders after I've loaded the newer ones for GB..
any thoughts?

I haven't heard of anyone going back to the froyo bootloader is there a reason that you want to. Bootloaders are something most don't like to mess with
Sent from my SGH-I997 using xda premium

well, to be honest I may be barking up the wrong tree..
Over the last few days I've been playing with various custom ROMs, as well as flashing back to stock repeatedly. In the course of all of this experimentation a couple of strange issues have arisen..
First, after running CM7 for a few hours I flashed back to Froyo/stock. At that point my phone decided that GMT was the only time worth displaying, despite my location clearly not being Western Europe... Additionally, I'm now completely unable to gain root on the stock froyo ROM. SOC will complete successfully, and says I have root, but nothing requiring root works. SuperUser is installed, but never prompts for permission. I get 'permission denied' when I try SU in a terminal..
So, the only thing I can think of that hasn't been reverted back are the bootloaders.. I'm curious if there's a compatibility issue between froyo and GB, and wanted to test that theory.

I'm not sure what's going on with your root maybe try doing a factory reset once you get back to stock just know that it will delete your SD cards ext. And internal I have been on gb bootloaders since they came out and have went to stock many times and have never had that problem
Sent from my SGH-I997 using xda premium

sounds like a corrupt su binary sometimes happens when soc fails and sometimes happens when you update the binary and the kernel init.rc script overwrites it with the old binary again( thats the trouble with voodoo kernels now that there are su updates). once the binary is corrupt it can be a pain to fix even if you are shell rooted in the kernel because for some reason even after deletion of the file it doesnt always get removed. i had this trouble with my infuse and a vm intercept and in bouth cases only a reflash fixed it. I don't know about the clock. try flashing stock again and root. also why root the stock Rom anyway? are you gonna run it that way? if not use Odin to flash the defuse or community kernel. that would actually root the phone but technically you don't need to be rooted in the first place to flash a rom just need cwm and a kernel that has a non secure shell.
about the bootloaders there should be no reason to revert, if you want to reset the counter just flash param.ifs from the unbrick package. but if you must then the bootloaders were dumped by a long gone dev names lost1 but nobody tested them. good luck if you try it!

I wouldn't mess with it. You can really mess up your phone.
Sent from my SGH-I997

I managed to get things back to "normal" today. The time still isn't quite right when running Froyo ROMs, but at least I was able to get root back and flashed to UCKL2 w/ root and fixed video.
As far as messing up my phone.. well, that's what insurance is for. ;-)

Stock GB Rogers to JB questions

I've been sitting on my stock Rogers Infuse 4G since I got it, hoping that they would at the very least release an update to ICS. I've pretty much given up all hope, especially now since the Infuse was listed as one of the "violators" in the recent lawsuit. So, in giving up there, I've started to try and get up to speed with what's available in terms of custom ROMs for the Infuse, etc...
I previously had a Captivate (seems like I pick the wrong phones) and have kept that one stock as well (now my wife's phone) aside from the official 2.3.3 update Samsung came out with for it. I checked in here once in a while to try and keep track of some of the updates as I thought about going for a custom rom, but I never had the balls to try anything (I've only ever flashed one phone in my life, and it was bought 2nd hand for $20 ) since I actually *must have* a working phone due to having a kid (daycare calls are kind of important!). However checking today, it seems like I am totally out of the loop and I just don't have the time to try and wade through thousands of pages on various threads to find out what the current "ways" are and such... but I know what I want to achieve so I'm hoping you folks are nice enough to at the very least give me a "search you noob" and point me to some threads :silly:
Since I'm totally stock, from what I'm gathering I think I need (and really I more of need a complete checklist of things to do rather than a "do it for me" kind of thing) to do is:
1) jot down my modem and apn settings and such (already done)
2) back up everything i need, pop out sd card (know how to do this)
3) wipe/clear to factory default (... and this)
4) back up the current rom - everything in case I want to return back to exactly the way the phone is stock
5) figure out what i need to do to flash CWM or something so I have the necessary recovery mode options?
6) flash to ICS (since from what I gather, I need to do that if I want to go to JB)?
7) follow instructions I found on the unnoficial CM10 JB thread to flash to JB
?) flash a new kernel? (is this done already during a rom flash; are there any new kernels?)
As commented, I can figure out 1-3 since I'm not stupid, but I have no idea what is even needed to do 4, nor do I know exactly all the tiny, necessary, steps to do the rest after that... especially since reading some things it seems like most of this is for AT&T users and since I'm on Rogers with a I997R (I assume the R means Rogers), I don't want to mess up my modem or other things to prevent the phone working for me... and these are the steps I'm hoping people can help me with.
So far, in prep, I've noted my phone info (basically everything in Phone settings) and I can back up all my apps and such that I care about, and I've downloaded the unofficial CM10 JB download and the Google apps apk as well, and on the same thread was a link to a 1-click ICS flash or something... so I got that too. Since I want to end up with JB, I'm not too concerned (or should I be?) with it being AT&T stuff to get to ICS, since it's the JB flash that I'd really want to ensure works for me.
Is anyone willing to help me out? I really wish I didn't have to be the "next loser" to make a thread like this but I just haven't had the time to be able to keep up with all the info going around (voodoo mods and whatever else?!) to be able to make sense of all this myself!
Thank you!

This looks like a good place for you to start
http://forum.xda-developers.com/showthread.php?t=1197248&highlight=how+to+root+rogers

First thing to do of course is read, read, read. Understanding what you are doing and why you are doing it is the most valuable resource you can have.
The gist of it is though: to install the custom updated roms, you need root. For Rogers infuse users that is very easy to do; all you have to do is install a rooted kernel in odin. After you do that you make a nandroid (and/or EFS) backup, and install whatever rom you want. CM9 and CM10 have their own kernel, so don't worry about that.
adfurgerson posted the step-by-step guide above me, although the links in the OP may be down. I have the mirrors here: http://minus.com/moAvVibed/
the 3 files in there are:
Odin_Infused_Gingerbread_Kernel_v1.zip - This is the rooted kernel you are flashing
Odin_Stock_Rogers_UXKG3_Kernel.zip - This is the stock rogers unrooted kernel if you want to unroot and go COMPLETELY stock for whatever reason (I doubt you will ever need to use this tbh)
Odin_UXKG3_rooted_no_bootloaders_v2.zip - The stock Rogers FIRMWARE. If you ever mess up you use this to "start from scratch". You will still be rooted though if you don't use the stock kernel above.
So yeah, just flash the kernel in odin as described in the above thread and you will have root + cwm.
From there you reboot into cwm (turn off, turn on holding vol+ and vol- buttons) and make a nandroid backup of your stock rogers rom (or an EFS backup with the infuse toolkit: click here), flash CM9 as per the instructions in the OP, and finally CM10 as per the instructions in the OP.
Also remember:
1. The infuse is almost impossible to hard brick. The only real way to do so is to improperly flash bootloaders, which a rogers infuse user will never have to do. Only AT&T users coming from Froyo have to do it. So keep that in mind.
2. On the chance that you get soft-bricked (screen won't go past samsung logo for example) you can always go back to flashing the stock rom/rooted kernel again in odin and start all over again.

The only thing that I can add to Threi's excellent reply is to mention the one click to ICS. It is in the first post of Scott's CM10 thread,it should give you the ICS recovery that is needed to flash JB without flashing a full ICS ROM.

I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).

j.smith said:
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
Click to expand...
Click to collapse
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.

adfurgerson said:
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
Click to expand...
Click to collapse
Aha, perfect description. I didn't realize I had to get a new kernel to have CWM... and I'm guessing because of signing and such, that a custom kernel (with CWM) is required in order to flash a non-signed rom, which is why you couldn't just do it on stock, right?
Ok, so now armed with that info that clears up a lot, I guess I have just one question left (which I can probably find the answer to with some searching). I have read what that voodoo lagfix is and is this something that is standard now on all kernels (because if it can cause issues, I'd rather just have a kernel without it)? Are there any "rooted" kernels without the lagfix built in so I don't have to remember about disabling the lagfix? ...or is there a way to install CWM on to my current kernel?
*edit* Ok, I realize I might be a bit too picky about the voodoo lagfix thing. I found two good threads on dealing with Rogers specifically, so I'll read over those (and suck it up about voodoo) and see how it goes. Since my vacation got unfortunately cancelled due to a sick kid, I have some time to experiment this weekend... hopefully ending up with JB on my phone!

Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.

adfurgerson said:
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
Click to expand...
Click to collapse
Yep, just flashed the rooted cwm kernel and performed a backup. I read somewhere that you can/should back up your efs in case you lose your imei... so I'm just going to quickly look in to that, then i wipe and do some flashes to jb... shouldn't take long hopefully!

Ok, I seem to be stuck at trying to get the one-click ICS install to work. I've got the EZUpdater package to ensure I have the right drivers, yet everything I try with the one-click seems to tell me that the drivers aren't installed and then launches an installer which also doesn't seem to detect the phone... yet EZUpdater will run fine, etc...
I'm just about to reboot and launch device driver in a mode to list all hidden/previously installed devices and nuke them from history to hopefully purge my system of all traces of any drivers and install EZUpdater one more time to get the drivers installed.
Any reason why my phone wouldn't show up in this one-click (it uses heimdall or whatever) program, but seems to work in most everything else (adb even runs fine)?
*edit*
Got it all working! I couldn't get the one-click ICS to work for the life of me... it just didn't see the drivers even though they were there and working. I guessed maybe it had to do with me running Windows 7 x64 and having x64 drivers, but the one-click maybe being 32bit. I even tried installing the x64 Java JRE but didn't seem to make any difference.
I ended up having to flash CM9 which worked fine, then going to CM10. Had no issues doing that... wish I had just tried that before since that one-click wasted hours of my day and got me somewhat frustrated!