Related
After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan
http://www.xda-developers.com/forum/viewtopic.php?t=2489&sid=8c1aea80a41318c77a50013b562fe4df
Jan said:
After upgrading a O2 (dutch) supplied RUU and RSU files my XDA is now totally dead. That is, it cannot recognise the craddle and connection, it only shows the O2 bubbles background screen. Hard and soft boot makes no difference.
Before the upgrade i did a total backup of the XDA, so I have a approx. 15 MB file BACKUP.STG, can I use that for something now ?
I have a SD card and a writer. I have downloaded the tools from this site.
When using the wallaby bootloader 5.14 I get a GSM ERROR, but I can still get to the place where I can write the rom to the SD card.
I can use the wallaby to get stuff of the XDA, so much is clear. I can load a new OS from the SD card and I can use the OSI tool to put something on the SD card.
My problem is HOW DO I GET SOMETHING USEFULL ON THE SD CARD.
Is there somewhere a default ROM thingy or can I create something myself?
I am new to this XDA stuff, but computer litterate so I do understand words with more than 5 letters, but if you want to answer to this cry for help then please write as if I am a IQ-17 XDA baby.
Thanks
Jan
Click to expand...
Click to collapse
Hello Jan
please find these two links i guess they are usefull to resolve your problem and the posts are by chosl and wwb95
First link click here
Second link click here
good luck and best regards
Othman :roll:
Fixed!
Here is how I did it.
First how I made the mistake:
From the Dutch O2 site (now Telfort site) I downloaded 2 zip files. They contained 2 .exe files
·Radio_unit_upgrade_v31703.exe (xda_ruu.zip, containing program A)
·RSUv1.15(gprs_421_eng_o2).exe (xda_rsu-zip, containing program B)
I followed the instructions and the first file (Radio_unit….) was installed without problems, but the second one hung up the XDA. It was asking for the code for the SIM card at the time of error but more windows were overlaid and when I tried to remove these I must have done something that I was supposed NOT to do. The end result was that the XDA was dead as doornail. (see further description in the above link)
I searched the Internet for resources on XDA and came to this nice place. I searched using different criteria, but did not find something very useful, then I decided to create an issue and within 2 hours I had a response (Thanks FROG). It was the link you have above and here I found the solution. I did try to follow the exact path described but as usual the case is, my situation was not exact the same, but I still recommend reading THE FULL THREAD and my description before doing anything. Be sure you understand what you are doing, I think it is quite easy to make things worse, but if you are careful you should come out with a working XDA. I did!.
BEFORE YOU START DOING ANY THING, TAKE A BACKUP OF THE NON FUNCTIONING XDA. (look at this site for description of the wallaby-bootloader)
If everything fails you can at least restore the XDA to the initial error state, either if you need to perform another try or if you are “throwing the towel into the ring” and send the XDA to official repair.
Here is what I have learned.
To me it looks like the “Radio_unit….” File is the upgrade of the operating system, that’s why it is so big (15MB) and the “RSU….” Is an upgrade of the phone (which I have read somewhere here is using a separate CPU/thingy). To me it also looks like the “RSU….” File and thereby the phone part is somehow connected to the control of battery and recharging of the same, because one of the things I noticed was that the little yellow/green light that shows battery charging stopped working after the failed installation of the “RSU…” file, and during the whole recovery I had to struggle with having enough power on the XDA to perform the tasks at hand.
So a piece of advice, get the thing fixed while you still have some power on the XDA and if that fails use your AC charging cable connected directly to the XDA during the fixing of the problem. The fixing involves using the SD card as a boot mechanism and inserting and removing while having the power cable in is a bit tricky but manageable.
Power level on the XDA is obviously very important, one thing I have noticed is that it is impossible to switch the phone back on again if there is too little power on the XDA, to get it to switch on I will always have to connect the XDA to external AC power. As soon as it is on, I can disconnect and use the phone quite happily. So there is something fishy with the phone and battery power level.
I have later seen on another site that you are supposed to close the phone BEFORE installing the phone update. I did not do that, maybe that was the reason for the failure.
Here is what I did.
First step is to get the PC and XDA to synchronise again.
In my situation the XDA was so dead that no connection using the cradle was possible and then the only other way to get information into it was through the SD card.
First I downloaded the recovery.zip file from http://www.xda-developers.com/repair.zip.
It comes with a small explanation. Basically you place a file and a subdirectory containing another file on the SD card, and then by inserting the SD card in the XDA you can boot the XDA.
To get the XDA to a point where he will accept the SD card, you need to have a To-day screen showing, it will not be a working screen but at that stage the XDA should be able to locate the SD card and boot.
To get the To-day screen try soft-reset (the small pinhole on the left-hand bottom side of the XDA) and be patient, my XDA was very slow under the whole recovery operation and remember to give him power using the power cable not through the cradle.
You might try pressing the volume button, it did nor help in my situation, but I do not think it makes anything worse.
When you have the non functioning To-day screen insert your SD card (with the recovery files).
The XDA starts doing something, you see a progress bar, but it stops after 1% is done with a flash error. The trick here is NOT TO PRESS THE OK OR CLOSE THE ERROR MESSAGE WINDOW, just let it be as it is, showing the message.
Put the XDA in the cradle (and put the power cable back on the cradle too). What we are trying now is to get a working connection going with the PC. Here you have to be a bit creative, like taking the XDA out of the cradle and put it back in, maybe click somewhere outside the messagebox while it is in the cradle or when it is out of the cradle, but again DO NOT CLOSE THE ERROR MESSAGE WINDOW.
If you cannot get this to work, you can try to change the RSUpgrade.sa.cab on the SD card with the other one from the recovery.zip file (as suggested in the documentation coming with the recovery.zip) or by copying the file you were trying to install with the “RSU…” file. In my case it was placed under c:\program files\PROGRAMME B, or just search your whole PC for a file named “RSUpgrade.sa.ca”.
At this stage you should have had a successful syncronisation with your PC.
Every time you start your XDA it will try to finish the failed update and we do not want that to happened. As described elsewhere (see link above) there are several ways of doing this. What I did was renaming 2 files in the windows directory on the XDA.
You should now be able to view the content of the XDA from your PC (no magic in this, this is what you always have been able to do. You have a mobile device icon when opening “My Computer”) , open the windows directory and look for 2 files named RSUpgrade.exe and RSUpgrade.cp64.
Either delete or rename these 2. This will prevent the XDA from trying the upgrade again when you soft reset it.
A bit of ordinary info:
As in windows on your PC, you have a “startup” directory under the “windows” directory. In the startup dir. There is a link file to the RSUpgrade.exe file. This is how the XDA starts the upgrade every time you “boot” the XDA
Remove the SD card from the XDA and softreset it.
Put the XDA back in the cradle and hopefully you get a connection to your pc again.
Now run the installation of the “RSU…” file again, YES the one that failed the first time, we need that to be finished to get back to a working XDA. During the installation, a check on the power capacity of the XDA is done and if less than 70% loaded, the installation will stop.
If this happens, have patience while you recharge the XDA, at this point in time the yellow light should have come back on so now at least you can follow the power loading progress.
After this my PDA part worked but the phone would not switch on, I tried different things including a good whack with a big hammer…. After I had bought a new one (just kidding!), anyhow after a while I decided to try something totally different namely installing the much acclaimed XDA developers special edition ROM and after installing that I was asked if I wanted to open up my phone for access from other parties (or something like that) Boldly I answered YES and LOO AND BEHOLD, my phone was suddenly working (It is something with the SIM lock I think. But anyhow I can recommend the Special edition, if not for anything else that it makes the phone works, but it actually comes with a lot of nifty software. Recommended!
Now is the time to read the whole tread attached (if you have not already done that) and then, good luck.
First of all, I'd like to say this is the most positive and progressive forum I've ever joined on the internet so far. You guys not only rock, but also inspire, for which I would like to add to the THANK YOU chorus!
I have spent days and sleepless nights browsing this forum, trying to unlock my T-mobile MDA.
The details are:
-T-Mobile (USA)
-ROM Version: 3.14.40 ENG
-ROM Date: 11/26/02
-Radio Version: 6.18
-Protocol version: 324e4
-Model No.: PW10B1
-IMEI: 35031400086966009
I'm using the USB via the cradle. The XDA unlock gives me an error reading, which is not uncommon elsewhere in this forum. I had to download the SER v 1.2.
Upon download and installation, I copied (via OSImage Tool)as per instuctions and ran programme A, only to get the "error message 007 ....No ROM image file".
At this point I'm pretty exhausted, especially when I see other posts of people who successfully unlocked theirs. I give up on foguring it out myself, so I please need help. Apparently, I'm a total rookie in this field . It would be highly appreciated if someone can be kind enough to please give me a step-by-step guide on the entire process either by replying to this post in this forum or by anyother means to contact me (e-mail, IM, etc) through my profile. I'll have a great sense of achievement and happiness gaining my freedom by eventually unlocking my device this weekend before my trip next week.
Thank You and I appologise to anyone that might be offended by the length of this post :wink:
You can run the file from your desktop, make sure you are synced with the xda, it will update the rom through the usb port. Before you do this it would be a good idea to back up your current rom using the sd bootloader method. Once the special edition rom has completed, just poke the unscrewed top half of the stylus in the hole on the bottom right of your xda, just poke once, wait one minute then poke again. You should tehn have an unlocked xda, you can then restore your original rom by inserting the sd card with your original rom, entering bootloader and pushing the action key when prompted.
Thanks for the response. OK, first, what ecxactly is the bootloader and the "bootloader method'?
Secondly, I tried running the S E ROM and keep getting the error message relating to its inability to find the ROM image.
Where did you download from, what size is the file? The bootloader method is accesssed by pushing the reset with the stylus while holding down the power button, then press the top left key on front of xda, you will see options there, you will not see these options when you restore a ron from sd, all you need do is enter bootloader, the xda will ask if you wish to program the rom, you press the centre of the 4 way jog button and away it go's.
I downloaded from:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
It seems to be a 15.4MB file
The file size is correct, you should be able to sync your xda, click on the special edition rom .exe file and it should install to your xda using program a, there is need to use any other tools, as\long as you have a backup of\current rom you have a way back to your original configuration.
I have just downloaded and executed that same file, the first thing that comes up is winzip self extractor, once it has unzipped itself a dos box pops up, it then jumps to program a and commences the install, make sure you are running the file direct from the directory and not from a shortcut, it definitely works.
I did that and I keep getting that bewildering error code 7. Again, I tried unzipping the file first and then run prog A. It went fine until after step #3 then error code 12 pops up: "ROM image is not compatible with my device.............. download utility nd try again...."
This thing seems simple and works for everybody else but me :evil:
at this point, you should use winzip or winrar to extract a file named nk.nbf frim the exe you downloade. then to either use the XDAtools to copy it directly to your XDA ROM, or move the file to SD card using your xda then use the SD flashing method from the bootloader.
good luck ...
Good news & Bad news ...... I was able to run the SER prog. First, I ran the adaptrom file and then programme A. Everything was proceeding fine until it was about 50% and then my system (desktop) froze/crashed. I had no choice but to restart the system. Now the XDA screen has a display with a progress bar and the message: "Upgrading........ It will take about 5 mins.........."
It seems its a curse :twisted: but since I've made some progress, I cant give up now. So I'm determined to succeed by fixing this stuff. My question is Can someone please tell me where to go from here??????? As usual, your patient and kind response is highly appreciated.
Oh, I forgot to add that in addition, now ActiveSinc cannot establish communication with my device, even after restarting it several times and trying to get connected via its program
hey ... no big problem ... relax!
you have to get SD reader/writer and connect it to your PC. move the extracted nk.nbf file to the SD card then insert it into the XDA. goto the bootloader mode (power + soft reset) it should recognize the card content ... just press the middle of the rocker key (action) and you will see hex counter increasing from 000 to 200 ,.. at the end, press hard reset and after 60 sec press hard reset again.
note: make sure your XDA is > 80% charged before start!!
good luck.
Didnt Work
Did exactly as you suggested, but ending up with the same screen "uploading..... It will take about 5 minutes..." :?
Finally made it!!! Thanks guys for all your input. Device works fine, so far, I dont seem to have lost anything! I feel FREE, excited and victorious!!!! YEAHHH!!!!!
ok...I'm really new to all this so please show a little patience towards me!
I was trying to load the XDA-developers-SER-v12 on my phone and just when it started with the progress bar moving at the top of the PPC screen, when it said "Do not Remove Device..." I accidently lifted the phone out of the cradle as dumb as I am...! After that I tried to hard start it by shoving a pin on the hole in the right side under the battery icon with the cross (hard-reset) and got the Bootloader 5.17 screen with the three colors and GSM (OK) there when I pressed the soft-reset and power buttons simultaneously.
But since I was the idiot and could not understand what was going on, as I was not in this forum nor even behind a computer, I reset it again and again a couple of more times. Now present situation; I have the same "Do not Remove..." screen everytime I do a hard or soft reset even if I keep the power on/off button pressed alongwith pressing the hot or cold boot buttons on the left and right corners respectively. In fact the screen has gotten badly distorted but the same "Do not Remove..." comes up in the totally distorted state on the screen and the Bootloader or the colors, nothing comes up anymore.
When I try to put the phone on the charger, the light goes orange just as if it is charging, in fact, after an hour or so, just as it normally would in the correct phone state, it turns green.
Is my phone toast or can I still do something about it?
Munz.
I'm no expert, but it seems to me that if there is a complication with the software when loading, one should try using the sd method of rom flashign. Cook or dl a rom, use XDA tools to load it to an SD, put the SD into the device, and then use the bootloader to load off of SD. Other than that, I know little to nothing.
Good luck!
Search in the forum after SD Card flashing for the Wallaby.
This would fix your device...
HTH
Stefan
Re: Dead SX-56
You guys are good and quick....but!!! As I mentioned, I can't even see the Bootloader even after a reset and power button combo...nothing comes up or happens...the screen just blinks and then goes blank...should I open it up and disconnect the battery or something...? Right now I am just seeing the screen saying "Do not Remove...." and that even in a totally distorted form....
Try pushing a pin in the hard reset, push once only, leave it overnight, I think that is good as removing battery as it disconnects the connection between battery and mainboard as fas as I know. Next morning push once with oin again, you never know your luck. Its weird that the bootloader should be affected however the good thing is that your gsm seems ok and the xda is charging.
XDA Dead!
Thanks for the reply...I have just pushed the pin and am leaving the XDA in that state for the whole day...hope it revives back...its presently just giving me a garbled screen and nothing else...even when I press the power and hard reset together, it comes back to the garbled screen and nothing else...I'll take your advice and not touch it after the above for the day and let you know what happens, if there is any other advice I would highly appreciate it...
Bootloader Malfunction
You mentioned that your bootloader seems to be screwed up. Download the full version of XDA tools WITH the bootloader and Programme A. Grab yourself a new ROM of your choosing, lumpistefan's kitchen, etc. Then use the XDA tools to write the bootloader and the rom to your SD card. After that hard booting the device with the SD card installed should ask you if you want to flash the device.
I noticed that if you have XDA tools without the bootloader file it will write the rom to your SD and you will NOT be able to get to the flash your device screen.
This is the only way to do it since your device will not boot to a rom. Upgrades from manufactures and roms prepared with Programme A all require MS Active Synch AND a good working connection.
If you have a SD card prepared with the ROM and the bootloader the right way, it should almost be foolproof from what I understand.
Hope this helps, I was in much the same situation
XDA Dead!
Yups! I tried to boot it from an SD Card, its not exactly an SD Card but an MMC Card (128MB). It still comes up to the same garbled screen which is more garbled than ever before! Does not ask me for anything; or even confirms anything...It does not do anything else besides the screen even after a soft reset/hard reset or a combo hard/soft power button reset.
I'm really totally stuck...Any ideas will be much appreciated!
Thanks.
Your XDA is completely dead; you screwed OS ROM and bootloader.
Forget SD or Details method, it won't work for you!
Re: Dead SX-56
Can you help me fix it please? What do I need to do?
Bootloader
The more experienced members of this forum can correct me on this, but I have been under the impression that the SD method of flashing does not require an intact OS ROM or bootloader on the device.
If you created the SD correctly, it should contain its own bootloader. Just putting it in the unit and then reseting it should come up with the screen to flash the device.
Did you create the SD card with XDAtools? Did you also have the bootloader file in the /bin directory when you did it?
If a properly created SD "flash" card cannot fix your problem, then you really might have no choice to but to get it professionally repaired where the remove the chips themselves and replace them.
I think you may even be in luck. www.pocketpctechs.com probably can do this and they are located in Fountain Valley, CA about 4 hours away from you. They can also put in bigger memory and batteries at the same time at a discount if you are getting it repaired
Re:
Thank you so much for the reply...I will try it once more; although, yes I have tried the same thing before and made the MMC Card through the XDATools, but never hurts to try again...I'll double check on the bootloader again too this time...
If you can, please send me the contact information for the people who fix the XDA's professionally as you mentioned in the USA somewhere near me preferably, I am in San Jose, CA...I'll try to contact them also...
Best Regards.
Contact Information
Their website is www.pocketpctechs.com.
You can find all the contact information right there. As far as I know fountain valley is about 4-5 hours away from San Jose.
Similar problem:
I have a XDA I here, which has a similar problem:
It boots with the welcome to T-Mobile screen, and
it shows at the bottom of the screen 4.01.16 after a while R4.06 and after a while G32S54. The machine locks-up and does not respond to anything except the touch screen. If i tap the screen, the backlight turns on, and a
rotating 'wait' icon appears. That's it. I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD.
I guess the former user has tried to reflash the unit, and had put the OS overwriting the bootloader, OTOH, the unit seems to run *some* code, since it responds to taps on the screen, by turning on the backlight.
Any guru have any clue on this one? I could not find anything in the forums, while the forums are VERY helpful in the past.
GreetingZ,
Richard
Bootloader
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Re: Bootloader
ed207_us said:
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
Click to expand...
Click to collapse
I also have a good working unit, and testing my SD card, created with XDARIT in this unit tells me i need to press power -> reset to be able to
flash the unit. if i do'nt hold the power button, the unit boots normally.
ed207_us said:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card.
Click to expand...
Click to collapse
It is there. 'press action to download ROM, or press record to exit'
ed207_us said:
<<
Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Click to expand...
Click to collapse
I cannot connect the unit to activesync.
ed207_us said:
<<
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
Click to expand...
Click to collapse
I don' know the contents of the SD, since i created it a long time ago, but i really would appreciate is if you can email me a image of yours. Hope you are right and i can use the bootloader on your card to start this unit.
email size is no problem upto 100Mb
ed207_us said:
<<
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Click to expand...
Click to collapse
<<ed207_us wrote:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. >>
<<<RichardRosenberger wrote:
It is there. 'press action to download ROM, or press record to exit' >>>
It is only there when you have the SD card in the device, otherwise you cannot find it by moving around through the different menus.
XDAArit is completely outdated. You need to get their new tool.
XDATools can be downloaded from the website here. The best thread that talks about the tool is:
http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools
The exact link to get the tool and all the supporting files, including the bootloader is:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
When you install this version of XDAtools you will find a directory called binaries. Under it there should be a file called "bootloader_v5_15.nb0"
Use the tool to create your SD card with a .nb1 file of your choice. After that it should only be a matter of powering on the device with the SD card inside the unit.
I have 2 XDAs. 1 good en 1 have problem with bootloader and rom.
I can't access Wallaby bootloader en the OS don't start.
I backup it from good XDA in the bootloader (ce+Boot) and i pushed my SD in the XDA where problems are..
He don't work. How can I fix my problem..
Please Help...
I am not aware of what the (ce+boot) actually creates on the SD card. If that is the exact ROM that you want, I would suggest downloading the full version of XDA tools, and I think you can use it to copy the ROM from the SD card to a .nb1 file on your computer. Then follow the instructions I have already posted to make the working SD card that will flash the XDA.
When it comes to the SD card, the only time I have ever been successfull is when creating it with XDAtools with a .nb1 file and the bootloader .nb0 file inside the binaries directory.
That's it. I have never been able to do it any other way. Programme A does not count since it requires an active and working OS and connection to the PC and most people that are in trouble don't have that.
Hey guys,
first, im sorry for opening a new thread, but none of the other threads helped me.
I bought a HTC Touch 3G Clone in China:
ROM: 2.706.2
QUALCOMM 7225
528 Mhz
RAM: 192MB
NEXPERIA SY.SOL 5209
Windows 6.5 Chinese
HardSLP doesn't work. It cant get a connection to the phone, although ActiveSync has one.
Then i tried to upgrade with my 1gb sd-card. But none of the button-combinations of this forum work.
I tried some other comb. and found three of them:
green button + red button + power --> reset config
vol up + vol down + power --> calibration screen
vol up + red button + power --> a white screen with "downloading"-label
vol down + red button + power --> a green/white screen saying: Checking valid image file
I think the last one is important to install a new rom. After 10 seconds it says:
Step 3 error while updating
Card operate: read retry timeout
Then i tried several rom-versions posted here. Nothing happens.
I just want an english operating system...
I really hope someone can help me. Its driving me crazy...
Thank you for your help.
Buddy close this thread & go 2 Touch 3G General -where u have posted ur thread- & read other threads, many can help.
HSPL does not work 4 cloams!! & also u can't use those custom ROMs on cloam!
check http://forum.xda-developers.com/showthread.php?t=580367&page=3 but make the "hxxp" correct!
Also http://forum.xda-developers.com/showthread.php?t=657212 links.
Search more, u will find stuff. If u follow the General forum related 2 cloams (clones) u will get more! U shall use a ROM working 4 cloam. Mine is T3238+, I'll try 2 help as far as my knowledge lets me!
Thank you for your help.
Sure, I can post my problem there. But I already read them and it didnt help. I tried both of the ROM-files. I get the same error:
Step 3 error while updating
Card operate: read retry timeout
I have a 1GB sd-card, formated in standart windows-fat-format.
I think there must be another button-combination for the update mode.
But like i said none of the combinations mentioned in the board work, and there are plenty of them...
In your second link I have seen:
3) Boot into TF Update Mode by holding the Green + Confirm + Red + Power Button
I tried it, nothing happens (if the confirm button ist the round big one in the middle)... What should I do?
Hi again,
Yes, confirm = big button; only use the ROMs 4 cloam phones not those 4 real 1s.
Seems that ur phone starts reading the file but stops in the middle, this means u have gone 2 update mode, only it can't continue; try another SD card.
-- Mine is Touch 3G T3238+. By far NO key comb. has worked 4 me. Seems that these cloams don't have a booter like other 1s.
I turned off my phone -> connected it 2 PC w/ WMDC -> Vol. down + green + power => a menu screen appeared!! w/ options like "update OS", "update logo" & ...
C if this works 4 u, though "update OS" did not work on my phone but mine has sum other problems 2, so u give it a try.
-- Turn ur phone off, insert the SD & just turn it on normally, this shall start reading SD.
Don't make the card as FAT 32 (though not possible!), only FAT or FAT 16.
Don't put the ROM in a folder on SD, let it be on the root directory.
-- Once open SD w/ ur phone -as u open e.g. "My document" - & c what message it shows? Does it even read the card??
Thank you very much for your help. I finally made it.
The trick ist to use a ROM with a .bin-format and rename it to "k3img.bin"
The update mode doesnt accept other names.
I flashed my phone to windows mobile 6.1 eng. version.
Now i have a bunch of other problems. Bad key mapping, no camera... and the biggest problem: the phone doesnt find any storage cards.
Under Settings-System-Memory it says: "Total storage card memory: Not installed".
What can i do? I need that extra storage.... And now i cant get into the update mode because windows deleted the old button map. Tried any combination, doesnt work.
Please help.
Hi again,
Well, I am a noob myself!! unfamiliar w/ these phones!! but I think keys problem is bcoz of the ROM; though it is installed, but it's not the proper 1!
Check http://forum.xda-developers.com/showthread.php?t=662170&highlight=QUALCOMM seems that this "first aid" has helped!!
Trying another ROM, BUT now that u can't use SD ......!! also the PC does not run .bin or .upr files!! Mayb if u change the file 2 .exe, it gets installed (of course after sync.!)
2 get 2 update mode, c if connecting 2 PC (my prev. post) does any good!!
I don't know any way; In sum days I shall go 2 the phone service center 4 my phone; I'll ask 2 c if they knew any way & [/I]if if they let me know about it[/I]!!
pringo said:
Hi again,
Well, I am a noob myself!! unfamiliar w/ these phones!! but I think keys problem is bcoz of the ROM; though it is installed, but it's not the proper 1!
Check http://forum.xda-developers.com/showthread.php?t=662170&highlight=QUALCOMM seems that this "first aid" has helped!!
Trying another ROM, BUT now that u can't use SD ......!! also the PC does not run .bin or .upr files!! Mayb if u change the file 2 .exe, it gets installed (of course after sync.!)
2 get 2 update mode, c if connecting 2 PC (my prev. post) does any good!!
I don't know any way; In sum days I shall go 2 the phone service center 4 my phone; I'll ask 2 c if they knew any way & [/I]if if they let me know about it[/I]!!
Click to expand...
Click to collapse
Hey, I finally got it! I installed WM 6.5 ROM and my SD Card works! Key mapping is bad and the cam doesnt work but I dont really need it. The storage card was important. Now im really happy.
Thank you so much for your help! The "first aid kit" really helped in combination with the k3 IDT. You are my hero!
If somebody experience the same problems, I can explain in detail what I have done!
WOOO.........W, SO HAPPY 4 u I wish u find another ROM in future 2 make other stuff work 2!
U shall mostly thank others!! ......... OK, have fun w/ ur SD 4 now,,,, Hope it stays this way!!!!!!
hi i have the same trouble in a t3238 clone, i need to change the rom but i cant, can you help me writing step by step all procedure ? and where can to find the .bin roms = thanks
Hi,
Sorry my english but im from portugal and don't speak to much english.
I need a HUGE HEELP with my Huawei Ideos X5 (U8800).:crying:
I will try to explain:
After try update, the update fails and the phone "died" (bricked, i guess), but i searched about the problem where and got success ("U8800 Software Upgrade Guideline"), the phone "wake up" and got me to blue screen and pink screen (power + Vol +).. but then i dont know what do next and do ****
I mess up the partition and deleted some ones (the little ones), and the phone "died" again, but this time the steps that i used on the first time doest work any more. I try everything and no success :crying:
I'm a beginner in android, but this time i mess up , right ?
Is any solution for this ? To recovery the partition ? Don't know, need help. Can someone help me ?
my u8800 die after this ?
(I attach a "example" of the partitions i delete on windows 7 "disk management". Delete 2 or 3 partitons, i guess)
Plz answer me
What are the contents of the sdc1 (/cust partition with image folder inside it)?
The partition table looks fine though. And what do you mean by "died", just shut screen off? Try doing the update while attached to USB, or even without battery (using USB as power).
Blefish said:
What are the contents of the sdc1 (/cust partition with image folder inside it)?
The partition table looks fine though. And what do you mean by "died", just shut screen off? Try doing the update while attached to USB, or even without battery (using USB as power).
Click to expand...
Click to collapse
Thanks for the answer ,
I mean, my phone (huawei u8800) won't turn on.. is dead .. won't respond.. i guess that because i (dont know why) deleted some partitions "unallocated". And after that the phone doesnt turn on again.
the attachement that i put on the first question is just a example of the partitons.. before i mess up my partitions are like the image i attach. you understand ? sorry my english
I'm not dev and i send my phone to technical service two times. First time; dark screen, no respons any bootloop etc. and came back to with new main card because it was damaged. At second time was same as dark screen, no bootloop etc. and came back with new updated rom b528.
You must calm down.
Do you have b518 or higher version? If you answer is yes go to copy it sd card. But you must create a folder with named "dload". Your update.app must be inside "dload" folder.
Infact when you look at your version, u will see step1 folder. If you look in, you will see dload folder again. Copy or cut it and then paste to main directory.
Just relax, drink water or what if you want .
Replace your battery. When you connecting cable to pc or some have usb plug doesn't matter (tv,DVD player). IMPORTANT!!!UNINTERRUPTED POWER SOURCE. When you connecting cable to SOURCE you must press power button, volume + button and volume - button at the same time. If your problem is only software this is your medicine; DON'T FORGET IT: IDE(A)OS NOT DIE.
Thank you #dzo, #Blefish, #forumber and other dev.heros
(not to djuanight whatever)
Sorry for my poorly english.
rsim said:
I'm not dev and i send my phone to technical service two times. First time; dark screen, no respons any bootloop etc. and came back to with new main card because it was damaged. At second time was same as dark screen, no bootloop etc. and came back with new updated rom b528.
You must calm down.
Do you have b518 or higher version? If you answer is yes go to copy it sd card. But you must create a folder with named "dload". Your update.app must be inside "dload" folder.
Infact when you look at your version, u will see step1 folder. If you look in, you will see dload folder again. Copy or cut it and then paste to main directory.
Just relax, drink water or what if you want .
Replace your battery. When you connecting cable to pc or some have usb plug doesn't matter (tv,DVD player). IMPORTANT!!!UNINTERRUPTED POWER SOURCE. When you connecting cable to SOURCE you must press power button, volume + button and volume - button at the same time. If your problem is only software this is your medicine; DON'T FORGET IT: IDE(A)OS NOT DIE.
Thank you #dzo, #Blefish, #forumber and other dev.heros
(not to djuanight whatever)
Sorry for my poorly english.
Click to expand...
Click to collapse
I already have try that .. and no results[/B]
brunodpferreira said:
Thanks for the answer ,
I mean, my phone (huawei u8800) won't turn on.. is dead .. won't respond.. i guess that because i (dont know why) deleted some partitions "unallocated". And after that the phone doesnt turn on again.
the attachement that i put on the first question is just a example of the partitons.. before i mess up my partitions are like the image i attach. you understand ? sorry my english
Click to expand...
Click to collapse
If you deleted mmcblk0p2 (/dev/sdc2), then it's done for good (you deleted bootloader partition). The only way to fix it is through hardware modification, and we haven't covered yet how to do the software part yet. The "unallocated" parts just show Huawei's faults in the allocation. Ideally, there would be no such space between these partitions.
Blefish said:
If you deleted mmcblk0p2 (/dev/sdc2), then it's done for good (you deleted bootloader partition). The only way to fix it is through hardware modification, and we haven't covered yet how to do the software part yet. The "unallocated" parts just show Huawei's faults in the allocation. Ideally, there would be no such space between these partitions.
Click to expand...
Click to collapse
:crying: And what kind of modification hardware you mean ? if i take to a repair shop they can solve it ?
brunodpferreira said:
:crying: And what kind of modification hardware you mean ? if i take to a repair shop they can solve it ?
Click to expand...
Click to collapse
There's always JTAG, but our phone has 6 test pins that are used to check the phone's motherboard to see if all connections are working. One of those pins had to be shorted, which would let the phone turn on into QHSUSB_DLOAD mode. However, we haven't got farther than that. It's a risky procedure aswell.
The repair shop can use JTAG if they know, however most of them will just replace the motherboard for a nice fee.
brunodpferreira said:
Hi,
Sorry my english but im from portugal and don't speak to much english.
I need a HUGE HEELP with my Huawei Ideos X5 (U8800).:crying:
I will try to explain:
After try update, the update fails and the phone "died" (bricked, i guess), but i searched about the problem where and got success ("U8800 Software Upgrade Guideline"), the phone "wake up" and got me to blue screen and pink screen (power + Vol +).. but then i dont know what do next and do ****
I mess up the partition and deleted some ones (the little ones), and the phone "died" again, but this time the steps that i used on the first time doest work any more. I try everything and no success :crying:
I'm a beginner in android, but this time i mess up , right ?
Is any solution for this ? To recovery the partition ? Don't know, need help. Can someone help me ?
my u8800 die after this ?
(I attach a "example" of the partitions i delete on windows 7 "disk management". Delete 2 or 3 partitons, i guess)
Plz answer me
Click to expand...
Click to collapse
Huawei's out of the new models:Huawei honor 3 c
But do you still get to the pink screen? How did you "delete" those partitions?
the above in Portuguese
Mas ainda consegues chegar ao ecran rosa? Como é que apagaste essas partições?
There is no need to panic.
This happened with me also.
I guess you have tha dload folder and put the official update file into it.
Connect the USB cable to PC(I don't know what it does but it works).
Press VOL+, VOL- and POWER key
It will start installing.
Try both the official Huawei roms 2.2 and 2.3 in this way.
If if you have managed to get the pink screen. Try different recoveries and ROMS.
For me I put the following recovery
http://forum.xda-developers.com/showthread.php?t=1288223
And tried different Roms but only Cynmobile worked
http://forum.xda-developers.com/showthread.php?t=2044617
And after this I could flash the official Roms as it is.
Hi all,
Some days ago I tried to modify my system partition to have more free space to install jb roms.but when I tried to install the zip for the partition ,it failed. Now when I try to install the official update, it failed at step 2/2 just before the end.also if I connect the phone to the usb without battery it shows the image I attached.Can I do something or I bricked it?
Στάλθηκε από το Nexus 10 μου χρησιμοποιώντας Tapatalk