I've an O2 streak, Firmware 1.6 build 3883 the baseband ends in -EU, I'm an O2 UK customer oem version ends in 21
After much researching I decided to upgrade to 2.1 so downloaded the O2 upgrade (update-6941-21.pkg) it seems this is the best build.
Copied file to sd card, renamed to update.pkg , double checked the md5 sum was correct then powered off the phone. I'm using Linux to copy files to the sdcard.
Held down both volume keys while powering on, selected second option (update), screen went black but a light could be seen behind it.
At this stage I'm not sure what to expect, the phone doesn't appear to do anything. None of the instructions tell you how long to wait, I expected 10 to 15 minutes max, after an hour and no change I reluctantly pulled the battery, the phone booted straight up into the old operating system (phew).
Tried an official 1.6 rom 4399 build, exactly the same result.
Is my phone being treat as if it has a custom rom is one idea that I'm considering, anyone had a similar experience, anyone offer any suggestions ?.
It's not as simple as just putting the .img file on your SD card. You have to flash a stock recovery. There's a sticky called "Complete Guide to Flashing Your Streak" or something close, that will hold all your answers.
*edit*
Here:
http://forum.xda-developers.com/showthread.php?t=776883
Personally I wouldn't even bother with 2.1
Goto the guide N upgrade to dj_Steve's 2.2 if I follow the guide it's quite straight forward N there is always plenty of help here if u get stuck
DJ_Steve has done a amazing job N made the streak what it should have been. I love BBC iplayer on it..although I now keep going over my T-Mobile broadband allowance LOL
Sent from my Dell Streak using XDA App
Charles: said:
It's not as simple as just putting the .img file on your SD card. You have to flash a stock recovery. There's a sticky called "Complete Guide to Flashing Your Streak" or something close, that will hold all your answers.
*edit*
Here:
http://forum.xda-developers.com/showthread.php?t=776883
Click to expand...
Click to collapse
Thanks for the reply.
It's not apparent to a newbie that to upgrade from a stock rom to another stock rom that you need to flash a stock recovery, at least it wasn't to me (being thick ?).
Maybe it's just a little piece of knowledge that people who've done this before take for granted and it never crosses their mind that newcomers would think otherwise.
Before you replied I managed to upgrade by doing as you said, I flashed the stock recovery with fastboot, put update.pkg on the sd card, held my breath and lo and behold I saw a screen that allowed me to continue (I'm going to try and take a photo of this for other newcomers benefit as in all the posts I read nothing indicated what you should see when upgrading).
I tried upgrading from build 8443 to 2.1 but ended up stuck at the Dell logo, (this was an early build that many people said was better than the last 2.1 release).
Tried upgrading again (different version) and finally managed to get 2.1 on the Streak.
Now for 2.2
Thanks for your help in any case, much appreciated.
Hi,
I've been reading and reading but am not fully comforatable making a decision on what to do here, really want to avoid bricking my baby I'm running a Bell Atrix with Version 4.2.11.MB860.Retail.en.FR. I really want Gingerbread and am tired of waiting for Bell to release it, even if they did, I would have to somehow return to a stock Bell Rom. What is my best option to upgrade right now avoiding any kind of bricking, memory or battery issues? Links would be great
I don't have any links for you, as I'm on my phone right now, but as a first step you need to flash the IHOP_bell.sbf to unlock your bootloader.
This is probably the riskiest part since you're flashing an sbf, but it's small and quick. If you have osx or linux, sbf_flash actually feels safer to use than the glitchy rsd lite from moto. After that install cwm using moto-fastboot. Once you have the clockwork mod recovery system it becomes very easy to switch roms from directly on your phone. Look for gobstopper by nfhimself. He was kind enough to put together some really good stuff for us.
Something to note: 2.3.4 and cm7 are both somewhat buggy at this stage. Buggy enough that I've gone back to 2.2.2 for now. I can put up with fc's but I can't have my main phone rebooting or freezing, or having irregular battery so often
Sent from my MB860 using XDA Premium App
Not sure of all the differences between the Bell and ATT versions but there is a great n00b guide here:
http://forum.xda-developers.com/showthread.php?t=1154600
You still have to look around a bit to find all the things you need. Unlocking the boot loader and rooting really aren't all that difficult.
Like maledyris said, its really easy to switch ROMs once you get CWM (Clockwork Mod) installed.
I'm a n00b and had no issues following Swiftks instructions.
Be sure to pay attention and don't try something for ATT only.
Have fun!
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
its been said before that once you're unlocked, you're always unlocked. Flash a fruitcake for a stock setting.
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
xploited said:
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
Click to expand...
Click to collapse
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Pizzaapu said:
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Click to expand...
Click to collapse
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
Lol hes returning back to Moto anyways ha ha! I'll try it out, I fastbooted to Gingerbread (via Kenn) So I never did the OTA.... so I guess I am safe.
Per this post, you can tell if you've flashed OTA 2.3.4. If it has been flashed already, then DO NOT downgrade to a official 2.2.2 build.
mysticdrew said:
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
Click to expand...
Click to collapse
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Sass86 said:
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Click to expand...
Click to collapse
Yeah but doesn't using the pudding 2.3.4 (4.5.91) still makes you have the "Unlocked" thing on the boot setting? which is what the OP wants to avoid so if he takes it to like AT&T if they see it and see Unlocked they will void the warranty, I am pretty sure the retail story wont extract his phone to see if the fuse it sparked and unlocked.
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
I am not sure about the sbf, but I can tell you for sure fruitcake will not get rid of the unlock logo, flashing a fruitcake is only a stock ROM.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
No. Only if you haven't upgraded via ota update. If you did, then there is no way of removing "unlocked" yet.
My overclocked alien atrix
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Just a thought... did you ever back up your PDS partition?
Touchscreen issues sometimes are due to pds issues. If you have made a backup, wouldn't be a bad idea to try restoring it to see if that fixes your issue.
If you didn't back it up, take a look at this thread with a pds file that helped others.
http://forum.xda-developers.com/showthread.php?t=1131649
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
Probably a long shot but, I used to have very similar issues with other phones in the past when I've had a screen protector on for awhile and it gets scratched up. Maybe try remove the screen protector if there is one and see what happens.
If it is going back for repair. why not intentionally hard brick it? The first thing they will do is the full blown factory flash, erasing all evidence.
If you do this, make certain you give them a story that somehow describes both the actual problem and the bricked condition (else they might think the un-bricking fixed it and not catch the other issue.
EDIT: Maybe not all evidence, the fuse that was blown when you unlocked a 2.3.4 might be a real hardware type fuse and never be cleared. Don't know.
My device is doing this exact same thing and I'm in the same position you are in. I never backed up the PDS partition, but a backup using the image in the linked thread did not solve the problem. Nor did flashing multiple new ROMs.
I'm not sure if this is a hardware or software problem. It problem seems to go away if you lock the screen a few times, but then later reapers.
Sorry to hijack this thread, but does anyone know if replacing the digitizer will fix this problem? Since I'm in New Zealand this would be an economic solution as shipping to and from the US is pricey.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Pizzaapu said:
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Click to expand...
Click to collapse
I just saw this. I ended up using the stock 2.3.4 sbf, and then doing a factory reset in the privacy menu. Now has all the stock info in the "about phone" section. I'll let you all know how it goes. Thanks for the suggestions.
Just got back from AT&T! they said it was a software issue! They gave me the warranty and gave me a refurbished Atrix with 1.8.3, stock froyo on it! I'll stay OTA until CM7 comes out of pre-beta then see how to root it after OTA : )
I had Magloader and WP7 in it. As time went by I upgraded to HD7 and never looked back. It's been a while since I have touched XDA and WM6.5.
My assumption is that even with Magloader, you only have to flash your stock ROM and it'll revert back to WM.
Mine won't go on and I suspect that I flashed a Non-Tmobile compatible ROM. Can someone confirm that this is the case? Here's the ROM string: RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.0 7U_2.04.50_22_2_Ship.exe
I understand completely that if I messed it up then it's messed up. I just wanna make sure there might be other solutions or something I am missing out.
-Thanks in advance!
----------------------------------
Is this a final answer? I need to know if it's bricked and nothing else can be done.
Anyone thinks a shop may be able to recover it back? It won't go on at all..
tictac0566 said:
Sometimes, it´s easier than you think.
You´ve got 2 options to get rid of HSPL. One of those options would be simply described in the original thread of HSPL.exe software. If you would have checked this program a little bit, you would have noticed the very fact that you can select what SPL or HSPL you want to install.
Second, you can flash your stock ROM via SD card method, this will replace HSLP and everything else - this does not work using RUU.exe via USB.
Click to expand...
Click to collapse
By the looks of the radio installed (2.04.50_22_2), I would say that you did brick your T-mobile phone. Take a look at the following thread for a possible solution to unbrick your phone:
http://forum.xda-developers.com/showthread.php?t=668347
Hi thanks for the response Lavell. Would MTTY be able to do anything?
The phone doesn't turn on at all, or it seems.
I've never bricked one before so Idk if this is the way it happens.
its gone. dead. it will need JTAGging or a new mainboard.
that thread wont help, the phone wont power on, and that thread requires you can get into bootloader.
that's a really early rom you used, the tmous didnt even exist when that rom shipped.
If you want to get rid of it let me know please!!!
Hey guys, don't mean to hijack the thread but I got the same problem here.
Had WP7 but could not use 2g so I went back to MAGLDR113 and installed the file below:
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship
It went all the way to 100% but now the phone is dead. Computer makes a sound when I plug in usb but I have tried changing batteries and all but it doesn't work.
Does anyone know in Dallas or areas around how to do that JTAG thing?
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
S2K_MoZo said:
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
Click to expand...
Click to collapse
At its most basic, its the same for ALL hd2's, ,
1 get the correct stock rom for your region&vendor
2 flash it
thats it.
Sadly lots of times this is shortened to
1 get stock rom
2 flash it
and people just assume they can use any stock rom, and since they usually already have HSPL installed, it allows the flash to start, and tmous phones die.
Yeh think the HSPL installer should of had a TMOUS version either blocking known bricking radio & ROMs or just an on screen message warrning & advising on checking before comencing with flash.
At end of the day it is the users fault for not researching or using a TMOUS rom to be 100% safer !
http://dl.htc.com/ruudownload/t-mobileUS/Filedownload.aspx?pid=leo
Hey all, I come from SGS4G forums, I know my way of flashing and whatnot with that device. However, a friend of mine owns a SGSII and has a weird issue that I hope you guys can help me fix.
The thing is, the device no longer recognizes the SIM card, or any other sim card. She already tried it on another device and the SIM is working fine. Also, the IMEI got corrupted.
I asked her what she was doing or what did she do with the phone. She told me that she was playing the sims and the battery died. So she plugged it in, waited a few minutes and then she turned it on.
After booting up, the phone didn't recognize the SIM card anymore.
As for ROM installed, she never replaced original ROM, nor ever tried to root the phone. This is what her device status states:
Baseband version: unknown
Kernel: [email protected]#2.
Build gingerbread.uhkg7
I really don't know how to proceed in this case. If it was my SGS4G, I would try to flash another modem using odin, but I don't know how it's done with this sgs2. So I ask the experts here to help me a bit.
Thanks in advance!
ps: i have no access to the device, my friend lives in a town far, far away.
I guess she didn't have efs backup, there are guide to recover imei I think it was in general thread, if those guides don't work, her pretty much final chance is to contact xda member called odia, he can restore imei's
Sent from my sgs2 running cm9 using xda app
If the phone is running stock firmware, why would you risk voiding the warranty by messing around with it ? If you stuff it up, your friend will either end up with a $500 paperweight, or she'll end up paying to have it repaired.
In other words, tell her to send the phone in for warranty repair/replacement. It's a no brainer.
MistahBungle said:
If the phone is running stock firmware, why would you risk voiding the warranty by messing around with it ? If you stuff it up, your friend will either end up with a $500 paperweight, or she'll end up paying to have it repaired.
In other words, tell her to send the phone in for warranty repair/replacement. It's a no brainer.
Click to expand...
Click to collapse
I was just asking if there was an "easy" way to fix this, like, flashing some other rom. If that didn't work we would just rollback to stock.
Anyway, looks like we're going to go with the warranty card this time.
I'm still open for suggestion though, I can't believe this device would damage itself just by running out of battery when playing a game.
And yeah, no efs backup I'm afraid.
There isn't easy fix for this
Sent from my sgs2 running cm9 using xda app
It's not a matter of an easy fix. There's never an easy fix for borked EFS details. You risk stuffing the phone up & voiding the warranty in the process, which means if your friend wants it fixed, she ends up paying whatever it costs on top of what she's forked out for the phone.
Use the warranty, she pays nothing.
Think about it.
Edit to add - Also bear in mind you're going to be telling her what to do with the phone given you don't have access to it yourself. If she misunderstands something you tell her to do, kaput.
mikeflash said:
I was just asking if there was an "easy" way to fix this, like, flashing some other rom. If that didn't work we would just rollback to stock.
Anyway, looks like we're going to go with the warranty card this time.
I'm still open for suggestion though, I can't believe this device would damage itself just by running out of battery when playing a game.
And yeah, no efs backup I'm afraid.
Click to expand...
Click to collapse
You could try first a factory reset
Then flash stock firmware both have been known to occasionally fix IMEI .
Did for me once .
jje
JJEgan said:
You could try first a factory reset
Then flash stock firmware both have been known to occasionally fix IMEI .
Did for me once .
Click to expand...
Click to collapse
The first thing I suggested my friend was to do a factory reset. However, it didn't make any difference. In fact, I thing she came across with an error message saying something about not being able to mount efs files or something like that (she wasn't very clear, but she did mention EFS).
I would definitely try to odin (or kies) another stock ROM but since it isn't my phone and my friend isn't too tech savvy either then I think it's better to send it back for warranty.
Thank you all