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.
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.
**UPDATE**
This method causes your serial number to change to 00000000 (which isn't a problem as such as this isn't currently used for anything) but there is a new method which involves directly hex editing the nv_data.bin file, which may be faster and does not change your serial number. You can find the details here: http://forum.xda-developers.com/showthread.php?t=843323.
**UPDATE**
First up I'll say that I'm not incredibly familiar with Galaxy S firmware changes/modding, and this mostly builds on work done in these areas, so not all these steps may be necessary but they worked for me. If someone can suggest a faster way to do this/unnecessary steps then please go ahead and reply with them!
This unlocked my Network Locked Australian Galaxy Tab and so I assume should work for others.
You should back up your /efs/ folder before you proceed as you may need this to undo if something goes wrong.
*I take no responsibility if something goes wrong!*
Requirements:
Root access
repair_nv_data.zip (from http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94)
Java
Busybox
The Android SDK for ADB, Root Explorer or some similar file system explorer/editor
(If you have US firmware with no Phone software, you may need to flash European firmware as described here: http://forum.xda-developers.com/showthread.php?t=838250 ).
Firstly, on your phone dial *#7465625# and check if the Network Lock is set to [ON], if so then your phone is locked (duh), so continue.
1. Use Superoneclick (http://forum.xda-developers.com/showthread.php?t=812367) to root your phone (the other z4root method may work as well, but this isn't what I used).
2. Either use ADB or some other method to rename or delete (backup first):
/efs/nv_data.bin.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
(I just used Root Explorer to rename them to something else).
3. Restart your phone and then go into the /efs/ directory and see if the 'nv_data.bin.md5' file has been re-created by your phone, as long as it has been created then you can proceed.
4. Go to http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94 and download the repair_nv_data.zip file (the credit for all of this mostly goes to that thread and helroz).
5. Install 'busybox' from the Market. Once you install it, you actually have to run it and properly install it (the Market app is basically an installer) - the files in the above zip have a dependency on this.
6. Extract the above zip to your PC, plug in your Tab in USB debugging mode. Run the Step 2.bat from the extracted file. You may need to allow the script super user access several times. This should copy the /efs/ and a bunch of files into a directory with a french name.
7. Run the Reparation_nv_data.jar file. (You will need Java for this step.) It will prompt you to enter two numbers, which are your pseudo-unlock codes. I entered '11111111' and '11111111' (eight 1's) both times. This rewrites the nv_data.bin file to be simunlocked with these details.
8. Run the Step 4.bat. Your superuser app (the one installed when you rooted using SuperOneClick) will need you to allow each command to have root access so keep an eye on your Tab. You may need to press y/n a few times if you encounter errors. This is uploading the edited nv_data.bin onto your Tab.
This batch file will stop several times and need you to hit a key when it pauses. My Tab rebooted halfway through this batch file - when it did this I waited for it to fully reboot back to the lock screen before pressing a key to make the script continued while the Tab was actually able to respond to its commands.
9. Towards the end of its execution it rebooted a second time. It paused during loading up and had some yellow writing on the screen saying it was updating media (I assume it was rebuilding the nv_data.bin). Leave it for a minute and it will prompt you to reboot/some other options. Just press whatever it wants (home I think) to reboot the phone - you don't want any of the other recovery options.
10. Go into your dialer and put in *#7465625# again and (hopefully) voila! Your phone should no longer be network locked. Try a SIM from a different provider to make sure.
Enjoy!
Edit: I had to go out and actually buy a prepaid SIM to confirm that all was working with a different provider. Attached are screen caps of my Tab on two different networks, as well as the network status screen, making/receiving calls etc. all works on both.
Awesome man, thanks.
This is much better than the 2 month wait we had for Galaxy S unlocking.
Hello, I'm french and i use your post to unlock my Galaxy TAB SFR ''réunion island'' and she is unlock thanks for your AMAZING post for unlock TAB
Ps: For unlock my TAB by SFR REUNION, he tell me 150 Euros.... Vive smithdc & helroz
Works well! I had little trouble running java on windows7. But changing compatibility mode to windowsxp sp3 and check run this program as an administrator solved the problem.
Thanks for easy guide!
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
smithdc said:
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Click to expand...
Click to collapse
Running the jar file. I didnt know how to run it.
Sent from my SGH-T959 using XDA App
Does the sim card and/or sd card should or should not be plugged in during the unlocking progress?
It shouldn't make a difference Zeron.Wong.
jay_jay_n said:
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
Click to expand...
Click to collapse
Traditionally, AT&T and T-Mobile hardware used different radios, it was more than just firmware. That's also true on the little brother Galaxy S series, the Vibrant has a different radio than the Captivate (though the Vibrant radio DOES have 1900 band in the hardware, for some reason).
Kudos to smithdc for this awesome guide! I saved a lot of money thanks to him. Congrats again.
Bump, is there any way to sticky/pin this for people?
So your saying if I use this method and install my tmous unlimited sim I can get calls and 3g or do I need a prepaid sim
I'm not sure on how T-Mobile are blocking, but if it IS my IMEI then you would have to use a SIM from a different network.
If they are blocking your IMEI on their network, then you would have to use a SIM from a different network (as a different network, wouldn't be blocking this IMEI number). Changing it to a different SIM on the same network won't help as your IMEI is for the device itself.
I just want to clarify something..
I have a T Mobile Tab and want to use a SIM I have for ATT.
Will I have to flash my device with the EU firmware first in order to get the phone software on it..then do the rest of the unlocking steps?
Assuming thats correct..after unlocking it I then can put my ATT sim card in and it should work for calls and data (Edge only) with not having to tweak any setting at all? Or do I have to set up my wap.cingular connections for the data like on a WM phone on ATT?
And if I want to get back to original out-of-the-box firmware from T Mobile (like if I had to send it in for repair) I just have to flash stock T Mobile firmware and its back completely to original?
Thanks..and wow am I loving this TAB !!!
You'll need to set up your APN data for AT&T, yes.
Thanks for the fast reply. As for the flashing of the EU rom..is that the only/best way so far in order for me T Mobile Tab to get the radio software on it. I was thinking I saw an APK for the radio software someplace but did not know what way was better.
I just want to be 100% sure bfr I take the jump to unlocking and playing with the phone part
thanks
I got a quick couple of questions:
1. If I restore original firmware (Canadian), does it relock my phone?
2. Where can I get the Canadian firmware release? I see EURO and US, but no Canadian.
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
clubtech said:
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
Click to expand...
Click to collapse
Yes, it will set your IMEI to a bogus one that will get your T-Mobile internet access disabled after 1/2 hour.
New update is up!
Version is : V100R001C00B528G001
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
Upgrade How-to
It has all languages android have!
This upgrade need to accomplish 1 upgrade package’s upgrade in the one step below, the file name can’t be revised:
Step1: include UPDATE.APP
- Prepare a formatted Micro SD card which at least has 512MB available space. Make sure your handset is powered off and then insert the MICRO SD card into the handset.
- Make a “dload” directory on SD card root directory
- Copy the “Step 1\ dload\UPDATE.APP” to SD card.
- Long press volume up + volume down + power button on the handset to startup you device until device into upgrade model, the handset will upgrade and shutdown automatically.
- After upgrade success , Restart the handset.
- It will reboot few times.
- Check the Build number is 100R001C00B528G001 . You can see it in “Settings”->”About Phone”..
Possible bugs!
- When the wifi open and screen is off phone reboots.
- Some phone gets imei=0 (please backup your imei)
- Not sure but I have network issues. Sometimes my phone gets "unreachable" state even I have 4 bars.
- There is a widget problem, "The widget loading problem" after each reboot.
- On calls your sound is very husky. You can try to solve changing build.prop "ro.config.dualmic=true" to "ro.config.dualmic=false"
- Some users reported screen lag, freezes and and glicthes.
- Sound (your sound from calls) not very good.
- Widgets get "The problem loading widget" on every reboot.
- Haptic feedback not work on capatitive keys.
Warnings!
- There is no safe way for downgrading.
Downgrading!
I go back to cm7 like this;
- Copy B138 dload to internal memory - This is important.
Power off your phone go to pink screen. Notice: you can't go the pink scren without sd-card. So, after copying dload directory insert sd card.
- Go to pink screen
- In pink screen, I replace all the files from my 2.2 backup. (If you don't do that, downgrade not work. Its failed step 2/2)
- Remove sdcard from phone and start the B138 update like always.
- After installing phone should open normally.
- Once your phone open normally, you can install cwm and flash any rom you want it.
I noticed cwm data backups not works, I don't know why its not worked. Maybe some experience person can explain that to us.
- Please notice, Even if this version worked on my phone, that doesn't mean it will work for you. You can try, I'm not responsoble of anything
Mirrors for those who hates china internet connection speeds too:
http://www.uploadstation.com/file/DBH479d
http://ul.to/3qi60wcj
http://www.fileserve.com/file/FmWvum2/U8800_V100R001C17B517G001_Tommix_China_sucks.zip
http://www.filesonic.cz/file/4048086954
http://uploadbox.com/files/1d337e044c
http://www.crocko.com/85045EFF9D6E4...00_V100R001C17B517G001_Tommix_China_sucks.zip
Epic fail. Its don't include market or gapps!
Cannot download, seems fine until downloaded the half size and after that goes very fast to end, resulting a damaged archive. Maybe too many trying to download?
Anyway how you find these links?
If from that page press the label to go to index, I cannot find this link. the froyo rom, not this link.
Özgürce said:
Epic fail. Its don't include market or gapps!
Click to expand...
Click to collapse
really? what is wrong with this people?
Can someone please re-upload it to another site I got a corrupted download
Sent from my u8800 using xda premium
Mirrors
Uploaded to some mirrors as Huawei site is taking forever to download.
Mirror 1
Mirror 2
Mirror 3
Mirror 4
Mirror 5
Hope this goes faster! http://www.mediafire.com/?doievioa1ybb9zn
Hayden18 said:
Can someone please re-upload it to another site I got a corrupted download
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
maybe you can try this link : http://115.com/file/c2bu9jd6#
someone download from the official website and upload to the above website
why dyou even want to install this without market? I mean... seriously, no market? rofl
swayjd said:
why dyou even want to install this without market? I mean... seriously, no market? rofl
Click to expand...
Click to collapse
try installing market.apk ......
will someone post quadrant score plz
Hayden18 said:
Can someone please re-upload it to another site I got a corrupted download
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Give me 10 minutes and I'll re-upload it.
What about installing instructions?
The pdf file in package is in Chinese.
sport_billy said:
What about installing instructions?
The pdf file in package is in Chinese.
Click to expand...
Click to collapse
Try this to translate...... http://translate.google.com/
PDF contains as fallows
11-30 Page 1 of 2
U8800 Gingerbread upgrade instructions
Reminder: 1, This package only applies to U8800, other models including U8800 + / U8800Pro are not
Using the software package in the "Settings" menu -> "About phone" menu to view models.
2, provides the official temporarily retreated from Android2.3 Android2.2 way back.
3, Brush risk, machine You need to be cautious.
1, note
a) upgrade process will erase all user data (such as contacts, SMS, MMS, etc.), the
Please be sure to upgrade before your users to backup data to an external SD card or computer.
b) Make sure the battery before upgrading to support more than 30 minutes to ensure complete support of the upgrade process.
2, the version of the functional description
This version, based on the original version of Froyo, mainly to do the following changes:
a) upgrade to the Gingerbread 2.3.5 version of the Android version.
b) In the original version of Android adds ease of use UI features and better functionality of Huawei, to better enhance the user
Use of experience.
3, the upgrade procedure
3.1 from Android 2.2.2 upgrade to Android 2.3.5 guide
This upgrade requires the following two step CPC 2 upgrade package upgrade, all file names can not be changed:
step 2 contains UPDATE.APP (G version of the function of the main package).
step 3 contains UPDATE.APP (indicated by package carriers).
3.1.1 Prepare a capacity of not less than 512M SD card;
3.1.2 SD card root directory create dload directory, copy the update step 2 in UPDATE.APP to dload
? ? ?
?
2011-11-30 Page 2 of 2
Directory, the phone off, the SD card into the phone, the (left thumb) while holding the volume up and down keys,
And (right) press the power button to turn the phone will automatically upgrade, the phone automatically shut down after the upgrade is complete, remove the
SD card;
3.1.3 step3 in UPDATE.APP replaced with an SD card dload directory UPDATE.APP, repeat
Step 3.1.2, in order to upgrade step 3 UPDATE.APP (while holding the volume down key, long press the Power
Key to boot).
3.1.5 upgrade is successful, the phone reboot to restore the factory into the interface to restore the factory is completed, the phone re-re-
Kai. Complete Android 2.3.5 version of the full upgrade.
3.1.6 Make sure the version number after boot as U8800V100R001C17B517G001, in the "Settings" menu
-> "About phone" menu, check the version number.
krish_nank said:
Try this to translate...... http://translate.google.com/
Click to expand...
Click to collapse
Thank you.I did that.
I want human translation.
If someone who speaks chinese can translate this it would be very helpfull.
286420123 said:
OK,i really doubt if you are mentally impaired,the rom is only a trial one , and only for trial in china , it is only uploaded in chinese local host,if you really want to say sth,i'll give you the reason that you country is so ..... that can't aford the expense of the international data exchange ,so you can only have a **** speed,if you want to speed up , you can just migrate!
Click to expand...
Click to collapse
Trial version means wont work after few days or is it like only testing purpose??? ...
Added root insruction. Its way too easy.
Another Mirrors for those who hates china internet connection speeds too:
http://ul.to/3qi60wcj
http://www.uploadstation.com/file/DBH479d
http://www.fileserve.com/file/FmWvum2/U8800_V100R001C17B517G001_Tommix_China_sucks.zip
http://www.filesonic.cz/file/4048086954
http://uploadbox.com/files/1d337e044c
http://www.crocko.com/85045EFF9D6E4...00_V100R001C17B517G001_Tommix_China_sucks.zip
To late, just upgraded to a Samsung galaxy note
my last ever Huawei, their after sales support sucks for every phone, why can Korea make better products than China? Better support, better phones, higher quality, China keep trying and keep failing in the support part of most products for some reason, I can't figure out if its a culture thing or a government thing that makes them not care about their customers
Sent from my GT-N7000 using XDA App
Hey guys
I got the Galaxy S4 i9500 with the stock firmware (build number JDQ39.I9500XXUAMDK) running Jelly Bean 4.2.2. I don't know what's the region but I bought it in the US if it helps.
I got a few problems/things I wanna do:
1. I want to change my stock rom to I9500XXUAMDE (ILO region) because my original rom doesn't support Hebrew menus.
I found a link to a file but I can't post it cuz i'm new. Its name is "Samsung-Updates.com-GT-I9500-ILO-I9500XXUAMDE-1365755329.zip"
For some reason I can't download the file from hotfile... just when the download is about to finish, the download stops
I tried downloading on 2 different computers in my house, both trying with firefox and explorer browsers (every attempt took about 2 hours to "complete" its exhausting!!!!) - could someone download it and upload it as a torrent link or provide some other way to help me?
2. I want to root the device while still leaving the stock recovery and rom, first of all - should I do it before or after putting the new rom?
and second - is it still possible to update the firmware after rooting?
3. Sometimes my phone decides to lose its reception - the circle with the line crossing it doesn't show up, just the reception triangle in the top becomes empty (with no lines) and the data network symbol disappears for a few seconds. How do I stop it from happening?
4. I bought a new 32GB sdhc class 10 card (Kingston) and I can't change anything in it unless I connect the phone to my PC with the card inserted. I put the card in a different phone (i9000) and I didn't have any problems with writing there. What can I do to make the card writable, and by the way... after rooting my s4 I can move apps from the internal SD to the external one right?
Sorry for the loooong story and thanks in advance,
Gilad.