Related
I have tested the rooting of the G1 with the CRC1 update (with my boss`s phone ) He accidently got the update and installed it yesterday on his non-rooted G1 and while we were at work tonight we flashed it back down to the RC29 with NO troubles at all ... only thing left to do was download the spl and the recovery image and type telnetd, download telnet connect to local host, and run some script... which all should work just fine since it did let us downgrade. I havent seen anyone here or on google that has tried that yet so I wanted to let everyone know it will let you downgrade to the lower version.
Now if you have a rooted phone and install the update .. you will more than likely loose the root .... but you should be able to get root back by re-rooting the phone and going with a non CRC version until a modified image comes out.
OK we finished the rooting today and it flashed with the new ROM and everything. It now is on the JF1.51MOD with the updated radio.
Yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/Close
andonnguyen said:
yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/close
Click to expand...
Click to collapse
NEITHER of these 2 threads say anything about anyone testing or confirming that you can downgrade FROM CRC1 and get root again.... the JF thread is saying pretty much dont install it and if you do it wont update anyhow. The other thread was cyogen making an altered CRC1 version that has been patched for updating.
Still no threads like this one that I found
/OPEN
Strapt said:
until a modified image comes out.
Click to expand...
Click to collapse
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29. This thread should be posted in the general Dream section BTW, as its not pertaining to any development topics.
/CLOSE
LULZ.
andonnguyen said:
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29.
Click to expand...
Click to collapse
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Strapt said:
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Click to expand...
Click to collapse
So yeah I'm just upping my post count now since I'm bored. lol. Mmm, family guy is funny.
Strange...as far as I know, I have been able to downgrade to RC29 from all official releases, RC30, RC33 and 1.5, since I have had 4 separate G1's since initial release (I'm extremely clumsy and rough with my phones sometime - usually halfway through a bottle of scotch).
Hmm.
Nevermind - apparently alcohol also affects my ability to read thoroughly.
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
There was never any question of it.
The only firmware known to be easily rooted is RC29.
Downgrading to RC29 is completely independent of what firmware version is actually ON the device -- it is strictly related to SPL version. Since CRC1 is an OS update and NOT an SPL update, it can't possibly have any affect on whether or not you can downgrade to RC29, hence it definitely CAN still be rooted when CRC1 is installed.
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
el_plebillo said:
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
Click to expand...
Click to collapse
what ROM are you going to?? if its Hero you HAVE to have the latest spl. If it has autoappsstosd you need to have your sdcrd partitioned right (fat32 first and then ext2) I recommend using the sdsplit method.
oneG said:
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
Click to expand...
Click to collapse
hmm intersting .. the only time I have seen that is if someone was placing the entire.zip file on the sd card instead of just the DREAMING.nhb file on there. I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Strapt said:
I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Click to expand...
Click to collapse
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
oneG said:
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
Click to expand...
Click to collapse
lol ya you should take her and try ... I finished rooting my boss`s CRC1 yesterday. after flashing the .nhb file we added the JF1.51MOD thats found on lucids page .. mainly because it has the radio and the rom in one update. But anyhow he has a rooted G1 straight from CRC1 ... wonder what radio you guys had on that phone and if it needed to be updated before going to the ROM you chose
I needed this!
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
SoTacMatt said:
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
Click to expand...
Click to collapse
You are very welcome!! Thats why I posted it to let people know that they werent screwed when/if they got the Crc1 update. Glad that it went well for you!
I just got a g1 (and use linux since 1999), and LOVE this phone...sofar.
i would want to root it, and plan to.
i have the 1.5 firmware, and crc1 and am planning this on saturday.
is there a way to take screen shots of it all ? (from the phone)
any tips/ links etc is appreciated.
"run linux, stay happy".
Bellevue Washington
doing the root in Kirkland
Pizza or soda (or beer) on me.
My buddy has the Samsung Epic 4g stock phone. He has not done anything to it at all like root or install any other roms/themes.. He wants to update to 2.2 Froyo DK28. Right now he is running 2.1-update1 SPH-D700 EClAIR.DI18. I have been reading through a bunch of posts online but a little confused. I see they have the update.zip file that you can put on your SD card and apply. If you do it this way do you need to do anything else? Or once you apply zip and install and boot up you are done. I see alot of things about modems and odin. I have a OG droid so I am very familar with the install zips/roms/themes but wasnt sure if the new phones are different. If anyone could let me know I would appreciate it. Should he root his phone and flash clockwork mod and make a backup first before trying to install the update?
I was in the same boat as your bud.
Used the update ziip method
Lost GPS but all apps still there
Had to odin back get lost all apps got gps lock then did the update zip again and GPS was good
Reinstaled all apps.... set up launcher pro again
Had slow auto rotation found a fix on the threads here for that
So now all is good except browser is slower and have checkerboarding ...but battery seems much better
If I had to do it all over probably would have stayed with 2.1 and waited but I am sticking with what I have now and se what happens
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.
Please post questions in the Q&A section.
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?
I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it
Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.
ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.
Hey all,
I looked through the posts and wasn't able to find the answer so I am leaving this. Basically I upgraded my X from a rooted froyo to GB using the 2 files provided by P3Droid to go from the SBF froyo to GB rooted. It works great and I am having no freezing issues however the phone keeps trying to update and download the GB over the air update. I don't know how to stop this from happening or if I did something wrong. I have deleted a few of the Verizon apps that should stop any update from taking place anyway. I thank you in advance for your help.
I downloaded the "rooted gingerbread .596" from p3droid and my Droid X has never asked to update.
the only other thing I can think of is that I accidentally hit check for update on my phone but I don't think that it should have even found the gingerbread once I had installed it myself...
I just went into my settings and into "about phone". I also checked for a update and it says that it is up to date no update is necessary. So I have no idea what is going on. Only thing I can suggest is if it continues, is to SBF back to Froyo and reinstall p3Droid's rooted .596 again. Sorry I couldn't be more helpful.
You could let the update happen, it would go partially, fail and reboot and you're all set
Same problem with Sprint EVO 4g
I have also just installed "4.22.651.2 Rooted & De-Odexed" after accidentally dl the OTA update last week. I just hoped that installing the new ROM would eliminate the notifications to install the update but unfortunately it did not.
I did try to let it install so as to let it fail and rebooted, and the notification is still there.
Is there maybe a way to manually remove the update file?
Tecrekka said:
I have also just installed "4.22.651.2 Rooted & De-Odexed" after accidentally dl the OTA update last week. I just hoped that installing the new ROM would eliminate the notifications to install the update but unfortunately it did not.
I did try to let it install so as to let it fail and rebooted, and the notification is still there.
Is there maybe a way to manually remove the update file?
Click to expand...
Click to collapse
this is the Droid X sub-forum. You will get the proper help if you post in the Evo section.
Sorry I just didn't find anything even closely related to this issue here and thought it would be best to not start a new thread. Isn't this a software issue and therefore somewhat universal?
Tecrekka said:
Sorry I just didn't find anything even closely related to this issue here and thought it would be best to not start a new thread. Isn't this a software issue and therefore somewhat universal?
Click to expand...
Click to collapse
here a link to the thread for your 4.22.651.2 Rooted & De-Odexed rom in the EVO section... and there's discussion in there about your exact problem http://forum.xda-developers.com/showthread.php?t=1110733
Thank you very much!
I'm having the same problem. It comes and goes with no ability to clear. It always pops up after a reboot. It never actually downloads, at least that I've seen....
Does anyone know which package to freeze so the updater stops flagging?
Stop OTA Updates
Freeze the application called "Updater 2.3.3".
So my phone was on .91, rooted, and today i just unlocked the bootloader (with this script http://forum.xda-developers.com/showthread.php?t=1182871). But now after it boots it wants me to enter my blur accont and as soon as i hit next, it wasnts to do the update to .141. I can copy the update but when i hit install later it kicks me back a screen and i have to do it all over again. Is there anything i can do to fix my phone. It is basically unusable
I'm not sure why a new thread, I think you could've just continued in the thread you already opened...
I assume you tried this already?
http://cleanimport.xda/index.php?threads/1027994/
Thank you very much! I was searching for a way to stop the ota, not blur and sorry for opening a new thread, i wasnt sure if anyone would check it again
You definitely should not have started a second thread asking the same question, and questions go in the Q&A section.
What do you want to do now that you are rooted and booted? Stay on GB 4.5.91? Flash a custom ROM?
bleufoxx22 said:
So my phone was on .91, rooted, and today i just unlocked the bootloader (with this script http://forum.xda-developers.com/showthread.php?t=1182871). But now after it boots it wants me to enter my blur accont and as soon as i hit next, it wasnts to do the update to .141. I can copy the update but when i hit install later it kicks me back a screen and i have to do it all over again. Is there anything i can do to fix my phone. It is basically unusable
Click to expand...
Click to collapse
upndwn4par said:
You definitely should not have started a second thread asking the same question, and questions go in the Q&A section.
What do you want to do now that you are rooted and booted? Stay on GB 4.5.91? Flash a custom ROM?
Click to expand...
Click to collapse
Yes i understand this now.
So far I've decided to stay with the stock 4.5.91 (for now) but i added faux's 1.3 Ghz kernel. It seems to be running much faster than before. Although I realized that there's now a bunch of apps I downloaded from play that are no longer available for my phone. What would cause this issue?
To stay with stock you have two choices I can think of:
First, flash a 4.5.141 fruitcake.
Second, find a way to disable updates. You could edit /system/etc/motorola/com.motorola.blur.service.blur/defaults.xml to a server that is inactive or doesn't exist. That will prevent your os from finding updates.
Maybe someone else knows another way to disable updates.
upndwn4par said:
To stay with stock you have two choices I can think of:
First, flash a 4.5.141 fruitcake.
Second, find a way to disable updates. You could edit /system/etc/motorola/com.motorola.blur.service.blur/defaults.xml to a server that is inactive or doesn't exist. That will prevent your os from finding updates.
Maybe someone else knows another way to disable updates.
Click to expand...
Click to collapse
I was able to disable the updates by renaming blurupdater.odex and blurupdater.apk to a .bak.
What exactly is fruitcake, just a modified update that you can put on your phone with rom manager? (Sorry I haven't been able to find out too much about it)