[DEV REQUEST] CAN/FR/AUS/UK/MEX/BR Dev to help Unlock CAN/FR/AUS/UK/MEX/BR Atrix - Atrix 4G General

We have a lack of Developers involved with the Atrix hailing from Canada, France, Australia, United Kingdom, Mexico, Brazil. Or so it would seem....
If you are out there, show your faces! I am willing to help as best I can, I am not without knowledge.
Maybe we can make some kind of amalgam with the French 2.1.1 & the "Pudding" SBF? Are the keys different in the AT&T firmware? Preventing us from using portions of it? We have to get moving on this.
*Update 1*
As I stated earlier, the keys might be different from the AT&T version & CAN/FR/AUS/UK versions. Unfortunately they are. The files released today are useless to us, other than the method to compile an SBF of our own when the time comes. We need someone to leak these files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
From a Gingerbread build for International Atrix's or we wait for the OTA Update. Basically it's a waiting game for a leak or the first OTA Update that is compatible with our devices. I am not even sure if we can grab Code Groups from an already flashed Atrix though.
*Update 2*
Couldn't we use some of that Bootloader Bounty to maybe "Persuade" someone into coughing up a couple Code Groups? Anyone know someone at Bell, Telstra, T-Mobile or Orange UK?

I have an IDEA.
i tried to depack the unlocking SBF and it works. now i can see all the files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
If i replace the firmware.hmg file for thefirmware.smgon the french or Telstra sbf, it should work but i have a big problem, i cannot repack the file . i have an error message (Error opening files from folder. Some ramdownloaders have nothing to flash, remove them.) (
nexxusty said:
We need to get rolling on this. The problem is, there is not many Canadian Dev's in the Atrix forum.
If there is, show your faces! I am willing to help as best I can, I am not without knowledge.
Maybe we can make some kind of amalgam with the French 2.1.1 & the "Pudding" SBF? Are the keys different in the AT&T firmware? Preventing us from using portions of it? We have to get moving on this.
Click to expand...
Click to collapse

yungboss22 said:
I have an IDEA.
i tried to depack the unlocking SBF and it works. now i can see all the files:
CG2.smg
CG3.smg
CG42.smg
CG44.smg
firmware.hmg
RDL1.smg
RDL3.smg
If i replace the firmware.hmg file for thefirmware.smgon the french or Telstra sbf, it should work but i have a big problem, i cannot repack the file . i have an error message (Error opening files from folder. Some ramdownloaders have nothing to flash, remove them.) (
Click to expand...
Click to collapse
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.

Try to unpack and repack the SBF, we never know
nexxusty said:
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.
Click to expand...
Click to collapse

I really don't think this is going to work for you guys but if you have any questions come in to #moto-atrix on freenode and I'll answer the best I can.
nexxusty said:
I was about to do just this. So I am guessing we have to figure out if these .img files are signed with the right keys. It seems they are compatible with AT&T devices, but not ours.
I am unsure as to how they did this. I am sure they all chat in IRC somewhere, we need to get in there and ask a few questions.
*edit*
Ended up here. Seems there is a way to recalculate the checksums of the sbf.
Got one step further, went to compile but errored out half way through.
*edit 2*
Not gonna work. The program errors out even when you unpack and repack the stock 2.1.1 SBF.
Click to expand...
Click to collapse

the only way is to flash the leaked GINGERBREAD chineese SBF Do u have the link of this firmware ?
the2dcour said:
I really don't think this is going to work for you guys but if you have any questions come in to #moto-atrix on freenode and I'll answer the best I can.
Click to expand...
Click to collapse

I will be on IRC in a bit. Just in town grabbing a few things.
Chinese. SBF hmmm....
Sent from my MB860 using XDA App

i haven't seen the full .sbf, all i've seen of this firmware and the way to apply it is in post 2 of this thread

We have waited so long for an unlocked BL and now when we get one, everyone that isn't on AT&T are SOL. I have 100% had it with the Bell side of things.
Looks like we are waiting for an OTA update.....

I guess we'll just have to wait until the 2.3.3 OTA update is released. I know there's skepticism regarding international users obtaining this update, but Motorola went on record stating that it will be released simultaneously for US and UK users. Since SBFs from Orange UK work on all international builds, it would seem likely that all international users will get Gingerbread from them.
EDIT: How were ATT users able to unlock their bootloaders anyway? And why is it so different for us?

I know you guys on Bell are extremely anxious to get your BL unlocked as well, however, I dont think it was necessary to create a new thread in the DEV section for it... It hasnt even been 24 hrs yet. Its also been said hundreds and hundreds of times that requests do not belong in the DEV section.

jgc121 said:
I know you guys on Bell are extremely anxious to get your BL unlocked as well, however, I dont think it was necessary to create a new thread in the DEV section for it... It hasnt even been 24 hrs yet. Its also been said hundreds and hundreds of times that requests do not belong in the DEV section.
Click to expand...
Click to collapse
Although i do appreciate where your coming from, i do think it is necessary for a Bell/international thread for unlocking BL/2.3 for Bell Atrix seeing as our framework is different from the ATT.
Perhaps this request could be moved to the correct area but i do think there should be a Bell/International related thread in the Dev forum.

J-Roc said:
Although i do appreciate where your coming from, i do think it is necessary for a Bell/international thread for unlocking BL/2.3 for Bell Atrix seeing as our framework is different from the ATT.
Perhaps this request could be moved to the correct area but i do think there should be a Bell/International related thread in the Dev forum.
Click to expand...
Click to collapse
Umm see, once we unlock ALL of our Bootloaders... there wont be a "Bell" or "AT&T" version. We will all be running the same stuff. AFAIK.
That's really why I want this the most, I am sick as hell of AT&T only stuff, which is 90% of the mods available, and 100% of the Unlockable Bootloaders available.

nexxusty said:
Umm see, once we unlock ALL of our Bootloaders... there wont be a "Bell" or "AT&T" version. We will all be running the same stuff. AFAIK.
That's really why I want this the most, I am sick as hell of AT&T only stuff, which is 90% of the mods available, and 100% of the Unlockable Bootloaders available.
Click to expand...
Click to collapse
There will still be bell and att versions - the firmwares are still different. I dont think we'll be running "the same stuff" until some of the devs polish up some custom kernels painted with custom roms that can support both models of the Atrix.

jgc121 said:
There will still be bell and att versions - the firmwares are still different. I dont think we'll be running "the same stuff" until some of the devs polish up some custom kernels painted with custom roms that can support both models of the Atrix.
Click to expand...
Click to collapse
I can 100% guarantee there is 1 model of the Atrix hardware. Maybe a couple revisions, but the same hardware nonetheless. This being said, only the software differs. Now that we do not have to use signed files, we can essentially all use the same kernels and data partitions.
If we had an unlock for our phones and flashed the 2.3.4 HKTW build, I highly doubt there would be much difference between our phones and yours when flashed with that same build.

nexxusty said:
I can 100% guarantee there is 1 model of the Atrix hardware. Maybe a couple revisions, but the same hardware nonetheless. This being said, only the software differs. Now that we do not have to use signed files, we can essentially all use the same kernels and data partitions.
If we had an unlock for our phones and flashed the 2.3.4 HKTW build, I highly doubt there would be much difference between our phones and yours when flashed with that same build.
Click to expand...
Click to collapse
I just hope the UK build for ginger comes out the same day the US one does.

Magnetox said:
I just hope the UK build for ginger comes out the same day the US one does.
Click to expand...
Click to collapse
Here's hoping!

Magnetox said:
I just hope the UK build for ginger comes out the same day the US one does.
Click to expand...
Click to collapse
Anyone tried putting cg42 in a french. Orange. T-Mobile sbf? Ill try later if not
Sent from my MB860 using XDA Premium App

stevendeb25 said:
Anyone tried putting cg42 in a french. Orange. T-Mobile sbf? Ill try later if not
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Read my first post. Signing Keys differ.

double. 10 char.

Related

Calls for Devs, Euroxoom?

Guys, Euroxooms are becoming expensive paperweights pretty quickly.
The boot image is what is bricking the devices as its not compatible when Root is being done.
Obviously we take the risks when we root, but im slightly PO with it Just kidding, i have faith in XDa and i hope to donate soon for such a worthy cause.
My question I pose to the devs is the following, Can someone source out a boot.img to recover back to Stock, for the Mz601 model? (3g / wifi Euro variant)
I see all the recovery and root for the Verizoom, but nothing for our Europe brothers here
Has there or is there, any work being done on recovering bricked devices?
A shot into the dark here .... have you attempted flashing the US system image?
Sent from my Xoom using XDA Premium App
I rooted my UK Xoom without problems but when I tried one of the BigDX Xoom themes I got loads of Force Closures.
I had no option but to flash the boot.img and system.img files taken from the Canadian (MZ604)
At least this recovered my Xoom to a working version and now works fine now running a rooted Xoom with the latest Tiamat Xoom 1.4.0 kernel.
I have now made a Nandroid backup using ClockworkMod Recovery should I have problems in the future.
Hopefully, someone will pull the recovery.img, boot.img and system.imf files from the UK Xoom???
Cheers
Ody
WAIT
Guys be patient, I have a stock system and boot image for us, we just need to get a recovery, DO NOT ROOT using the methods here, I will post a rooted boot for euro as soon as I can get it tested.
I have asked the people posting the root instructions to mention that it should not be used on the euro xoom's but it seems to have fallen on deaf ears.
alias_neo said:
Guys be patient, I have a stock system and boot image for us, we just need to get a recovery, DO NOT ROOT using the methods here, I will post a rooted boot for euro as soon as I can get it tested.
I have asked the people posting the root instructions to mention that it should not be used on the euro xoom's but it seems to have fallen on deaf ears.
Click to expand...
Click to collapse
Once you get it can you send me a link so I can add to http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom
bwcorvus said:
Once you get it can you send me a link so I can add to http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom
Click to expand...
Click to collapse
I have the stuff already, except for the recovery I just don't have anyone to test it yet and theres no way I'm releasing without testing. I got it to work on my device but I had to go through an unusual and painful process.
alias_neo said:
I have the stuff already, except for the recovery I just don't have anyone to test it yet and theres no way I'm releasing without testing. I got it to work on my device but I had to go through an unusual and painful process.
Click to expand...
Click to collapse
Yea I know I was there
Sent from my Xoom
bwcorvus said:
Yea I know I was there
Sent from my Xoom
Click to expand...
Click to collapse
I'm just re-iterating for everyone else who wasn't there
may i suggest that the Devs sticky this for the benefit of the European Xoom.
I bricked mine, bought in york, took to Portsmouth CPW and they replaced it there and then, you might not be so lucky, but i think we need to be careful with bricking it lol ,
On a lighter note, how do we dump our roms with boot, system image files, for the benefit of all those who want to unbrick their uk / euroxooms?
How did you brick your Xoom? You did'nt try and relock it? As I said no problems rooting my Xoom from PCWorld? PUP!!!!
Sent from my Desire HD using XDA Premium App
yep i did lock it and put a buggered boot.img on there
any update on the Euroxoomroot? xd
Id like to crack it open without having to worry about the bloody thing of bricking it again haha
fkofilee said:
yep i did lock it and put a buggered boot.img on there
Click to expand...
Click to collapse
That'll explain it! I may be wrong but to re-lock it, you would need to flash UK image files (boot.img, recovery.img and system.img). I'll leave my UK Xoom unlocked and rooted until Motorola release a proper recovery flash file?
Sent from my Desire HD using XDA Premium App
haha, yeah might be a good idea, you have a DHD too? XD, what you running on it ?
im currently on CM 7.0.2 xd , nice phone :_),
How did you get your root on your tab? i am desperate to root it as TitBAckup is a necessity xd plus i want to experiment, do you think its worth waiting till the files for the Eurotab are released?
When i try to boot my tab after the one click root, it was at that point it was bricked, i didnt try to lock it until after ,
weirdly enough though, i could still use fastboot after to do one click root, etc, and lock and unlock and install CWM,
Yep DHD running HDMix Gingerbread! To be honest I don't think you bricked your xoom if you can still get Fastboot? I don't know why one click root didn't work for you but did for me? That said Titanium isn't working for me with the latest Tiamat 1.4.0 kernel.
Also just to say my UK Xoom is WiFi only (not 3g) might explain why I could root mine?
Sent from my Desire HD using XDA Premium App
yeah if you have a wifi only xxom, thatll explain why you have bee able to use the 604 canadian images.
Quick question for you EU zone Xoom wifi owners... on the back of your device where the CE mark is, does it also list an FCC ID? If so what is it?
yes it does, erm, it would vary with the wifi model obviously, ill have alook abd get back to you
fkofilee said:
yes it does, erm, it would vary with the wifi model obviously, ill have alook abd get back to you
Click to expand...
Click to collapse
I really should have asked if there was a TUV registration number and FCC ID. (CE mark is a certificate of self conformance).
What I was trying to determine is if the hardware between the euro spec wifi xoom and the us spec wifi xoom are the same. If they are then both units could share the same fcc id. In theory the wifi Xoom could hold both a TUV ID, and FCC ID since there is in theory no need to make engineering changes between the units to meet compliance regulations, and because of the costs involved most companies tend not to make engineering changes if they do not need to.
The 3G units will obviously have variations because of the different Rx/Tx frequencies for the various cellular carriers, but
My WiFi FCC ID Number is IHDT56MT1

[Q] Can the verizon Play be rooted at all? (in the future)

Hi everyone,
I'm a new smartphone user, but I finally got one in the form of the Xperia Play. Upon doing research on the phones, I find that I'd definitely like to root the phone, and seeing that Verizon made a change to their version made me sad. Now, as I got the phone a few days ago, I was wondering:
Can the Verizon version of the phone be even rooted? i.e., should I keep this phone and wait for someone to root the phone, or will this more than likely not ever happen and I should go back and exchange it for a different model?
Thank you for any information.
-ender
I'm optimistic about GingerBreak being updated soon to allow root for the R800x. As of right now, version 1.2 just says "rooting" forever. I left it for 8 hours to no avail.
I believe it will be rooted with a future update for Gingerbreak.
Anything around will eventually get root. Its a fact of life basically
I'm willing to bet money that the verizon play will be rooted very soon.
RacecarBMW said:
Anything around will eventually get root. Its a fact of life basically
I'm willing to bet money that the verizon play will be rooted very soon.
Click to expand...
Click to collapse
I have to agree with you. Even though it is frustrating right now that I don't have root I am willing to wait it out
Can't you flash to generic system image, then root?
Blagus said:
Can't you flash to generic system image, then root?
Click to expand...
Click to collapse
Don't we have to have the BL unlocked in order to flash a generic image? Also I was checking out some of your post on the Arc forums I don't think Verizon is sim locked just CDMA and fastboot detects our phones just the unlock code doesn't work is there anyway the brute force or trick the phone to unlock? I would be willing try anything for the sake of the Verizon play's.
yes please please can we get some dev love on the verizon version of this phone.. I've had the phone 5 days and love the controls, but would like to see root access and all other types of goodies. Verizon is a bootloader locking b*tch, but there has to be someway around it. Unfortunately i think most of the devs on this phone aren't US/verizon customers so I don't think we're gonna see it too quick. I only have 9 more days to make a decision on whether or not to keep the phone or not...
Please if there is anyone reading this thread working on helping to crack this phone on Big Red please let us know... Unrooted + 3g reception issues might make me have to abandon one of the coolest phones i've ever owned...
Just take system.sin and loader.sin, make flash bundle and flash with flashtool. But be careful, if you don't have original Verizon's system.img, and you lose CDMA...
Blagus said:
Just take system.sin and loader.sin, make flash bundle and flash with flashtool. But be careful, if you don't have original Verizon's system.img, and you lose CDMA...
Click to expand...
Click to collapse
Wouldn't this require us to have unlocked bootloaders? Currently you can't get that on VZW/CDMA to my knowledge.
ryocoon said:
Wouldn't this require us to have unlocked bootloaders? Currently you can't get that on VZW/CDMA to my knowledge.
Click to expand...
Click to collapse
Flashtool can be used with a locked bootloader (see link below). Just put your phone into update mode just like you would with SEUS, and load your FTF file on the phone.
The trick is getting the generic UK R800i firmware to work correctly on the Verizon R800x. Nobody has done it, so there is the possibility of the CDMA radio not working after flashing (and other things may not work either). And AFIAK there is no R800x FTF file out there you can use to go back. But the R800i generic UK 2.3.2 firmware is rootable, so it could potentially be one way to do it.
It is possible to load the generic R800i UK 2.3.2 build on a Canadian Rogers branded/locked R800a, so theoretically it could potentially be a viable alternative
http://forum.xda-developers.com/showthread.php?t=1108239
Yeah, cross-flashing is possible but there's possibility of loosing CDMA.
But I doubt this will happen since amss/radio is not located in /system, only some radio-related files which shouldn't affect this.
Anyways, grab /system/build.prop and if you'll need to go back, restore it, chmod 777, reboot phone, turn off, run SEUS.

Here is the stock SBF for the xprt.

Okay, here is the stock SBF file for all those that have been waiting and digging around for it.
Please be careful using this and I am in no way responsible if you break or cripple your phone.
Enjoy.
http://www.mediafire.com/?ecadm7dxhrchb7z
thanks~
here it comes!
tcaudill01 said:
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
A pity, but I understand. Thanks for posting it when you did though.
(I never had the chance to download it, but I'll thank you anyway.)
tcaudill01 said:
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
I've downloaded it...
Now I give you my "thank you". But.... Can You understand my "But"?
tcaudill01 said:
Okay, here is the stock SBF file for all those that have been waiting and digging around for it.
Please be careful using this and I am in no way responsible if you break or cripple your phone.
Enjoy.
**** Since not one of the people who downloaded the file even had the decency to say "Thank you", I'm pulling the file. I have no tolerance or willingness to help ingrates. ****
Click to expand...
Click to collapse
aww :-(. 30 minutes of google and i find this thread two days too late? My phone is bricked and useless :-(. Please reconsider?
dcostalis said:
aww :-(. 30 minutes of google and i find this thread two days too late? My phone is bricked and useless :-(. Please reconsider?
Click to expand...
Click to collapse
I have to agree. My old man needs this desperately. If you won't post it, at least send the link to some via PM.
Again, thank you for uncovering this.
thanks to original uploader, I personally don't understand calling people names and pulling the file after 2 days...
For those still looking...
cdn.anonfiles.com/1333515773933.rar
Thanks for the sbf!
This is great news, thanks a ton to whom managed to share this with the community.
working or not working
do u try it? information is not clearly.
works, but not recommend
cutdaubac said:
do u try it? information is not clearly.
Click to expand...
Click to collapse
it works, but not recommend.
motorola has released the update.zip for 4.1.15, and after the update, the final sha1sum of every file doesn't equal to the sha1sum in the sbf.
take care of it...
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
i mean, after update to 4.1.110 from 4.1.15, the sha1sum of the system dont equal to the sha1sum of the files in the sbf. however, i didn't check it, and i flashed the sbf.
now, i dont think there are any chance for this sbf to upgrade to the coming gingerbread. as the version are 4.1.100, but the sha1sum are totally different.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
for example,
the sha1sum of /system/app/AccountAndSyncSettings.apk:
4.1.15: d8c4844aaea053262817f7e3e48a2c70cab9c1b9
4.1.110: b8be65cc4224f5fd1bcb27404a94c463f57f8041
4.1.110sbf: b4957ae44524df9c8bd61d1f6842d47175092055
so i dont think there is anyone can upgrade from 4.1.110sbf to the coming gingerbread.
of course, the apk content is same.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
i think, i consider too much...
i wish the coming gingerbread use a total update, not patch..
if there are patch, then it will check the sha1sum of the origin system.
and if it just replace the whole system, then everything should be ok.
tcaudill01 said:
Being that the SBF is version 4.1.110, I would assume that file checksum would not match those in version 4.1.15. Also, 4.1.110 is Sprint based while 4.1.15 is direct from Motorola and I'm unsure what changes (if any) sprint may have applied.
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.
Click to expand...
Click to collapse
thank so much for the file...!! im sure this would have saved quite a lot of people!
The Cell Phone Biz is corrupt to the core thats why we have to,,, customize..
...
All I know is that I have used this several times without issue and over 400 downloads have been made and no one else has seen the issue you have so I am not sure what is going on.
Thanks for bringing it to everyone's attention and if anyone else is seeing this please share your experience.[/QUOTE]
I like the phones you mention...
Galaxy Prevail, Marquis XRPT... I know I am well on my way to becoming a fanatic about this...
And I am just saving up to buy the Galaxy Note from Korea for like $250 (unlocked)...
But can you clue me in on how to save this "original file onto my mac"..
I already downloaded this MDM installer for my mac...
I am dreading all this and have no clue if I can take the ..
Original Sprint Motorolla ,,, that someone in China put a cardboard boost mobile sleeve around and now... Not really knowing who's OS is on this phone... and now try to unlock it (from ..?? sprint or boost) to.... Virgin Mobile (and a special low end Virgin Mobile called Assurance Wireless which everyone says is JUST FOR PAYLO (read lousy phones without features).... so teach me how to ave whatever OS is there in case this does not work at least I can activate it for Boost... and i will share my files... if you need em..
Thanks
A still somewhat sane Newbie who has been tormented too many times but the "in humane" and uncaring cell phone business!
I want to restore my Sprint XPRT to stock Froyo using this SBF and then update to Gingerbread.
liudongmiao mentioned some checksums not matching up for files between this SBF and stock files originally on the phone. Now that GB has been out for a while, anybody run into any problems updating as a result of that or have your updates went smoothly?
My phone isn't bricked, but rongsang made the excellent suggestion in the main XPRT thread on here that I should use the SBF and then apply the Gingerbread update as the easiest way to get to GB. My XPRT currently is running Froyo, rooted, and works okay (other than missing a few Sprint bloatware apks that the GB update seems to want there).
Update: After finding positive reports on another forum I went ahead and applied the SBF followed by the OTA Gingerbread update and all appears to have succeeded.
will this work with thr boost version of XPRT ?
I clicked the download link, and the file was accessible and downloadable. I don't know if this means that the OP was having second thoughts, but thank you very much to the OP for the file!

[Q] Anyone have AT&T rom flash?

My DVP decided to crap out yesterday for no reason. I read the "how to unbrick your phone" thread and was able to revive the phone using the TMO ffu file. It crapped out again so it looks like it's the SD card. I will be doing the flash again but does anyone have that file for AT&T instead of TMO? Thanks in advance.
It might be possible to use the TMO ffu, update to 7720, then use cabsender to send the ATT firmware bundle and turn it into the att version (as that's the only file that differentates the 3 versions)
It could also possibly brick you to the point that nothing can fix it, so I'm intentionally not posting the direct link to the files, but there are links to them if you search around for the VP on xda.
TheManii said:
It might be possible to use the TMO ffu, update to 7720, then use cabsender to send the ATT firmware bundle and turn it into the att version (as that's the only file that differentates the 3 versions)
It could also possibly brick you to the point that nothing can fix it, so I'm intentionally not posting the direct link to the files, but there are links to them if you search around for the VP on xda.
Click to expand...
Click to collapse
I think I'll give it a try, can you point me to the right cabsender? If it bricks I really don't care, went out and bought a Lumia 900 and actually like it. Thanks for the help.
Joey
I'm only make a (hopefully) educated guess on the whole thing, I believe there's only 1 version of cabsender(?), but it's the actual cab that i'm talking about that i'm not linking to.
Since the potential issue of permenetly bricking isnt an issue(?), look on the VP page on the xda wiki, it's listed there.
TheManii said:
I'm only make a (hopefully) educated guess on the whole thing, I believe there's only 1 version of cabsender(?), but it's the actual cab that i'm talking about that i'm not linking to.
Since the potential issue of permenetly bricking isnt an issue(?), look on the VP page on the xda wiki, it's listed there.
Click to expand...
Click to collapse
Found it, thanks again!
SPYDar007 said:
Found it, thanks again!
Click to expand...
Click to collapse
Have you tried this and what happened?
mofotech said:
Have you tried this and what happened?
Click to expand...
Click to collapse
I was able to flash the phone and get it running but it shows TMO as the carrier. It does work with the AT&T sim card, so no issues.

G955u factory binary and eng_boot (bootloader v2)--ERASED THE LINK!!

erased link sorry
What benefits does flashing this provide?
ktimque said:
What benefits does flashing this provide?
Click to expand...
Click to collapse
None yet, it's the base for getting root, once we find a way to get it to stay rooted. It's mainly for those who upgraded to the 2nd iteration of the bootloader and can't downgrade to a rootable firmware (It's been confirmed by a few to work with the new Cyborg rom, albeit without root).
As of right now, unless you know why you need it, it's best to leave it alone.
podagee said:
IF ANYONE GETS ROOT COULD YOU BE SO KIND AND POST IT HERE THANK YOU.
Click to expand...
Click to collapse
ktimque said:
What benefits does flashing this provide?
Click to expand...
Click to collapse
Well, I may have spoke too soon, you guys might want to take a look here in the Cyborg rom thread, seems they have a modified U2 bootloader they're flashing and retaining root. One member has volunteered to do a factory reset to see if it survives, but if so, v2 bootloader may now be rootable, or at least on the right track for public use.
IJoxer said:
None yet, it's the base for getting root, once we find a way to get it to stay rooted. It's mainly for those who upgraded to the 2nd iteration of the bootloader and can't downgrade to a rootable firmware (It's been confirmed by a few to work with the new Cyborg rom, albeit without root).
As of right now, unless you know why you need it, it's best to leave it alone.
Click to expand...
Click to collapse
Thanks for answering that man. Haha. That's awesome that the guys got stuff moving that quickly. I knew that they had the files also,but, held off as long as they could until I came along.
But another useful feature I've noticed in this combo firmware is that there is an open unlock option now and mine sticks after reboot. I tried build roms, kernels,etc.. in the past that ended in ultimate failure. I'd like to start again. At the moment I just cruise the foreign forums grabbing whatever software I can find. I kinda have building only the tree down, not so much, as it's been years. I used to build Linux OS's a long time ago but forgot. I'll do my own research here if it, anybody wants to teach, I'm all ears, all eyes. Aloha

Categories

Resources