Related
I had/have bricked my X10 Mini Pro
I followed the instructions here
http://forum.xda-developers.com/showthread.php?t=743800
and after receiving NO errors and thinking everything was finished unmounted from the host machine and unmounted the sd card and re-booted the phone
Sadly it all went tits-up.
It booted into the locked screen and the reolution was way lower than before
The GUI was gone leaving only the activity/notification bar - the rest of the touchscreen was a fetching blue, with no applications, no corners, no nuffink.
Somewhere in this forum was a tip to start PCC and hold down the back and home keys, tap the power button and when the screen goes black connect the phone to the PC.
This gave me back a GUI but I have lost some Apps and more importantly it has booted into airline mode and no amount of turning 'Airline Mode' on/off with the power button will get rid of the airplane icon in the notification bar. So I can't get into my phone carrier nor any wireless networks.
So a few questions before I start again
Build.Prop file
changing numbers to have an unbranded phone for Australia ?
- is it just a matter of opening the file with gedit and changing the string with something from the list for Australia then saving or need I also change locale to AU ?
ok assuming that I only cut 'n' paste the 1234-1234, or whatever the number is I need to use to allow SEUS to update the phone for me, into the build.prop file then save it to copy from the SD card into the phone's system directory
( ./busybox cp /sdcard/build.prop /system/ )
I think that command roughly translates to " run busybox to copy the build.prop file on the card into the system sub-directory of the phone"
doesn't it ?
so, to continue this example,
I am in Australia,
I have a phone that used U20a firmware from this line
U20a WORLD-1-2-5 CDF1238-2298 1239-2226 3 AU/Black
I would cut the 1239-2226 and paste it into line #3 of the UK generic .prop file
ro.product.name=U20i_1238-0199
or do I change the line to read ro.product.name=U20a_1239-2226
or am I barking at the wrong tree ?
and
#68 ro.product.locale.region=GB
should that now read
"ro.product.locale.region=AU"?
hey mate hope this helps:
backup your build.prop first
open build.prop and replace the 1234-1234 values with the values directly after CDF, in this case 1238-2298.
do the following:
adb push build.prop /sdcard/build.prop
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
busybox cp /sdcard/build.prop /system/build.prop
exit
Now run update service.
it will ask you to connect your phone to the system. You will need to turn your phone off, hold the back button and connect the usb then after that just follow the prompts.
goodluck
Am I editing lines
#3 ro.product.name=U20a_1238-2298
AND
#8 ro.build.fingerprint=SEMC/U20a_1238-2298/SonyEricssonU20a/delta:1.6/1.1.A.0.8/1:user/release-keys
===
backup your build.prop first
===
I assume this is
./busybox cp /system/build.prop /sdcard/
Boo hoo hoo
That didn't work, having rooted the phone (I assume that when I connect it to my PC run CMD.exe and in the terminal run 'adb shell' then su the SuperUser application opens up in the phone to allow/deny is an indication that I have root)
I have edited the generic UK build.prop file to change it to an Australian Vodafone build.prop file ---I think ---
Exited out of the adb shell, exited out of the command line interface
unmounted the phone from the host machine
unmounted the client - the phone
shut down the phone
removed the battery for at least 5 seconds
during which time I completely removed all traces of SEUS using a Windows application called CCleaner
and reinstalled
opened the Update Programme
put the battery back in the SE phone
held onto the Back Button as if my life depended on it
connected the phone to the PC
SEUS says ..........
wait for it ..............
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
i had the optus firmware but since i live in china now i have been using the chinese firmware. do system restore and see how that goes, otherwise get the optus system installed and update it...but as far as i know everybody should be upgraded to 2.1 by now...
Also all you have to do is just edit the build.prop and restore the original firmware through pc companion... and then try to get the 2.1 update hope that works mate
saywot said:
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
Click to expand...
Click to collapse
You should have used "repair". That will work.
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
There isn't a 'repair' option any more with SEUS
and I keep getting the "No new software for your phone" message when attempting to repair using PCC
I'm guessing that I need to edit something else because I have some sort of a VFE file system version
Can I edit the firmware version in the build.prop file to something else
- then ask PCC to repair ?
Hmm
I just did the HBBHBHHB shuffle and see that in the software info section there appears to be an inconsistency
there is a different identifying strings of numbers for
- Phone software version
- S1 Boot Version
- ETS Sofware Version (whatever that is !!)
- Customization Version
I give up
I have edited the build.prop file with quite a few CDF numbers
re-booted
connected to SEUS
only to be told
"there is no new software for your phone"
I am starting to think that there will never be any 2.1 juiciness
I've tried Telstra AU, I've tried 3 Au, and Vodfone
- nothing and am now at my wit's end
And it's not as if this forum is bubbling over with suggestions as to the reason why a rooted phone can't have different firmware installed so it may have an OS upgrade
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
I decided to just dump the generic UK U20i build.prop file into the system directory and overwrote whatever I had there (the older one was saved as build.prop.bak)
This still didn't get me any software updates from SEUS - if that's what Sony is calling the next Operating System.
So apart from copying and pasting the whole build.prop file I want to use and asking what EXACTLY needs to be changed.
I have a question or two
-- "VFE-1-8 1.1.A.0.8" how can I get it changed to 'World 1-2-5 ?
-- and no matter what I do to the customisation version using an edit or two of /system/build.prop the software version stays the same and this is why I think I keep getting a "No New Software For Your Phone - try again later" from both SEUS and PCC
and the Model Info always reports U20a
as always any help or suggestions will be gratefully received
saywot said:
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
Click to expand...
Click to collapse
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
My sincere advise to you is spend 10 euros and get it reflashed by these guys http://www1.davinciteam.com/index.html
Good luck.
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
Click to expand...
Click to collapse
Now you tell me !
I know what I have been doing is futile and wasting my time.
But the guide is NOT simple for some of us less-talented people.
It doesn't say whether to replace all instances of the xxxx-xxx number in the build.prop file or only one,
I'm still not clear where there is a mention of CDFxxxx-xxx yyyy-yyyy whether I should use xxxx-xxxx or yyyy-yyyy in editing the properties file
Also the phone is a u20a phone, the UK Generic file is for u20i devices, and the guide doesn't make any distinction between the different hardwares - and they are different
In which directory does PCC keep the downloaded firmware that I am to delete?
'Dashboard' 'Drivers' 'Languages' or 'Skin' are the choices of directories, the rest of the C:/Program Files/Sony Ericsson/Sony Ericsson PC Companion/ folder are individual files - dlls exes etc etc
So to start again
I am about to upload (via the CLI in Windows) so
one last question (which is really the first question)
which line do I change in the build.prop file
- I am now assuming from the tone and content from #vlissine that I am changing too much so it's one line with one new number
and is it the string of numbers attached to the alphabetic CDF or those immediately following the CDF alphanumeric string in the u20a listing?
This is sort of the firmware I'm after
U20a WORLD-1-2-5 CDF1239-5023 1238-9150 Telstra AU/Black
which is to ask - do I use "1239-5023" or "1238-9150"
B.T.W.
if the phone has 1.1.A.0.8 firmware
and the build.prop file has 1.2.A.1.174
doesn't that create some sort of 'inconvenience' for me ?
OK this is a Guide on how to Flash Xbmod & Yuki’s WP7 ROM (Mango 7720). It is not a replacement of the original thread simply an accompaniment, continue to use other thread to post issues and asks.
PLEASE READ / PLEASE READ / PLEASE READ / PLEASE READ / PLEASE READ /PLEASE READ / PLEASE READ / PLEASE READ / PLEASE READ
This sometimes causes offense- If you ask a question that has been answered here! You will not get an answer on the board–
If I link a thread visit the page and read the instructions and thank the person for taking the time and effort.
History
There are two ROM’s made by XBmod and Yuki (within a few days of releasing the ROM Yuki retired from XDA, may they RIP or be resurrected in the future) XBmod continues to build and offer solutions. But understand that you are indebted to them and others – for providing the ROM.
Concept
To build a WP7 ROM that can be updated by Zune when MS release updates and Also so that Dev’s or anyone can develop custom CAB’s to be sent to the device without the need to reflash or mess with the system…….
The ROM
Both are Unbranded i.e. Vanilla flavor i.e. No carrier branding and you have Root access.
There are two differences between V1 and V2 ROM’s
1. V1 - HD2_Updatable_XBmod_Yuki_v1
a. Radio: 5.69.09.05a_22.50.50.21u
b. was an attempt to try and get he Sdcard working for other things but it failed, V1 remains for future development only
(Feedback from those testing V1 was that the Radio caused extreme battery drainage and the SD card created more issue than good, so V2 was born. V1 is left for others to play and possibly future development, to see if they can eventually get Dual boot to work – but it may never occur and quite frankly this ROM is so Stable & Pure and running on the best device ever, that you don’t need another OS)
2. V2 - HD2_Updatable_XBmod_Yuki_v2_native
a. Radio: 5.51T.09.29a_22.32.50.10U
b. Formats the SD card like a native WP7 device
(Feedback about battery performance has been for most, positive with a few exceptions will attempt to build country table in Appendix)
Common Questions
Q. Which ROM should I use?
A. Use the V2 ROM for obvious reasons.
Note: When you flash you will LOSE ALL DATA from your SD card, so if you need it - back it up! Also some SD cards present issues so be warned not all work…..
Make sure it’s a SD card that works and is supported, otherwise you could face frequent reboots / freezes / restarts / loops. SandDisk seems to be the best so far try to use class 4, you can use, 2GB, 4GB, 8GB, 16GB and even 32GB
Q. Can I Dual boot and Run Android?
A. Yes. XBmod has released a CAB that can be used to unlock the SDCard for Dual boot.
Q. I’ve installed V1 should I move to V2?
A. that’s up to you, but the general consensus is Yes move to V2
Q. I’m on V1 do I need to Start right from the beginning – re-run the whole Process?
A. Update oriignally yes, but we have a report that someone has gone straight from V1 to V2 without going back to stock rom (WM6.5) by simply flashing V2 on top of V1. No reported problems. So, it's up to you...
Q. Do I need to change the HTC HD2 name in about to HD7
A. No the HTC HD2 is just afriendly name, it wont and can't cause any problems anywhere. The phone is registred as an HTC Schubert (HD7)
RADIO:There are two Radios:
The first which you install during the initial set-up and another which is Baked into the ROM. Some folk who want to play and experiment will want to change the Radio in the ROM – you can do this and more about that in the Appendix:
UPDATEL: XBmod is working on a CAB to change the Radio in the ROM, thus in the future you will be able to send the CAB and change the Radio.
What do I need?
HD2 unlocked and a WP7 Activation key (search the forum)
Hard SPL v 2.08 or higher
I used HSPL4 and selected HSPL2.08.
WP7 doesn’t support HSPL3.03/OSPL3.03. You need to select HSPL2.08 to run WP7 & MAGLDR.
Radio which supports 576 RAM. (Radio 2.15.50...)
I used Leo_RADIO_2.15.50.14**:
Magldr1.13
Windows Mobile 6.5 Stock ROM
I used World Wide English (WWE) 3.14.405.2
Zune Download and Install the lastest version of the client.
WP7 Update Cab Sender
Download and extract to a folder on your PC, this will be the tool used to send custom packages (CAB) to the device and offer backup and restore features:
HD2-7720fix
Extract to a Folder
The V2 ROM HD2_Updatable_XBmod_Yuki_v2_native
Extract to a folder
DeviceProvisioning.cab
To be placed into “WP7 Update Cab Sender folder” later. Do not Extract!!
UPDATE: XBmod has released a new SDCARD UNLOCK TOOL. You are now able to Read and Andriod PARTITION and UNLOCK all your locked Cards.
Custom and Special CAB's:
DEV_STORAGELOCK.cab (this will install the unlock tool for your sd card (providing the possibility of dualboot))
DEV_STORAGELOCK_REMOVE.CAB (as always a second CAB removing the above function "unlock tool" Warning your SDCard will be relocked at reboot resulting is dataloss.)
The Install Procedure
Note: should you be familiar with custom ROM's and have following already installed on your device:
A) hard spl
B) magldr 1.3
C) the correct Radio!
D) then proceed directly to Section 7 and follow instructions "restart your phone and get into magldr menu by pressing and holding the red button then follow steps from Section 7. If you do not have the above installled, proceed from the Step 1 . Thanks to bryangopan
Install
1. Install Hard SPL v 2.08 or higher
2. Install Windows Mobile 6.5 stock ROM
Make sure you’ve got more than 50% power on the device.
• Unplug USB cable
• Power Off device.
• Press and hold volume down button and press power button to start again.
• You will be presented with a tricolor splash screen.
• Connect USB cable to PC
• On the Tricolor splash screen you see “serial”; change to “usb”, if not unplug and plug the cable back in.
• As Administrator Run the WM6.5 ROM Update and follow instructions, your device should now be flashed with WM6.5.
If you have installed a ROM with Radio 2.15.50.** then you can skip the next Install (3) and move directly to section (4). If you are unsure perform section 3, it wont break antything.
3. Install the Radio 2.15.50.** to the device, it installs through the same method as above
• Power Off device.
• Press and hold volume down button and press power button to start again.
• You will be presented with a tricolor splash screen.
• Connect USB cable to PC
• On the Tricolor splash screen you see “serial”; change to “usb”, if not unplug and plug the cable back in.
• As Administrator Run the ROM Update and follow instructions, your device will be flashed with right Radio
4. Turn on WM6.5, using the format tool in WM6.5 format your SD card.
5. Install Magldr1.13
• Power Off device.
• Press and hold volume down button and press power button to start again.
• You will be presented with a tricolor splash screen.
• Connect USB cable to PC
• On the Tricolor splash screen you see “serial”; change to “usb”, if not unplug and plug the cable back in.
• As Administrator Run the ROM Update and follow instructions, your device will be flashed with right Radio
6. When you’re Device Restarts, on the device screen you will see the Magldr menu, use Volume Up and Down to navigate, Answer Call (to Select)
Move down to last option and power it down.
7. Go to Magldr menu, do this by Holding the Power button on the device while powering the device up again
• Navigate using Vol Down and Up and use the “Accept Call” (green key) to Select feature
• Move down to and select Services
• In Services menu select option 4, uselast24nand.
• You will auto return to main menu
• Move down to and select Services
• In services menu select option 5. clearsd MBR.
• Confirm selection.
• You will auto return to the main menu
• Select option 5 usb flasher.
• The screen changes showing you USB Flasher mode / Wait USB
• Make sure you’ve connected the usb cable to the HD2 and PC
8. download and Extract HD2_Updatable_XBmod_Yuki_v2_native.zip (7004)
• This should be extracted to your PC, in the folder locate DWI.exe
9. As administrator Run DWI.exe follow the instructions and flash the rom.
• Once WP7 has been flashed (7004) it is important that you go set the Time and Date to match the Time and Date on your PC, otherwise Zune will not update. You do Not need to Sign into Windows Live or Activate the device at this point, not until you have flashed 7720 it makes no difference if you activate now you will only need to do it again later.
• Start the Zune and it should Detect your HD2
• In Zune go to settings / Phone and check for updates updates, once Zune finds the update, press ok and update now.
• This will be the (7008) update and your phone will automatically restart show you progress and eventually show successful.
• Once completed Zune will check for another updates and find another update this is the move to (7392). Press Update Now and once successfully completed you will be on 7392 this is NODO.
10. Optional.
• If you want to wait for the official release of MANGO through Zune then start using your WP7 by activating it etc and stop here.
• If you can’t wait and want more then continue……
11. HD2-7720fix.rar
Extract to a Folder
Within there are two sub folders
MangoRTM
update tool
Open the "update tool" folder and run either x64 or x86 to install the program according to the version of Windows you have. You will see it run once and exit.
Exit Zune make sure it’s not running.
12. WP7 Update Cab Sender.zip
Extract to a Folder
Download and extract to a folder on your PC, this will be the tool used to send custom packages (CAB) to the device and offer backup and restore features:
13. DeviceProvisioning.cab
Do not Extract!!
Copy this file into the “WP7 Update Cab Sender” folder.
Then run the “WP7 Update Cab Sender.bat”A DOS Window will open
╔════════════════════════════════════════════════════════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠════════════════════════════════════════════════════════════════════╝
╠══════» S •(S)end Cabs to device
╠══════» B •Send Cabs to device with (B)ackup
╠══════» R •(R)estore device backup
╠══════» L •Read last Update (L)ogs from device
╚══> Your choice: S
Press “S”
The program will send the CAB to your phone, which will automatically restart the HD2 and show progress, once successful.
You will see this message in the DOS Windows
The device has been updated to version ****************
╚══════» Done
Exit MS dos Window
Delete DeviceProvisioning.cab from the “WP7 Update Cab Sender” folder.
14. Zune update 7712
Launch Zune and check for Updates it should find 7712 and Update Now. The update will take about 1.5 hours.
Once you are done with 7712 update you will see update successful
Exit Zune.
15. HD2-7720fix.rar
HD2-7720 Folder
Within there are two sub folders
MangoRTM
update tool
Open the MangoRTM folder and copy the files (If you know which languages you need, only take the ones you need, if you are unsure take all 8) copy them to the “WP7 Update Cab Sender” folder
Make sure you deleted deviceprovisioning.cab before and Zune is NOT running
Then run the “WP7 Update Cab Sender.bat”
A DOS Window will open
╔════════════════════════════════════════════════════════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠════════════════════════════════════════════════════════════════════╝
╠══════» S •(S)end Cabs to device
╠══════» B •Send Cabs to device with (B)ackup
╠══════» R •(R)estore device backup
╠══════» L •Read last Update (L)ogs from device
╚══> Your choice: S
Press “S”
The program will send all the CAB’s to your phone, which will automatically restart the HD2 and show progress, once successful.
You will see this message in the DOS Windows
The device has been updated to version **************
╚══════» Done
Exit MS dos Window
Delete the CAB’s from the “WP7 Update Cab Sender” folder.
You’re now on 7720 MANGO
DO NOT STOP HERE
16. A Hard Reset is recommended.
Switch off the phone when the Magldr screen displays and you see
"Go Go Go 12345"
Press and Hold the Volume Up and Down keys at the same time.
If successful
You will see a white screen explaining that data will be erased,
Press Volume Down and Press Volume Down again, this is a hard reset.
Once you phone restarts, you can proceed to configure it, enter your activation code, Windows Live ID etc and set up your accounts.
Welcome to 7720 MANGO
Note:You can send other CAB’s to the phone by copying them “WP7 Update Cab Sender” folder and run the “WP7 Update Cab Sender.bat” do one at a time
Appendix
Adding Custom CAB's
Optional Add-on’s & Custom modifications
Please refer to this Thread by XBmod for links to additional CAB and additional Language packs.
The Concept:
Copy additional CAB file’s to the “WP7 Update Cab Sender” run “WP7 Update Cab Sender.bat” to send the file, you phone simply needs to be turned on and connected via USB to your PC.
Download the CAB you want and to a folder on your PC, you do not need to extract CAB’s.
You copy each CAB one at a time into the folder and use the tool to send custom packages (CAB) to the device and offer backup and restore features:
your_choice_.cab
Do not Extract!!
Copy this file into the “WP7 Update Cab Sender” folder.
Then run the “WP7 Update Cab Sender.bat”A DOS Window will open
╔═════════════════════════════════════════════════ ═══════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠═════════════════════════════════════════════════ ═══════════════════╝
╠══════» S •(S)end Cabs to device
╠══════» B •Send Cabs to device with (B)ackup
╠══════» R •(R)estore device backup
╠══════» L •Read last Update (L)ogs from device
╚══> Your choice: S
Press “S”
The program will send the CAB to your phone, which will automatically restart the HD2 and show progress, once successful.
You will see this message in the DOS Windows
The device has been updated to version ****************
╚══════» Done
Exit MS dos Window
Delete your_choice_.cab from the “WP7 Update Cab Sender” folder. Send more or finish.
Language: In the MangoRTM Folder the files below are language packs.
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_0c0a.pks.cab
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_040c.pks.cab
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_0407.pks.cab
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_0409.pks.cab
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_0410.pks.cab
Diff-7.10.7712.60-7.10.7720.68-armv7-Retail-Microsoft.Lang_0809.pks.cab
Locale Code Table from Microsoft
Language in ROM
0x0c0a 1252 Spanish: Spain (Modern Sort)
0x0410 1252 Italian: Italy
0x040c 1252 French: France
0x0407 1252 German: Germany
0x0409 1252 English: United States)
0x0809 1252 English: United Kingdom
Optional Languages
Note: you must send both CAB's
LANG_0404_7661.cab & LANG_0404_7712.cab
LANG_0405_7661.cab & LANG_0405_7712.cab
LANG_0406_7661.cab & LANG_0406_7712.cab
LANG_0408_7661.cab & LANG_0408_7712.cab
LANG_040B_7661.cab & LANG_040B_7712.cab
LANG_040E_7661.cab & LANG_040E_7712.cab
LANG_0411_7661.cab & LANG_0411_7712.cab
LANG_0412_7661.cab & LANG_0412_7712.cab
LANG_0413_7661.cab & LANG_0413_7712.cab
LANG_0414_7661.cab & LANG_0414_7712.cab
LANG_0415_7661.cab & LANG_0415_7712.cab
LANG_0416_7661.cab & LANG_0416_7712.cab
LANG_0419_7661.cab & LANG_0419_7712.cab
LANG_041D_7661.cab & LANG_041D_7712.cab
LANG_0804_7661.cab & LANG_0804_7712.cab
LANG_0816_7661.cab & LANG_0816_7712.cab
0x1404 950 Chinese: Macao SAR (Traditional)
0x0405 1250 Czech: Czech Republic
0x0406 1252 Danish: Denmark
0x0408 1253 Greek: Greece
0x040b 1252 Finnish: Finland
0x040e 1250 Hungarian: Hungary
0x0411 932 Japanese: Japan
0x0412 949 Korean (Extended Wansung): Korea
0x0413 1252 Dutch: Netherlands
0x0414 1252 Norwegian: Norway (Bokmål)
0x0415 1250 Polish: Poland
0x0416 1252 Portuguese: Brazil
0x0419 1251 Russian: Russia
0x041d 1252 Swedish: Sweden
0x0804 936 Chinese: PRC (Simplified)
0x0816 1252 Portuguese: Portugal
Radio:
There are 2 different Radios:
Radios that you can flash using HardSPL:
For installing a RADIO ROM you need to use HardSPL on your device: it won't hardreset your device.
Changing the Radio in the ROM
UPDATE: XBmod is working on a CAB to change the Radio in the ROM, thus in the future you will be able to send the CAB and change the Radio.
At present use the instructions below.
To use a different Software Radio you need to change the Part00.bin in the 7004 Data.zip and start the process to 7720 all over again... As for the regular HD2 radio we can continue to flash away
Steps:
Download the radio you want to use
You'll get a part00.bin file
In the V1 or V2 ROM you can find a data.zip file
Replace in data.zip the part00.bin with the one you downloaded
Go through the usual process of installing the ROM
For EU Leo users who want to try 5.51 (without the t) see this post by LittleH79 .
Simple guide to replace the radio:
- Download 7zip from the web and install it.
- Download V2 rom.
- Download my radio attached.
- Extract attached radio to a folder (inside is part00.bin)
- Extract V2 rom to a folder
- Go to the extracted rom folder.
- In there you'll find Data.zip
- Open this folder with 7zip.
- Open the folder where you saved my attached radio (part00.bin)
- Simply drag file part00.bin inside 7zip window
- Wait a few moment and you're done
- Just to be sure, if it went well you'll see that file part00.bin has 2 dates changed
The Radio I’m sure will become a topic in its own right! what you have to remember is that there is no right or wrong Radio, it’s all about how close you are to a tower, Signal strength, country etc etc etc, right now to change the ROM radio you need to flash, hopefully someone can figure out how we can flash it without needing to Flash the ROM, perhaps a CAB.....
RADIO TABLE (need Data from folk for this)
SIM lockedIf you have SIM locked device from your mobile provider, before you upgrade to WP7 you must unlock the device (if you want SIM lock free). unlocking not working under WP7. For unlocking you must have unlock code... in most case, you must buy this code from any trusted GSM unlock site) or contact your carrier and ask them for an unlock code, typically they will give you one.
Thanks to dxdy
SD cards and unlocking them.
Once WP7 formats your SDcard, your computer won't read them since WP7 locked them this is part of the security feature built into WP7.
But if you need to, you can format the cards in certain devices, you should use one of thre following reported methods
Nokia N or E series
Nokia Phone
Nokia Symbian OS phone
PDA like 5250
N95
Canon camera
Nikon Camera
If you don’t have one of the above and rather than buying a new SD card, borrow one from a freind, or even go to a store and ask the store guy, and ask him if its ok that they let you use one to do it.
Custom and Special CAB's:
DEV_STORAGELOCK.cab (this will install the unlock tool for your sd card (providing the possibility of dualboot))
DEV_STORAGELOCK_REMOVE.CAB (as always a second CAB removing the above function "unlock tool" Warning your SDCard will be relocked at reboot resulting is dataloss.)
HTML 5
Is working.
This looks fantastic! I was having problems and just about to give up and go back to my previous rom, but this has given me a few areas where i could have gone wrong!
The installation instructions with the rom were sketch at most, so this is a great addition to yuki and XBmod's brilliant work!
I hope it's ok I post here...
I'm only a bit wary about doing this, because I don't have a serial to activate WP7.
Plus, I'd like to know if it's possible to have Portuguese(Portugal) as the display language, and how to do that...
Also, I got a 4GB, class 4, sd card from Kingston.
How do I know if it is compatible?
Can you help?
Ok, now I believe I could flash that ROM. All other explanations were written mostly for the authors. Thank you very much!!
a011528 said:
Q. I’m on V1 do I need to Start right from the beginning – re-run the whole Process?
A. Yes you do.
Click to expand...
Click to collapse
I went from v1 to v2 without going back to stock rom (6.5) but just flashing v2 on top of v1. Not had a single problem. So, it's up to you...
Edit: Nice tutorial!
RCOO said:
I hope it's ok I post here...
I'm only a bit wary about doing this, because I don't have a serial to activate WP7.
Plus, I'd like to know if it's possible to have Portuguese(Portugal) as the display language, and how to do that...
Also, I got a 4GB, class 4, sd card from Kingston.
How do I know if it is compatible?
Can you help?
Click to expand...
Click to collapse
Its not really okay for you to post a question on the front page, in the development section, but since you have now, i will answer your question, maybe it will add to the guide.
Unfortunatley i do not know about the language, but if you have look around the forums, you will easily find out that its not possible for anyone to say for sure whether your sd card will work, even when a card of the same spec works. So its purely luck. Try and flash Yuki's rooted rom on the developement section of this forum first, to determine whether your card works, then move onto this.
As for the activation code, you will only be asked for this when connecting to the marketplace.
I was able to get mine by phoning up, however some people have been unsuccessfull in doing this now, but its always worth a try. Then you code can be used multiple times, so if you flash over your rom, you can re-enter it again in a clear rom fairly easily, as long as you keep the same XBOX LIVE ID and dont change too often.
only small tip
if you have SIM locked device by mobile provider, before upgrade to WP7 you must unlock device (if you want SIM lock free). unlocking not working under WP7
for unlocking you must have unlock code... in most case, you must buy this code from any trusted GSM unlock site (unlock-now for example... very fast and good support)
stevemilw said:
Its not really okay for you to post a question on the front page, in the development section, but since you have now, i will answer your question, maybe it will add to the guide.
Unfortunatley i do not know about the language, but if you have look around the forums, you will easily find out that its not possible for anyone to say for sure whether your sd card will work, even when a card of the same spec works. So its purely luck. Try and flash Yuki's rooted rom on the developement section of this forum first, to determine whether your card works, then move onto this.
As for the activation code, you will only be asked for this when connecting to the marketplace.
I was able to get mine by phoning up, however some people have been unsuccessfull in doing this now, but its always worth a try. Then you code can be used multiple times, so if you flash over your rom, you can re-enter it again in a clear rom fairly easily, as long as you keep the same XBOX LIVE ID and dont change too often.
Click to expand...
Click to collapse
Thanks =p
Great work!!!!!!
This will be really helpfull for a lot of people
In Yuki's thread I made a (small) post about changing radio before flashing:
http://forum.xda-developers.com/showpost.php?p=17207345&postcount=2394
Maybe you can use some bits of it
LittleH79 said:
Great work!!!!!!
This will be really helpfull for a lot of people
In Yuki's thread I made a (small) post about changing radio before flashing:
http://forum.xda-developers.com/showpost.php?p=17207345&postcount=2394
Maybe you can use some bits of it
Click to expand...
Click to collapse
Lmao. I just added your post and this thread to favorites xD
Be carefull, you have a trouble with your last post:
the numbers are:
10, 11, 12, 1, 12, 13
i stuck at sending the cab to the phone, anyone can help?
http://forum.xda-developers.com/showthread.php?p=17129153&posted=1#post17129153
we need another post to *.cab fix the rom, can you make that please?
thanks
dAV84 said:
we need another post to *.cab fix the rom, can you make that please?
thanks
Click to expand...
Click to collapse
can you explain further?
hengmy said:
i stuck at sending the cab to the phone, anyone can help?
http://forum.xda-developers.com/showthread.php?p=17129153&posted=1#post17129153
Click to expand...
Click to collapse
I replied on the main board
Unfortunatley this guide hasnt worked for me.
During the stage of updating to 7008, on step 8, restarting your phone, the phone re-boots and locks up, i cannot move anything on the phone, and the installation will go no furrther.
Any ideas as to what this could be?
I cannot format my memory card again after applying the magldr services sub options (24mb thing and the other) so its basically dead to the computer, even through USB mass storage mode on MAGLDR.
Any ideas people? i flash 6.5 previous too with 2.15 rom. Left software radios the same, tried english us and uk when setting up phone for first time, neither worked.
Hello all,
Not a great first post, but I have a problem, that I cannot solve myself.
I bought LUMIA 800 from a guy on ebay, really good offer(ofcourse), the phone was in good condition, all functioning. Checked the IMEI - not stollen. After taking it home, I noticed that I cannot log into microsoft live, facebook and twitter, from the add new account menu. It keeps giving me - there is an error, please try again later. However, day after that, the phone gives me a message - this demo phone is going to be reset. After that reboots, with all my data formated and starts installing content, like some demo contacts, messages and etc. Also a promo video is played, while I`m loading it.
So, in short - is there a way to get that phone to function normally? I tried both formats, from the menu and with the 3 buttons, it always starts loading the demo contacts and etc.
Any help will be greatly appreciated!
Pavel
ok, did my homework and searched the forums. I will try with standart debranding method, hope it works.
you can flash it using NCS (Nokia Care Suite). I will upload a handy tool for you. wait a moment....
here you can download the tools: http://www.multiupload.nl/91Y8NK6L7E
greatly appreciated Tim! thank you
Hi,
I also got one of those demophones and I tried Tim's method but When I do Step: 20 and Step: 21 I do not see the newer firmware there.
The line where it should be is plank.
I have downloaded firmware from navifirmplus and place it to that exact place what it is on Tim's document: C:\ProgramData\Nokia\Packages\Products\RM-801 without any subfolders.
But on my PC I had to make that products folder too, there was none when I first time navigate to that folder, I check File -> setting from product support tool for store and there that folder is right but I do not see that newer firmware, so can anyone help?
you must run the applications under Administrative rights. so right click on the NCS and click: "Run as Administrator"
otherwise the program doesn't have access to the c:\programdata\......
most accounts have administrator rights, but if you have UAC (userAccountControll) enabled on your computer than the error that you describe will come.
Hi tim!
I tried with administrative rights, now effect, still do not show "new software version"
Does that Product Code have to be same on downloaded firmware and that it is already on phone? caude in phone I have 059N394 and firmware I downloaded is 059N341
You solved your own problem ;-).
yes that's the issue, make the productcode that you downloaded the same as the productcode of your phone, and it will work.
in NaviFirm there is not a code with "059N394", I would download the firmware that is applicable to my country and color, and most matching with the productcode of the phone.
sorry for my bad english....
Please hit the "Thanks" button if I helped you....
Thanks! ur a MAN!!!
It worked!!
Please have you got someone firmware NOKIA LUMIA 800 RM-801 for Nokia Care Suite ?
Thank you very much for your help.
David
Hi,
I first tried the method below:
Is someone trying to develop a Custom ROM for the Huawei Ascend G600 (U8950D)?
http://forum.xda-developers.com/showthread.php?t=1943003
But the phones are not just different band versions, as mentioned in post 58 of the thread above. The T8950 is not kernal compatible with the U8950D:
http://www.jetdroid.org/forum/viewtopic.php?f=106&t=8383
Indeed, the T8950 is equipped with MTK6517 dual-core processor, the MT6517 and MT6577 are the same, A9 architecture 40nm processor, clock ed speed is 1.0Ghz.
http://defendgun.com/2013/01/22/mobile-customized-huawei-glory-t8950-listed-price-at-261/
I don't pretend to have any knowledge about rooting phones, I just was able to find the correct information on the web. I spend two weeks figuring this out. So I hope I can save somebody else his time with this information.
this is how I did it.
UNLOCKING THE BOOTLOADER
--------------------------------------------------
the bootloader of the T8950 is not locked, so it does not need to be unlocked. Allight, step one done!
INSTALLING THE CMW CUSTOM RECOVERY TOOL
------------------------------------------------------------------------------
The T8950 does indeed not have a fastboot mode. the CWM custom recovery can be installed by flashing the ROM using the Flash tool of Mediatek
tutorial: http://bm-smartphone-reviews.blogspot.com/2012/05/mt6575-flashing-tutorial.htmlthe correct files to use in the tutorial can be found here:
- SP_Flash_Tool_exe_v3.1224.01 --> http://www.mediafire.com/?c8lr368ceaqk7tv
- MediaTek DA USB VCOM drivers --> http://www.mediafire.com/?h0ytkyagj0kf89u
if all went well, you should have a different recovery screen now.
ROOTING
-----------
Tutorial: http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
The fileto be used is:
- RootT8950.zip --> http://www.mediafire.com/?je47wz2ozjr7oth
After the update is finished, reboot . Now, you should see Superuser in your Huawei T8950 app list. You can double check if you have root, using the "got root?" app.-->https://play.google.com/store/apps/details?id=com.island51.gotroot
INSTALLING THE GOOGLE SERVICES
----------------------------------------------------------
Since the the CWM custom recovery tool is installed now and the phone is rooted, it's very simple to add the google services to the phone. I used the GAPPS of Cyanogen. You can find them on many places, e.g.
http://www.needrom.com/mobile/gapps-cyanogen/
choose the right version, most likely your T8950 will have android ICS 4.0.4
istallation is the same as installing the rooting ROM
REFERENCES
----------------------
http://bm-smartphone-reviews.blogspot.com/2012/05/mt6575-flashing-tutorial.html
http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
http://www.aiothudanu.com/2013/01/huawei-t8950-install-cwm-recovery-and.html
http://forum.xda-developers.com/showthread.php?t=1911475
http://www.needrom.com/mobile/gapps-cyanogen/
Regards,
TeTTiweTTi
Hey TeTTiweTTi!
I can not say how glad I am that you wrote this tutorial. It seems that this is actually the only tutorial on how to truly unlock the T8950 (at least for non russian-speakers )
Still, I'd have some questions:
How do you install the VCOM driver? I downloaded it, but I can only find .inf files.. How do you install them?
Did you flash the whole ROM or just a part of it, as shown in the tutorial? And what exactly happens when you flash the ROM? Are you able to boot afterwards? It seems to just install CWM - right?
How do you apply the update RootT8950.zip?
Help would be appreciated a lot, since you seem to be the only one who knows how to properly do it
Oh and btw: did everything work for you after flashing the ROM? Or did you encounter any errors?
Cheers,
amannn
Hi, it was indeed not so easy to collect these bits and pieces together
here an answer to your questions
1.
The .inf files are the drivers. There are two ways to install the drivers. One way is to right click on the .inf file and choose "Install". The other way is to start the process with SP Flash Tool and as soon as you plug in the phone a new device will be detected and you have the choice to install the drivers.
Also, it is very important to make sure that you click "Download" first before you connect the device. Actually there is a trick, below the sp flash tool, you will see something that says "USB". Click "Download" and wait for the "USB" to become "Searching". Once it is "searching" then connect the USB. SP-Flashtool should be able to capture it before it disconnects itself again.
2.
yes, you only flash a part of the ROM, so you don't need to have all the files in the SP Flash Tool. Only the ones mentioned in the tutorial. Your phone will boot normal, nothing will be changed yet. But now you will have the CWM custom recovery when you start up in recovery mode.
3.
the linked tutorial is quite clear. Let me know if you cannot reach the page or you encounter a problem.
Regards,
TeTTiweTTi
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Hey TeTTiweTTi!
Thank you very much again for your detailed explanation!
So i think I've installed CWM recovery successful. Therefore, I'm now working on the rooting part.
The RootT8950.zip file needs to be applied, using the "choose zip from sdcard" option from CWM recovery right? When I choose that option, I encounter the error "E:Can't mount /sdcard/". Also when I'm trying to create a backup, it says "Can't mount backup path.". So it seems that there is a problem with accessing the sdcard. I then tried the "mount /sdcard" option, but it also says "Error mounting /sdcard".
Did you have any problem like that? When my phone is booted up, there is no problem with accessing the sd card... Or is there a option how I can check if the sd card is inserted correctly? I guess it's internal and therefore impossible to even remove it..
Your help would be highly appreciated!
Many thanks in advance and best wishes,
amannn
EDIT: I was now able to upload the update with an external micro sd. Therefore everything works so far - thanks again
Similar phone mtk6517 svp s580
Hi
I have this. svp. Phone with ARMV7 ( see cpuz snapshot
)
It says mkt6517 with A5 cortex
I tried jnstalling all drivers linked here for ADB
but windows xp disqualified em as valid drivers for this hardware
Finally I got android device driver to install on
All 3 devices ( see pic- there are 3 devices
That show up )
I don't think this generic driver is the right one
So rooting this is still not done .does anyone hace luck with this device
Any idea ......? With getting the right driver and root
Procedure
I tried eroot too amongst other rooting s/w's
CPU screenshot
CPU screenshot
sieger007 said:
Finally I got android device driver to install on
All 3 devices ( see pic- there are 3 devices
That show up )
I don't think this generic driver is the right one
So rooting this is still not done .does anyone hace luck with this device
Any idea ......? With getting the right driver and root
Procedure
I tried eroot too amongst other rooting s/w's
Click to expand...
Click to collapse
Hi sieger007,
It can be a little bit tricky to install the drivers, since it are .inf files only. But these are the driver files
http://bm-smartphone-reviews.blogspot.be/2012/05/mt6575-flashing-tutorial.html said:
There are two ways to install the drivers. One way is to right click on the .inf file and choose "Install". The other way is to start the process with SP Flash Tool and as soon as you plug in the phone a new device will be detected and you have the choice to install the drivers.
It is very important to make sure that you click "Download" first before you connect the device. Actually there is a trick, below the sp flash tool, you will see something that says "USB". Click "Download" and wait for the "USB" to become "Searching". Once it is "searching" then connect the USB. SP-Flashtool should be able to capture it before it disconnects itself again.
Click to expand...
Click to collapse
This second way worked just fine for me.
You can find the drivers and tools also here
http://mt65xx-tools.4shared.com/
he password to login is bm-smartphone-reviews.blogspot.com.
But always make sure that you trust the sources of the ROM you download and know that it is meant for your phone. After flashing a wrong preloader, your phone will be completely dead (can't be powered on, it will not charge and won't be detected anymore by the computer) and there is no way to recover it.
In order to root you first need to install a custom recovery. In this case it is CWM.
hope this helps
still stuck in driver hell
thanks for your help . I had a previous Chinese MTK (MT6575 ARM A9 cortex ) phone , whose ADB drivers successfully installed when I installed the SDK .
Now this one is MTK6517 ARM A5 Cortex. and none of the methods ( #1 or #2 ) help, in those drivers being recognized.
By method #1 : Right click install - It maybe just copying the driver file to system folder and then on windows would auto detect it when the device is inserted -assuming there is a match .
Method # 2 : Uses the new h/w found dialogue . Not sure if invoking sp_tool is related anyways in invoking that dialogue . It shows up anyways - soon as you plug in the phone .
I could not get the driver files in with the blogspot password to be recognized . Kept giving me "specified location. does not contain info about your h/w msg"
I have the EXACT same problem with ALL drivers hunted on the net , that say MTK driver. Some files say MTK65xx some say MTK_USB_Driver etc.
the h/w ID's and instance IDs associated with the devices are attached .
USB\VID_1782&Pid_5d04&Rev_0229&MI_01
Now the driver.inf file did have one ray of hope with this mention ..wonder if that'd make it compatible with a modified inf file.
But I am lost about HOW to add the h/w ID info ( format and what specific data to add ) to the inf file -most data is of the form VID_eXXX something in that file ( see below quote )
MT6516 USB VCOM drivers\readme.txt
Code:
3. Customers can customize usb2ser_XXX.inf file.
There is a string in the file:
MTK6218 = "USB Modem Driver"
You can modify it for your product name, for example:
MTK6218 = "MY_PRODUCT Modem Driver"
The other perplexing thing is that there are 3 Devices that show up under XP device manager. I managed to get one of em installed as device "android phone" with driver "android ADB interface" from Google and can possibly manage to get ALL of em installed the same way since those device ID's are close ( the last '1' becomes 2 and 3 respectively ) in this
Code:
USB\VID_1782&Pid_5d04&Rev_0229&MI_01
After pushing all these device ID's as "android ADB interface" - and attempting to root- the android rooting s/w's will NOT work at the identification step , erring out with "ADP device not found "- conclusively indicating that those drivers probably did not work well and I ought to look around for better ones - something I am trying to address by this thread.
Lastly - sp_tool when you start it - it will ask for scatter file. The scatter file out there is for MTK6577 (vs my model 6517 ) . If I choose that file - it gives me a warning - yes it out - and click download - it will then just freeze doing nothing
after some more G-mining ( Google) - i found out that I have to stick my VID in that hardware ID's and create an adb_usb.ini file to get the device recognized. Will update on happened next
sieger007 said:
after some more G-mining ( Google) - i found out that I have to stick my VID in that hardware ID's and create an adb_usb.ini file to get the device recognized. Will update on happened next
Click to expand...
Click to collapse
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
found something !!! I hope this is perm and not "leased"
TeTTiweTTi said:
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
Click to expand...
Click to collapse
TeTTiweTTi said:
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
Click to expand...
Click to collapse
ADB driver issue
> adb_usb.ini needed oXXXX as device ID . Where XXXX is the ID that shows up on Device manager. This is detailed here
http://blog.fh-kaernten.at/wehr/?p=1182
after that there will be 2 yellow marks for the rest of the unknowns in device manager. for this you have to modify the .inf file to include the entire h/w ID strings. I guess that makes just about any driver get along with anyone unknown - so here I am not sure if showing them as the such h/w by changing the driver files - gives them the actual intended functionality or all it does it just makes the device manager look clean without yellow marks. Maybe someone could help expand the talk here
[
Code:
android_winusb.inf
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_01
/*ADDED*/
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_03
So with that - I get 1 ADB interface and 3 devices show up under "com and LPT" - alright that completes the drivers
ROOTING
I found this Chinese rooting program Vroot . I still have'nt figured out what exactly it means but it looks like it DID root that sucker after all. I tested with one app - root checker - got an dialogue in Chinese , asking me whether to give or not and I think I said Y but that app still does not say I have root. Its probably the apps thats at fault because I can get Linked2SD do ALL the stuff it would be doing running as root - .e.g force move programs to SD to free up space etc.
If someone out there can make English out of that and tell me if its mine to keep or leased out ( trial ) - that'd be damn nice !!!
ROMS
- WIP- when I get some more time
the chinese rooting program - now hiring English interpreters
the chinese rooting program - now hiring English interpreters
sieger007 said:
ADB driver issue
> adb_usb.ini needed oXXXX as device ID . Where XXXX is the ID that shows up on Device manager. This is detailed here
http://blog.fh-kaernten.at/wehr/?p=1182
after that there will be 2 yellow marks for the rest of the unknowns in device manager. for this you have to modify the .inf file to include the entire h/w ID strings. I guess that makes just about any driver get along with anyone unknown - so here I am not sure if showing them as the such h/w by changing the driver files - gives them the actual intended functionality or all it does it just makes the device manager look clean without yellow marks. Maybe someone could help expand the talk here
[
Code:
android_winusb.inf
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_01
/*ADDED*/
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_03
So with that - I get 1 ADB interface and 3 devices show up under "com and LPT" - alright that completes the drivers
ROOTING
I found this Chinese rooting program Vroot . I still have'nt figured out what exactly it means but it looks like it DID root that sucker after all. I tested with one app - root checker - got an dialogue in Chinese , asking me whether to give or not and I think I said Y but that app still does not say I have root. Its probably the apps thats at fault because I can get Linked2SD do ALL the stuff it would be doing running as root - .e.g force move programs to SD to free up space etc.
If someone out there can make English out of that and tell me if its mine to keep or leased out ( trial ) - that'd be damn nice !!!
ROMS
- WIP- when I get some more time
Click to expand...
Click to collapse
sieger007 said:
the chinese rooting program - now hiring English interpreters
Click to expand...
Click to collapse
Post some screenshots of the text you want translated and I will ask the help of one of my Chinese colleagues.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
some screenshots of the text you want translated
here goes ..thank you . Combined several screens together in '4 lets '
TeTTiweTTi said:
Post some screenshots of the text you want translated and I will ask the help of one of my Chinese colleagues.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
sieger007 said:
here goes ..thank you . Combined several screens together in '4 lets '
Click to expand...
Click to collapse
ROM Basic Information Huawei T8950 Emotion UI 1.6 official pure version of the card brush pack
Author: Hay.
Size: 398MB
Android Version: 4.1.2
UI type: official factory style
Suitable models: Huawei T8950
Release date: 2013-07-31
MD5 code: F7A21630317EE4239DC145E75FF8A276
ROM presentation
1, based on the official code base package and Qualcomm made to upgrade to 4.1.2
2, emui upgrade to 1.6
3, repair legendary SMS unlit issue
4, full root privileges
5, caused during an upgrade wifi loss problem to fix
6, clean up some pit length useless underlying file
7, adjust the signal and the network connection speed
8 streamlining TTS voice database file
9, usb debugging is enabled by default
10 to adjust the overall Desktop Note: Upgrading from 4.0 to 4.1 need to upgrade Bottom bag bottom package
download address: http://pan.baidu.com/share/link?shareid=805743044&uk=137718883
recover before upgrade to upgrade the official recovery Brush back REC official and third-party tools
brush download address: HTTP :/ / pan.baidu.com / share / link? shareid = 807162397 & uk = 137718883
1.6 EMUI ROM Download: http://t.cn/zQWgp1r
3G not accessible
Hi again,
so I've been struggling with another issue.
Somehow my T8950 isn't capable of connecting to the 3G network of my carrier. When I search for networks, only the 2G networks are being found.
Does anybody have a clue why that is and how to solve that problem? My carrier is from Austria and is called "tele.ring" which is operated by T-Mobile.
I'd really appreciate your help, since 2G is reaaally slow for data connections
EDIT: I just tried allowing my phone only to connect to 3G networks by using the Network app from Philipp Mangelow (which shows the same menu as if you dial *#*#4636#*#* as i just found out). This results into no 3G networks being found at all.. I thought maybe the problem occurs because I'm always connected in roaming mode. As I bought the phone in China, it seems to believe that i need to be in roaming mode to connect to my local carrier. However, I have a local SIM-card, so this is somewhat weird..
EDIT 2: So after some googling I've found out that China has the TD-SCDMA radio interface for 3G (at least China Mobile, and that's from where I've bought the phone), but in europe it's W-CDMA.. Remains the question how to change that (if possible at all)..
EDIT 3: So I've wrote an email to Huawei about the issue, and that's the reply:
Sorry that T8950 doesn’t support the W-CDMA mode.
Below please kindly check the frequence band of T8950 for your reference.
• GSM/EDGE：900/1800/1900MHz
• TD-SCDMA：A frequency（2010-2025MHz）/F frequency（1880-1920MHz)
So that means that there is nothing i can do about it?
Thanks and all the best,
amannn
amannn said:
Hi again,
so I've been struggling with another issue.
Somehow my T8950 isn't capable of connecting to the 3G network of my carrier. When I search for networks, only the 2G networks are being found.
Does anybody have a clue why that is and how to solve that problem? My carrier is from Austria and is called "tele.ring" which is operated by T-Mobile.
I'd really appreciate your help, since 2G is reaaally slow for data connections
EDIT: I just tried allowing my phone only to connect to 3G networks by using the Network app from Philipp Mangelow (which shows the same menu as if you dial *#*#4636#*#* as i just found out). This results into no 3G networks being found at all.. I thought maybe the problem occurs because I'm always connected in roaming mode. As I bought the phone in China, it seems to believe that i need to be in roaming mode to connect to my local carrier. However, I have a local SIM-card, so this is somewhat weird..
EDIT 2: So after some googling I've found out that China has the TD-SCDMA radio interface for 3G (at least China Mobile, and that's from where I've bought the phone), but in europe it's W-CDMA.. Remains the question how to change that (if possible at all)..
EDIT 3: So I've wrote an email to Huawei about the issue, and that's the reply:
Sorry that T8950 doesn’t support the W-CDMA mode.
Below please kindly check the frequence band of T8950 for your reference.
• GSM/EDGE：900/1800/1900MHz
• TD-SCDMA：A frequency（2010-2025MHz）/F frequency（1880-1920MHz)
So that means that there is nothing i can do about it?
Thanks and all the best,
amannn
Click to expand...
Click to collapse
No, unfortunatly not. this is not a software setting, but a different hardware chip. my t8950 also does not support 3G in Belgium
TeTTiweTTi said:
No, unfortunatly not. this is not a software setting, but a different hardware chip. my t8950 also does not support 3G in Belgium
Click to expand...
Click to collapse
Mmmmh, ok – that's what i thought too.
Thank you very much anyway for your response TeTTiweTTi!
HI all,
I am looking for the O2 UK firmware, either Amber or earlier.
Does anyone have a link for it anywhere that i can download and flash to my phone?
Thanks
Adam
P.S. Reason i ask is because i am currently on the euro1_dev firmware but wanting to get rid of the phone so would rather put it back on original O2 UK firmware
you need firmware with product code 059S333: RM-821 VAR GB O2 SL BLACK
current version is 3047.0000.1326.2004
you can try this app to check did this offer you right firmware
http://jkorondy.com/NokiaLumia920/Nokia_Software_Updater_For_Retail_3.0.8.exe
if not, you must use navifirm+ v2.6 (but must pay donation to author to download firmware)
or use NCS
After Nokia Suite installs, copy and replace the usergroupsconfiguration.cfg file to Crogram Files (x86)NokiaNokia Care SuiteProduct Support Tool For Store 5.0 if you’re running a 64-bit version of Windows. Or Crogram FilesNokiaNokia Care SuiteProduct Support Tool For Store 5.0 if on 32-bit.
1. Open Nokia Suite. And select ‘Product Support Tool For Store 5.0′
2. When prompted, select ‘CareSuite External’ then hit ‘Sign-in’ button.
3. From the Menu, select Tools, then ‘Firmware Download’
4. Now enter the product code of your device, hit ‘Check Online’ button, to check the latest firmware version of your product code.
5. Then ‘tick’ ‘Optional Content Files and ‘Download’ to save your firmware.
6. Wait a few minutes for your files to download
7. You may now manually flash your Nokia device with the firmware you just downloaded.
- Your firmware should be stored in the C:\ProgramData\Nokia\Packages\Products folder of your hard drive.