That flash 10.1 support makes it awesome but i wish you could toggle it on for wi-fi and off for mobile network. IMO that would make this rom golden.
[ROM] T-Mobile froyo firmware 3.4.2 leak (new, signed)
- Thread starter Simplestas
- Start date
That sucks, sorry
Could be slightly different kernel boot string in cdt causes this.
Same problem with 2.51 and cq31 from 3.4.2That sucks, sorry
If you only can hex edit cg31 and change only the 2.21 string it should work.
Last edited:
You can't edit it since it's signed
If you have more willpower and bravery to test you can try adding ramdld.smg/firmware.hmg from 3.4.2 to your sbf.Also 3.6.190 posted two pages ago has cdt.bin version 4 with 2.51 kernel bootstring! Here is CG31.smg with that cdt.bin; but beware.
Last edited:
It's really the 3.6.390, just for an odd reason named badly when I downloaded it.You can't edit it since it's signed
Also 3.6.190 posted two pages ago has cdt.bin version 4 with 2.51 kernel bootstring! Here is CG31.smg with that cdt.bin; but beware.
So this means I could switch to a 3.6.390 if somebody had a nandroid backup ?
Mind posting the difference in boot stings ?
Is there also a simple boot.sbf for the CG31.smg that you just posted ?
@bizzaboy same here getting huge latencie.
I am a bit baffled at the mow whay is coursing this.;
I am a bit baffled at the mow whay is coursing this.;
2.21/2.34:
Code:
ATconsole=ttyS2,115200n8 console=ttyMTD10 rw [email protected] init=/init ip=off brdrev=P3A androidboot.bootloader=0x0000 mtdparts= mmcparts=mmcblk1:p7(pds),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(userdata)
Code:
ATconsole=/dev/null console=ttyMTD10 rw [email protected] init=/init ip=off brdrev=P3A androidboot.bootloader=0x0000 mtdparts= mmcparts=mmcblk1:p7(pds),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(userdata)
Code:
ATconsole=/dev/null rw [email protected] init=/init ip=off brdrev=P3A androidboot.bootloader=0x0000 mmcparts=mmcblk1:p7(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(userdata)Perhaps if sbf was posted. Nandroid backup won't change your kernel boot.img back to 2.1.
Last edited:
Did not work bootloader error.You can't edit it since it's signed
One reason I found is that there is some web2go.com configured as home-page for the browser. Seems it pings that every now and then. There was also something in the 6.3.190 build.prop. I'll go and recheck.
BTW, I came up dry with a config switch for HPSA. Need to recheck with a 2.2.1 ROM from a Milestone 2.
Back to the question that I posed. Before you stated the 3.6.390 (the latest t-mobile update) uses version 4, which is the same as 3.4.2. Shouldn't it be possible to extract a boot/mbm for 3.6.390, and flash that over a 3.4.2 boot, and then reinstall 3.6.390 with a nandroid backup ?
I'm really just looking for a way to at some point get back to the 3.6.390 one, so that I can maybe upgrade to the regular T-Mobile US 2.2.1 whenever it comes out. My worry is that Motorola starts using version 3 for the non-US versions, and version 4 for the US DEFYs, which kind of leaves 3.4.2 users stranded if no further 2.2.1 based rom gets leaked that will enable an upgrade path.
Theoretically, if you dump boot partition from 3.6.190 phone flash memory completely with signature and flash it with sbf then it may work. Not sure if nandroid can restore boot.img with singature.
Last edited:
What kind of trouble ? I saw it yesterday being off somewhat, but didn't think much about that. Was using "my tracks" ...
So what I've gathered then from reading is that the newest update TMobile pushed out is essentially the 2.51, which would mean as it stands I should just be able to do a Nandroid restore of the 3.4.2 with no problem correct? Should boot as the kernal would be the same now, or I am I missing something else here?
@gomdon the does appear to be a problem with the GPS
GPS test show 2 or 3 sat's in view.
tried on my htc desire i am getting about 9 or 10
GPS test show 2 or 3 sat's in view.
tried on my htc desire i am getting about 9 or 10
Last edited:
No, the other way around. What if somebody puts the cg31 from 3.6.390 into a 3.4.2 sbf ?
Just checked here. Initially GPS test showed only 2 sattelites. After about a minute of so the rest (8 in total) popped up. I seem to recall this being way faster than on 2.21/2.34.
I think but not 100% sure, once sats have been found data is stored. Then when you use the satnav again it has an idea which sats to look for and should find them quicker.
which does seems to be the case now as the defy finds sat's just as quick as my htc
Last edited:
Yes, this has been a standard for GPS receivers for a long time.
I remember when I got my first USB dongle years ago it took over 20 mins to get a lock the first time. I was ready to box it back up and return it!
First cold boot of a GPS is always gonna take longer than subsequent locks.
That data does expire too though so if you don't use GPS for a (depends on your equipment) set amount of time it will act like a cold boot again.
I re-installed copilot in a panic after reading this earlier, and it took me about 20 or 30 minutes to get about 9 or 10 satellites, and it still wasn't working right until I rebooted. And now it's perfect
As it's a rom for the US it's likely to be pre-configured to be in the USA.
By the way, big THANKS go to Higgsy for making me a zip to unlock all the apps in the market earlier. Thanks Dude
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone