I just got a white g1 and gave my black one from oct 22 to my wifey, but 1 prob the whitey has a bad BT radio, if I want to use my BT I have to hold the phone within 3 inches of my head, which defeats the point of bluetooth handsfree tech...
of course it was at RC33 when I bought it and I did the dreamimg.nbh number on her and a theme, should I try to get it back to rc33, Im wondering if I just do a wipe will anybody look much further if at all...whaddya guys think......
I want to ship today if possible, cause they need a valid tracking # before they will ship me a good white G1.
anybody return a moddded g1 and get some kind of hassle...?
why should I even have to ask these questions on an "open source" device isn't modding the point of open source devices????
bhang
As long as you left the bootloader alone, I wouldn't think it would be any problem-- they should do a wipe with the RC33 restore image, to prevent sending your personal data to anyone else.
However, now that you've done it once, it'll take you 15mins to flash back to the default RC33, so why not do it and set your mind at ease?
If you want to be really paranoid about it, then downgrade to RC29 again, and then just wipe it and let it auto update to RC33.
Related
So earlier today I decided I wanted to take my phone off root because it had become really buggy so I followed these instructions from another thread:
"download this http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip unzip it and load it to the root of your sd card and reboot the phone holding down the camera and power key then follow the instructions in screen then reboot and wait for the update. how many more times must i type this? can you people not see the search button."
SOURCE: http://forum.xda-developers.com/showthread.php?t=478856&highlight=original+firmware
After doing this, my phone was working fine. Everything worked. For some reason like 2 hours later, my threaded txt messages started showing up in the wrong order. I called T-Mo and they had no solution so they're going to sen me a new one. I wanna make sure there is no evidence on the phone that it was ever rooted. How do I make sure? Thank you so much!
just make sure you updated to original firmware after you changed your fastboot images... that is... if you changed the fastboot images... then you are good to go.
I never messed with fast boot and all that, after I rooted it, I updated JF1.41 with auto rotate and multi touch. thats it. when I went to original firmware, literally I did exatly what he said with the DREAIMG.nbh file, and rebooted. ( Copied the DREAIMG.nbh file to root of SD, restarted with camera+power, ran the update, rebooted) Was there a step I missed?
The problem now is, I dont wanna change much at this point bc if it fixes the threaded txt issue, then theyll prob charge me for the new phone if the txt problem is fixed.
find the SPL thread(sticky) and make sure that your bootloader screen looks like the stock one and you should be fine as well, RC29 already wipes everything else
my threaded txt messages were going in a crazy order last night. but i assumed it was cuz of daylight savings time lol. my g1 to g1 messages would show up in correct order. but everyone else' messages were in screwy order.
yeah its because of DST. T-mobile changed the clocks to early lol. Either that or the g1 screwed something up.
we will see what happens
I posted this in another thread so ill be brief ...
due to a hardware error I returned a white g1 which I had rooted and tricked out with JF's RC33 a theme and the dev BL... I was feeling lazy so I just wiped it and made sure it was back to the stock theme and sent it off with a flat battery, I dont think they will scrutinize them much, we will see, most of the time you play stoopid say you took it to a store and they did some stuff, whatever, PROVE IT, pry my replacement from my cold dead hand.
ill post if I get some response to my tricked out g1 returned due to a bad bt radio
bhang
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Oh. Ok. Thanks for telling us.
nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!
EDIT: Whoops! Wrong thread!
I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies
i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.
thanks im gonna go back to root then
yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..
I'm not sure it has to do with this, but I flashed my NAND with nandroid with one from a different G1.
and one of the axes in the accelerometer doesn't work at all (its stuck).
any idea how to fix this ? (again,i'm not sure the nand has to do with this)
I had the same problem and ended up just doing a whip and setting everything back up. I had a black G1 that I traded for a White one. It might of also been that i flashed a different version of JF on it was well but wasnt worth the time to flash back to 1.41 nand retore and then flash to 1.42. It only really took me about 15 mins to reinstall all the apps and setup options.
i think i read somewhere that accalerometer doesnt work with nandroid.... mine stopped working this week- just did a wipe and a reflash and it works fine now.....
Can Someone help me? I was playing Labyrinth and when I finish, the accelerometer has stopped working. It does not work with anything, either games or any application. nybody know how to reactivate? Thanks.
PS. I Dont make any mod on G1. It is R33 version.
PS2: It never dropped.
Hmmmm, this happened out of the blue for me a long time ago. I think I had to reinstall the firmware, and maybe even a wipe. Been fine ever since...
-oldsk00lz
Accelerometer probelm - Just happened to my rooted rc33
Hey gents, this just happened to my rooted g1 yesterday.
The accelerometer now only works on one axis. I'm pretty sure its a software issue. I tested the accel using Api demo's OS/sensors. The one graphical output and the three dials at the top. The graph changes and registers the change when i rotate it but it just doesn't want to work with any programs that use the accel. ie labrynth, bubble level etc.
I'd really like to know what happened, what caused this. I didn't drop my phone or do anything of the sorts. I did max out my memory installing too many apps that day but I couldn't see that affecting it.
***re-installing is not an option if this constantly happens. I don't have a data plan to keep logging into the start screen every time I wipe my unit. I know there's a thread about getting around this but I'm still not to comfortable using the sdk.
I haven't tried to wipe and reinstall via recovery mode yet. I was wondering though,
1. how do i find out what version of jesus freak rc33 i have. I think Its 1.41 but I forget and just looking at the buildnumber i can't figure it out. and are the newer versions better should i be upgrading?
2. Is there anyway to fix this with a reinstall. Is there anyway to examine the accel. data readout or code.
3. If not, should i just try wiping and reinstalling the same version of jf rc33 or do i have to reinstall a packaged (oem) version of rc33 and loose root (i don't want that to happen,root is a necessity for me )
I'll glady post my findings and even write up the step step process. I just need some answers first.
Thanks for you help (your form seems to be the only place i get solid answers about my phone) http://forum.xda-developers.com/images/icons/icon10.gif
this happened to mine a while back. a wipe and reflash fixed it. use mybackup to quickly get back to where you were.
this just happened to me the other day i posted here about it but it might of been deleted as i was the only one to post and answered my own question through trial and error.
you might try the app bubble it might allow you to calibrate it (i didn't know this until i read it somewhere this morning) other than that when i had the issue i just reinstalled everything the old fashioned way one apk at a time although first you would need to alt+w in the loader menu then install the latest jf update
hey guys, love the Forum, used it for about 7 phones I've had over the years, but recently i effed up:
so my G1 has worked great and I've been running jf1.42 rc33, and then had the android aero theme. and last night a birdie told me that cupcake was coming so I got a little download happy and didn't realize that it's not out for my phone yet, just the ADP.
Long story short i tried to install it on my G1 and then realized my error and reinstalled jf 1.42 - but now my home button doesn't do anything and my green call button doesn't bring up the contacts/recent calls stuff anymore. but it does work to answer a call or send a call, and the home button will bring it out of sleep and i can enter the recovery mode.
Anyone have any ideas? Factory reset? simple patch-fix? any input would be welcomed before tonight (or at all really) and I'll let you all know what works!!
Thanks in advance!!
bessertier said:
hey guys, love the Forum, used it for about 7 phones I've had over the years, but recently i effed up:
so my G1 has worked great and I've been running jf1.42 rc33, and then had the android aero theme. and last night a birdie told me that cupcake was coming so I got a little download happy and didn't realize that it's not out for my phone yet, just the ADP.
Long story short i tried to install it on my G1 and then realized my error and reinstalled jf 1.42 - but now my home button doesn't do anything and my green call button doesn't bring up the contacts/recent calls stuff anymore. but it does work to answer a call or send a call, and the home button will bring it out of sleep and i can enter the recovery mode.
Anyone have any ideas? Factory reset? simple patch-fix? any input would be welcomed before tonight (or at all really) and I'll let you all know what works!!
Thanks in advance!!
Click to expand...
Click to collapse
Try a wipe(start up phone with home+power and then alt-w at the menu). That said, there are cupcake builds for the G1 as well on here, including one of them by JF himself(JF1.5)
I've only seen jfv15 for the adp - and I thought that they were different variations of the Dream... am I wrong about this? and yeah I think my guy could use a fresh start.
bessertier said:
I've only seen jfv15 for the adp - and I thought that they were different variations of the Dream... am I wrong about this? and yeah I think my guy could use a fresh start.
Click to expand...
Click to collapse
JF1.5 is a modified version of the ADP1.5 firmware which will work on rooted G1's as well as ADP's.
all right well I have class for 2 hours now (and since I'm such a good student I'll wipe and rewrite my G1 and let you all know how it is once I'm done
and the ADP is the G1 minus the T-mobile branding and more unlocked bootloader/software
ok - update 1 : yes wiping the phone to factory default fixed the call button and the home button.
downloading jf1.5 now and will install it - so the ADP version wont have the tmobile myfavs and that stuff, but will work just fine on my phone?
Yes.
Make sure you download and apply the separate radio update, which is also required. http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
mmmk I did download JF's radio update, I'm assuming that it's this update
and YEAH!!!! my phone works perfectly now, just going back through grabbing all the apk's off my computer and reinstalling everything, sah-weet, loving it!
Thanks guys!! (or girls, gotta be Politically Correct nowadays...)
Hi,
My girlfriend recently bought an XDA Orbit 2 which has WM 6.5 install on it.
Everything else on the phone works perfectly and without issue but she is unable to make phone calls correctly;
The phone will be able to dial out and establish a connection but no sound can be heard by either party even though both phones say the connection is there.
This can be resolved by a hard reset, however this only last for about 10-20 minutes before we lose all sound once again.
Can anyone shed some light onto this for me?
One thing that always screws up phone calls is the radio on the phone it should be a 1.59.xx.xx to check it go to start => setting => system => Phone Information => Software Information. Will find it there also while you are there what 6.5 rom is she running on it as if its not a stable one it may be worth updating it...
Should the .xx.xx be anything in particular or just stay as .xx.xx?
anything in particular i use the stock one (with the default rom) which is .42.15 any should do the job though...
Ok the radio on it is 1.58.25.14 which im asuming is wrong. How do I change it?
This a custom flash thingy ma bob wont hard reset the phone when you flash it => http://forum.xda-developers.com/showthread.php?t=376119
http://forum.xda-developers.com/showthread.php?t=426203
Is the radio i am using and imo the best for signal/ battery life.
How to do it.
1.Download both
2. Put the nbh file in the same directory as the custom ruu
3. Put the phone into bootloader (Start + OK + Reset whole on bottom, hold the buttons until it show a red green white blue screen)
4. plug it in to computer (let the drivers fully install)
5. Start up the Polaris_Custom_ruu.exe
6. Follow the instructions, shouldnt take too long to go through and flash
7. it will reset and you will have a nice shiny new radio and hopefully no more call problems.
All i will say now is what an idiot for selling the phone in that state... (may actually be the reason it was sold lol)
Im going to sound ike a total idiot now but I have no idea what ruu is or nbh or where to put it or what a bootloader is.
Could you possibly put it in moron speech Chris?
LOL well honestly i thought that i had already done that....
Have a look at the files that you download and then it will be explained.
The RUU is the thing that will do the flashing to the device
The nbh files contains the information of you download the stuff and follow the instructions you will have the result that you want honestly i cant think of a simpler way of doing it
Ive also put 2 screenshots to try to help you (one has a different radio but you get the idea...)
Also give this a read but i feel it may confuse you more..
http://forum.xda-developers.com/showthread.php?t=381600
Its a noobs guide to flashing and has all of the info that you need to have.
It does give one point that it has to have SPL-2.20.Olinex on the screen but i would guess this is there as you already have 6.5 on the phone.
Awesome, thanks chris I will get it done tonight after work and let you know how it goes, if it fails I have no doubt I will be back complaining about my lack of phone savvy.
Hey Chris, just to let you know that it worked perfectly, thank you for your help it was much appricated.
No worries glad that it worked as if it didnt then i would be out of ideas...