(NOTE: You need to backup the files before you install a diferent rom)
This will help you keep the 2G/3G settings (WCDMA) for you country after debranding or flashing another ROM.
Im from Portugal and I bought an orange UK flipout from ebay. Once I got it the first thing I did was debrand it and installed the non-motoblur version found in the debranding guide. I noticed that I did not have 2G network, since when I changed it to 2G I would loose all network.
After reasearching in a lot of forums I found a solution:
- Before changing the original rom (if you live in the country where you bought the phone) backup these files from /etc/motorola/bp_nvm_default:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
- After you install a new rom (if you notice that your network is working wierd) just replace the files in the new rom for the ones you backed up previously (Dont forget to check the files permissions after) and reboot.
In case you get stuck in a boot loop you might have forgot to copy one of the files or forgot to change the files permissions. Solution is to flash again (for me at least, maybe you can change it using adb);
[What I did was:
- I installed the rom with the frequencies I wished;
- backed up the files above;
- Installed the non-motoblur rom;
- Replaced the files with the back up ;
- Checked the files permission;
- Reboot.
Voila, I have 2G and 3G working perfectly]
(You have to have ROOT and I used root explorer)
This will allow everyone to install the non-motoblur version in their phones withought loosing their coutrys network frequecies.
Since the new update from motorola aparently corrects reception, maybe someone can share these files after they aplyed the update? In case you do, please specify where your from and if you know the frequencies your countries network works on, e.g. Portugal, 850, 900, 2100.
Sharing the original ones might help someone too, so please go ahead. I'll share the ones from the Italian rom (according to the debrand guide have the most frequencie support, once I get home)
Hope this helps !
(NOTE: You need to backup the files before you install a diferent rom)
[Just in case your wondering, I got this from this guide:
http://www.simply-android.com/discu...-3g-after-flashing-the-wrong-firmware/#Item_5 ]
Hmm.. Interesting.
But I was wondering..
/etc seems to be a symlink to /system/etc , wouldn't it be better to edit the files in /system/etc to make it more clear? (the results are pretty much the same, though)
You probably right but I dont have that kind of knowledge...
If you think its better I can change the location in the post?
Bartleby said:
You probably right but I dont have that kind of knowledge...
If you think its better I can change the location in the post?
Click to expand...
Click to collapse
Nah.. It seems to me that /etc is just a symbolic link to /system/etc
while the rootfs (/) is just a ram image.
Editing whatever from /etc is just the same as editing stuff from /system/etc
i have problem with rom for italy and uk with motoblur. when i installed is i dont have range 2G, only on deblur rom it work properly. do that method works with my situation? on chinese rom i dont have this problem
Yes, that was my issue too
ATT files
can someone please post these files for the att flipout, my phone is stuck in a boot loop and I fear the only way to fix it would be to flash one of the roms, in which case I would really like to have 2g
How you check "file permissions"?
I'm using this on Linda File Manager.
UPDATE: Thanks anyways ROOT EXPLORER Solved the permission stuff.
I'm trying this on a Telus Charm that was flashed with a T-Mobile ROM. Everything works OK apart from the phone (calling) functions.
I do have another Telus Charm working properly to get the files.
But every time I put the file on the folder the phone restarts and I have to do a factory reset; I modified permissions so the look just as the phnes in the original folder (on my Charm rw-r--r--) but still my phone still don't get signal. The only file I can't find on my working Telus Charm is generic_pds_init so I can't replace it on the other phone.
Best Regards.
Best Regards.
MGA2009 said:
How you check "file permissions"?
I'm using this on Linda File Manager.
UPDATE: Thanks anyways ROOT EXPLORER Solved the permission stuff.
I'm trying this on a Telus Charm that was flashed with a T-Mobile ROM. Everything works OK apart from the phone (calling) functions.
I do have another Telus Charm working properly to get the files.
But every time I put the file on the folder the phone restarts and I have to do a factory reset; I modified permissions so the look just as the phnes in the original folder (on my Charm rw-r--r--) but still my phone still don't get signal. The only file I can't find on my working Telus Charm is generic_pds_init so I can't replace it on the other phone.
Best Regards.
Best Regards.
Click to expand...
Click to collapse
When I first tryed this I thought that some files were not needed so i would get stuck in a bootloop. If that file does not exist try to find one that might be the same (similar name?) That file must be important and related to the others. Worst case scenario maybe try copying the entyre folder?
A quick warning - using Motorola Charm (not flipout) it seems that once you flash the T-Mobile ROM no other ROM will work (it updates the bootloader with a locked one). So avoid T-Mobile unless you it's you only solution.
It might be the same point-of-no-return issue on Flipout.
dvfk said:
A quick warning - using Motorola Charm (not flipout) it seems that once you flash the T-Mobile ROM no other ROM will work (it updates the bootloader with a locked one). So avoid T-Mobile unless you it's you only solution.
It might be the same point-of-no-return issue on Flipout.
Click to expand...
Click to collapse
This Telus Charm was semi bricked because I flashed the "de blured" SBF and I could only get to bootloader.
After I flashed T-Mobile SBF I've a semi working phone, as everything works apart from the phone functions.
This is only for 3G? I'm not getting neither 2G nor 3G.
Am I missing any file/folder?
Best Regards.
Hi Guys!
Sadly I saw this post too late.
I flashed my wifes Flipout with the deblurred ROM from the Orange debranding guide.
Now we also have got the missing 2G problem.
I´d really appreciate it if is were somebody out there who could upload the correct baseband files for Germany.
Thanks in advance,
Moe
Update:
Found the baseband config files here: http://dext3r.komodin.org/ (bottom of page)
I´ll also append them to this post for your convenience.
German Baseband files:
Bartleby said:
(Dont forget to check the files permissions after)
Click to expand...
Click to collapse
Which permissions should be given?
In doubt is it okay to set permissions to everyone?
chmod xyz filename. What is xyz?
moritz.narnhammer said:
Hi Guys!
Update:
Found the baseband config files here: http://dext3r.komodin.org/ (bottom of page)
I´ll also append them to this post for your convenience.
Click to expand...
Click to collapse
Hi, I'm from Germany and can confirm that these files not working for german Motorola Flipout devices on O2 network with deblured US version. Use the uk files mentioned in ITA/FR/etc. Thread instead!
I have the same problem. I have a samsung gt 5830i phone. Where do I download the file? So I can have a 2g signal.
Related
I'm sorry about this new thread, but I couldn't manage to find the right answer for me.
I flashed to JPC and my product code has changed. I don't have any problems with network/sim lock, but I wonder If I can revert to my original product code.
My SGS is rooted and I have this program Root Explorer, but when I get into the EFS folder there is nothing, no files at all. Can somedoby please tell me where's the problem? By the way this code *#272..... doesn't work also
How can i see changed product code?,i am using JPC too.
posted about this this morning!
Don't know if this will help you... but I posted this this morning on another thread:
http://forum.xda-developers.com/showthread.php?p=7997364#post7997364
Thanks, but my EFS folder is empty
This is not a problem as long as I can install another new firmware without any problems. And I think that Samsung MUST create an option to select your region and this fix your product code. And I'm sure that they already know about their fault with this stupid KOR :|
celeronix said:
Thanks, but my EFS folder is empty
This is not a problem as long as I can install another new firmware without any problems. And I think that Samsung MUST create an option to select your region and this fix your product code. And I'm sure that they already know about their fault with this stupid KOR :|
Click to expand...
Click to collapse
If root explorer isnt working for you, try EStrongs File Explorer (enable Root option in settings), its free so no need to buy anything. I dont have root explorer so cant help you with that.
Thanks, this Estrongs Explorer works. I have managed to find my .nv_data.bak files and they are dated 07/02/10
The question now is how can I fix my product code without reflashing my firmware to another version. This JPC is good for me at this point
I have rooted the boot image from my XOOM, this is a UK 3G XOOM, DO NOT USE if you are NOT 3G, or use at your own risk, attached.
Before you proceed you will need to unlock your bootloader, note this will erase all of your data, you have been warned!
UPDATE for 3.2
Use the following to get root on your 3.2 updated euro xoom. Please note, the modules here from the earlier boot image are most probably not functional anymore. I will try get an updated set. For now, here are the instructions, the new boot image is attached to this post.
Get the boot_3.2_insecure.zip from this post which also contains an su binary i just compiled.
Code:
adb reboot bootloader
fastboot oem unlock
Follow the on screen instructions!
Extract the files into you current directory, then reboot into fastboot mode and do:
Code:
fastboot flash boot boot.img
fastboot reboot
This will get you a rooted bootloader but you still aren't rooted yet, get a prompt or terminal open in the folder where the root_files are from the attached zip you will need the su file.
Make sure you have a computer with adb set up then from the computer perform the following commands with the xoom connected:
Code:
adb remount
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
NEXT: Go to the Market and install "Superuser" by ChainsDD and you will probably want to install busybox too.
Congratulations on rooting your euro 3G XOOM all by yourself, and remember "one click" is for noobs who like to brick their devices (like me) don't do it.
OLD Modules(tun/cifs/etc) 3.0.1:
Code:
I have attached an archive containing cifs.ko, tun.ko, nls_utf8.ko, option.ko
and usb_wwan.ko with correct version magic. I did not compile them,
and I can not provide others (unless I can find them).
How to use:
Copy the modules to "/system/lib/modules", reboot.
If you don't know how to do that, you probably shouldn't be using them.
Disclaimer: I take no responsibility if either this boot image, the tutorial, or the files attached murders you violently, in fact, don't even use them.
alias_neo said:
Guys, I have been through this process, STOP using the US root instructions and images, they don't work on the european 3G XOOMs.
I have boot and recovery images that I need someone with a little experience to contact me about testing before I can release them to anyone else as working.
If a mod could sticky this please to stop people bricking their euro XOOMs until I can get the images tested and get a dump of the recovery partition!
Click to expand...
Click to collapse
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
If there's been an OTA update for the UMTS Xoom already, and you have a recovery-from-boot.p binary patch and the boot image, you can make the recovery image by using applypatch.
I don't have a device yet, sadly, so I can't test yet.
ydaraishy said:
As an aside, it's pretty damn obvious from the Wi-Fi/CDMA malarkey that flashing the wrong boot image for the wrong model is bad, especially without stock images.
Did you actually rip the stock boot image? (How'd you manage it?) Can you just post it somewhere? It should be a simple matter to make a root boot image from it.
I don't have a device yet, sadly.
Click to expand...
Click to collapse
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.
alias_neo said:
Well, dumping the stock boot was easy enough once recovery partition was sacrificed, you just boot off of that, as for the boot.img I have a rooted boot image that I created, I'll post it here so hopefully some of you can unbrick (as long as you didn't overwrite system too).
I won't post system until it's been tested because that wasn't a simple flash to restore.
Click to expand...
Click to collapse
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.
ydaraishy said:
Yeah, but what did you flash to recovery? The kernels from source, last time I looked, seemed like they didn't have mods for the UMTS model yet.
Click to expand...
Click to collapse
I flashed a stock 3G boot image that I rooted myself.
alias_neo said:
I flashed a stock 3G boot image that I rooted myself.
Click to expand...
Click to collapse
Ah, got you. Thanks for the info.
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk
alias_neo said:
I already included a working rooted boot image in the first post...
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Oops, you're right; I thought you said you had the stock boot image, which is why I got confused.
Xoom Brazilian 3g and wifi
ydaraishy said:
The attached boot img MIGHT work for root (unpacked, set ro.secure to 0, repacked).
(ed. If this works, then the guinea pig who flashes it can easily rip a stock recovery from this, if it hasn't been clobbered already.)
Click to expand...
Click to collapse
In brazilian 3g gsm and wifi works fine tks
rickjardim said:
In brazilian 3g gsm and wifi works fine tks
Click to expand...
Click to collapse
May can you give me a your framework-res.apk file?
Thanks so much
Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?
mlokane said:
Well, it seems to work - tried on my UK 3G model. The problem is that my 3G no longer works - I try to activate it and it just sits there on "searching for service" and "activation can take a few minutes" with nothing happening.
Wifi etc. works BTW. I may have accidentally overwritten something as I managed to semi-brick it before realising that the US images wouldn't work.
Anyone have any ideas?
Click to expand...
Click to collapse
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.
alias_neo said:
You have done what I did. There is no such thing as activation on a UK xoom 3g. You have overwritten the system partition with the US one and you will need the stock UK System image. I have one but I had trouble getting it to work and I wont be posting it until it has been tested. You are welcome to be the ginea pig, and this is the only way you'll get your xoom back to UK and get 3g wworking again, believe mem iv been there.
Macbots drool as I XOOM through the Galaxy to my hearts Desire on the back of a Droid.
Click to expand...
Click to collapse
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!
mlokane said:
Ah - that makes sense. Well the US system image I have works fine except for the 3G access, so if I try and flash this uk system image onto my xoom and it doesn't work can I still flash the old US one back again easily? As it's a new xoom and I haven't installed anything on it I'm fine with being a guinea pig as long as it won't completely brick!
Click to expand...
Click to collapse
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.
alias_neo said:
Yep, I was in the same position, the US version works fine but no 3G cause it's built for a CDMA device. The stock system image I flashed would not boot so I had to relock and then unlock again the device to fix the permissions for it to boot again.
If your confident you can relock and unlock again the device after flashing this image PM me and i'll get the system image to you to test, I won't be around to help though if it goes wrong cause I'm at work so make sure you're confident first.
Click to expand...
Click to collapse
PMed now - we can update this thread if it works...
i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.
aefelix said:
i'm trying to do the opposite, I'm looking for euro gsm images, to flash into my verizon 3g/wifi version. The goal is to verify if, once flashed, the us xoom can work with european 3g networks ( for sure it has a world radio chip, same used in the verizone ip4).
If anyone has got a dump pm please.
Thanks in advance.
M.
Click to expand...
Click to collapse
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.
alias_neo said:
I doubt it will work, I tried Verizon on my UK 3G and there was no radio detected. They may have the complete hardware available but the baseband probably takes care of access the correct hardware.
Click to expand...
Click to collapse
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )
aefelix said:
That make sense, but a complete euro 3g system dump could do the job...I'm investigating on harware differencies on the euro/usa versions, if they are the same , ther's no apparent reason that could not allow me to push a euro version rom on the verizon one (with a good dose of luck and tech skills )
Click to expand...
Click to collapse
I flashed a complete Verizon dump on mine and everything worked except the radio, so I imagine it would be the same the other way around. By all means though give it a go, bear in mind they are different models and so most likely have hardware differences (no LTE upgrade in europe).
Anyone know how we can change this text? XML location?
This rom gives you the option to personalize the carrier text AOKP V9
Sent from my Galaxy Nexus using Tapatalk
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Tag, looking through the framework for this and other tweaks are on my lst for this weekend.
nachtschicht said:
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Click to expand...
Click to collapse
Anybody know the numbers for USA and Verizon?
BeADroid said:
Anybody know the numbers for USA and Verizon?
Click to expand...
Click to collapse
I'd like to know this too.
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
http://forums.androidcentral.com/ve...d-removed-verizonwireless-lock-drop-down.html
here is a guide
SpinDisc said:
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
Click to expand...
Click to collapse
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
I just realized that you can start Market Enabler and it will tell you the correctly number
nachtschicht said:
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
Click to expand...
Click to collapse
Thanks for the info! I'm still a newb. My family & friends think I'm a genius (rooted their D.Incredible, D2, Eris, etc). But none of it's possible without the knowledge on XDA. Still learning, and hoping to learn more. Thanks for the info on how to change the banner info, too!
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
mrZoSo said:
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
Click to expand...
Click to collapse
I'll update my write up over the weekend as it is for the OG, but look for
HTML:
EriInfo......Verizon Wireless...64...65.
So in the Gnex it is immediately before 64
Can toss a link to market enabler
Sent from my Galaxy Nexus using xda premium
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Nevermind that was a different one I had here, my bad.
I'm going to pull the one off the phone now.
mrZoSo said:
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Click to expand...
Click to collapse
I am still running a stock 4.0.2 based ROM. When I look at some of the ASOP 4.0.3 that I am playing with, one has google, one has verizon. Changing whatever comes before ...64...65 will edit both the lock screen and the tag at the bottom of the notification bar.
CM9 based ROMs seemed to have moved this value to a different file. It would take some digging to determine where they move it to.
DHO said:
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
Click to expand...
Click to collapse
Thanks for linking to your great write-up! I followed it (for the most part), and it works...until my screen shuts off (from no activity), and then it goes back to Verizon Wireless. I've tried it two different ways (I'm currently on Deoxed Stock ICL53F with APM & Softkeys):
1. I edited the eri.xml, repackaged it in the APM .zip (since I found that installing other framework-res.apk's broke the APM). Re-flashed the APM .zip, and the new banner "Galaxy Nexus" stuck until the screen shut off. Back on, and it's back to VW
2. I just repackaged the framework-res.apk, and took it out of the APM.zip. Placed it in the "sdcard" section, copied in Root Explorer, and pasted into /system/framework/. After a reboot, same this as #1.
So, how do I get it to stick? Does it have anything to do with the ROM I'm on? Or with APM? I feel like it should work, but something's just not sticking...ugh...
SpinDisc, I'm not sure. I think it may be a function of APM. I have been trying to replicate that bug and I cannot. What launcher are you using?
I cannot replicate it running a ROM compiled from Pete's 4.0.2 AOSP source and NOVA launcher. I will further explore this over the weekend.
This weekend I plan on testing/modding a few different 4.0.3 ROMs, if I find any nuances I will let you know.
If you're rooted, you can use Root Tools.
https://market.android.com/details?...51bGwsMSwxLDEsImNvbS5qcnVtbXkucm9vdHRvb2xzIl0.
Steps to Flash Taiwanese or European ROM on Mainland Chinese T328W
Disclaimer: I m not claiming any credit for the tools. The tools are developed by other smart guys (some based in mainland China), and all the credit goes to them. I am merely collating and translating information here for the benefit of t328w users outside China.
And flashing ROM is a risky process as always. Use it at your own risk and have fun!
This is a general approach, and should work with ROMs or Official RUU from different regional replease or different version. In particular, this method should install the 100% stock version of Taiwanese or European ROM to your phone, without running into the CID unmatched problem. It does not change or upgrade Radio in the process.
REQUIREMENT:
unlocked bootloader
custom recovery
STEPS:
1) Download the pseudo flashing tool: HTC_T328w_1.56.1402.6_BackToOriginal_modified.rar
The download link: http://d-h.st/Hq2
This is a pseudo flashing tool that pretends to behave like the official flashing tool, and thus enable any unlocked phone to flash back a modified version (Slim down and rooted) of the OTA 1.56.1402.6 stock ROM. Don’t worry too much about this ROM as it is only needed as an intermediary process.
2) Unzip the file in a convenient location (e.g. desktop), it should contain several files including a ROM.ZIP.
3) Reboot the phone into “BOOTLOADER” by restarting (or switch on) the phone and pressing “POWER” and “VOLUME DOWN” at the same time. Then go into “FASTBOOT”.
4) Connect the t328w to PC via USB cable. The phone should now display “FASTBOOT USB”
5) Open the file HTC pseudo flashing tool.exe from step 2. Half the interface is in Chinese but don’t worry! It’s straightforward enough. The functions are as follow:
B – Enter Bootloader;
S – go into Flashing Mode
F – Flash the pseudo official ROM
Q – Reboot from Flashing Mode
I – developer’s information
what we need to use are S and F.
6) Press S and ENTER, then Y and ENTER to confirm. This will bring your phone into Flashing Mode. The screen will be displaying a big HTC logo in the middle of it and nothing else.
7) Press F and ENTER, then Y and ENTER to confirm. This will start the pseudo flashing process to flash the content of the ROM.ZIP into your phone.
8) When its done, reboot. The phone will be flashed with the pseudo official ROM.
NOW, THE INTERESTING STEPS:
The tool is created in such a way that you can flash a great variety of different custom ROM as if they are official ROM files. All that needed to be done is change what’s inside of the ROM.ZIP file.
9) Unzip two files from official RUU Taiwan version (PL11IMG_PRIMO_DS_ICS_40A_hTC_Asia_TW_1.59.709.3_Radio_1.05.34D.29_20.21.30.23U_release_264969_signed): BOOT_SIGNED.IMG and SYSTEM.IMG
see here for the Taiwan RUU url:
http://forum.xda-developers.com/showthread.php?t=1714317
10) Open the ROM.ZIP using WINRAR as it is, do not extract or unpack.
11) Select the BOOT.IMG and SYSTEM.IMG, and click “Delete” on WINRAR.
12) Click “ADD” on WINRAR, and add the two files (“BOOT_SIGNED.IMG “ and “SYSTEM.IMG”) from the official Taiwanese ROM RUU from step 9. (DO NOT RENAME THE BOOT FILES! Leave it as BOOT_SIGNED.IMG). Save it as ROM.ZIP
13) Replace the ROM.ZIP from step 2 with the ROM.ZIP from step 12.
14) Repeat step 3 to step 8.
Alternatively, I have created a ROM_Taiwan.ZIP that was based off step 9-12.
The download link: http://d-h.st/v8B
You can download this file and go straight to step 13.
JOB DONE!
RADIO:
This method works on all radio version. There are mainly two radios version at the moment for the Chinese mainland t328w:
the original t328w is on 1.04.34D.11_20.11.30.11U
the OTA upgraded t328w is on 1.06.34D.05_20.22.30.23U
The 1.06.34D.05_20.22.30.23U is a different radio compared with the Taiwanese or European release. But it is a great bug fixing radio and massively improves the performance of t328w. I am using it in U.K. with no signal problem at all with this radio.
This method will NOT update Radio as the phone itself is S-ON. I am not aware of S-OFF method for this phone at this stage.
To update radio, you need to restore phone to stock Chinese status, do an OTA, and repeat the steps above.
ROOT:
Depends on if you have the OTA or not, the root methods can be different. Several root method that worked on the initial stock version will not work after OTA. See other thread for root methods.
wow, thank you so much, I'm gonna try this when I get home. I've been going crazy with Chinese version (I live in Vietnam) and unable to use Google play! Hopefully it'd work! Thanks again!
Edit: I re-locked my t328w, is it possible to do this with re-locked status?
awesome
cezent said:
Steps to Flash Taiwanese or European ROM on Mainland Chinese T328W
Disclaimer: I m not claiming any credit for the tools. The tools are developed by other smart guys (some based in mainland China), and all the credit goes to them. I am merely collating and translating information here for the benefit of t328w users outside China.
And flashing ROM is a risky process as always. Use it at your own risk and have fun!
....
.
Click to expand...
Click to collapse
I have followed the steps from gfan and mobile01 and flashed the Taiwanese version ROM yesterday. I have tried but failed to translation the method into English. Your traslation is faultless.
bug report after flash the Taiwanese version ROM: Wandoujia (the most popular andriod devices manage software for PC in China) recongnises my T328w as HTC desire (G7) .
File not found! It is still uploading?
nam207 said:
File not found! It is still uploading?
Click to expand...
Click to collapse
Uploaded to a different source. Should work now.
nam207 said:
wow, thank you so much, I'm gonna try this when I get home. I've been going crazy with Chinese version (I live in Vietnam) and unable to use Google play! Hopefully it'd work! Thanks again!
Edit: I re-locked my t328w, is it possible to do this with re-locked status?
Click to expand...
Click to collapse
this tool requires unlocked bootloader, so u need to unlock again. should be a simple process.
koyfee said:
I have followed the steps from gfan and mobile01 and flashed the Taiwanese version ROM yesterday. I have tried but failed to translation the method into English. Your traslation is faultless.
bug report after flash the Taiwanese version ROM: Wandoujia (the most popular andriod devices manage software for PC in China) recongnises my T328w as HTC desire (G7) .
Click to expand...
Click to collapse
unfortunatley there is no real quick solution to this one. the problem is with Wandoujia, not with the ROM.
The ROM will flash your phone into 100% stock Taiwanese or European version. This means in About - Phone identity - phone Model number will be converted into "HTC Desire V" instead of t328w.
Unless wandoujia data base is updated to include Desire V, it won't really identify the phone correctly.
Maybe I should give it a try,Thanks.
did anyone have PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed ZIP file?
plz upload it or post link to download it
thanks!
cayowl said:
did anyone have PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed ZIP file?
plz upload it or post link to download it
thanks!
Click to expand...
Click to collapse
Google is your friend: (remove spaces i'am a new member and no links allowed)
ht tps: // docs.google.com / uc?id=0B5l6 hlK799AFMFdma0xKRXNrYlU&export=download
edit : oh its an exe file although i think it is what you want to have
Run the .exe until a dialog appears. Leave the program (dont exit) and go to your %temp% folder. There you will find 2 subfolders with a hash ID (look at created date/time to find these). Inside 1 of these folders you will find rom.zip. In this file look for system.img and boot_signed.img
I'm currently trying this procedure to flash the Europe version. I will post the result.
Just installed Europe version. Great it seems to work!
Google play is installed by default.
There seem to be 2 settings for language. I think (although i'am quite new to android) 1 language is for the system language and the other language is for the phone dictionary for messaging.
The system languages provide only a lot of different eastern europe languages and different variants. I (being Dutch) selected Russian English. For the dictionary setting I could see all major European languages.
The phone keypad still has some eastern europe characters. Not that anoying. You can also see 'normal' abc characters.
[deleted, update: after a while I was able to use web interface of google play]. The google play app lets me install all the apps i couldnt install before with the chinese rom.
I'm not sure if the radio has been updated but now I have 2 full bars which I i'am sure wasn't like that with the chinese rom.
So far I'am verry happy!
Still have to test some things that didn't work before.
Edit : cheered too fast. Mobile reception has increased. 3G connection won't go further then GPRS at my house ... which was HSDPA most often. Hopefully because of the bad weather...
Still I do have internet on most of my apps. However browsing doesn't work and randomly apps stop to have an internet connection. However facebook app always works. Anyone any clues why? This was before the ROM update and also after same behavoir.
jp1980 said:
I'm not sure if the radio has been updated but now I have 2 full bars which I i'am sure wasn't like that with the chinese rom.
So far I'am verry happy!
Still have to test some things that didn't work before.
Edit : cheered too fast. Mobile reception has increased. 3G connection won't go further then GPRS at my house ... which was HSDPA most often. Hopefully because of the bad weather...
Still I do have internet on most of my apps. However browsing doesn't work and randomly apps stop to have an internet connection. However facebook app always works. Anyone any clues why? This was before the ROM update and also after same behavoir.
Click to expand...
Click to collapse
I think the issue is with ur radio.
Check ur radio version, it sounds like u have the 1st release radio 1.04.34D.11_20.11.30.11U
That radio version has known issue including unstable signal and dropping lines randomly, thats why HTC issued an OTA for this.the OTA upgraded t328w is on 1.06.34D.05_20.22.30.23U.
The European and Taiwanese Desire V has radio 1.05.34D.25_20.20.30.22U and 1.05.34D.29_20.21.30.23U. I m not sure if the 1.06 radio is definitely newer as it could simply be a different regional release, but I would assume the 1.06 is the latest ROM for the t328w variant.
The Desire V is Radio S-On, which means only stock phone with locked bootloader can change radio version. As mentioned in my original post, flashing ROM won't update the radio.
The radio included in t328w s OTA is much better with significant stability improvement, and it worked very well on mine with the Taiwanese ROM. I would recommend restore the phone back to stock, OTA, then reFlash ur European ROM.
What u need to do is the following:
1) Do a backup in CWM recovery
2) relock bootloader
3) get the RUU ( the .exe file) for the first release of the phone, boot ur phone into fastboot, run RUU to restore ur phone to factory states
4) OTA
5) unlock bootloader again
6) flash modified recovery
7) wipe and restore from the backup in step 1. (or reFlash the European or Taiwanese rom from beginning )
I would also recommend root ur phone before starting this process. The OTA locked some partition on the phone, which makes rooting afterwards slightly tricky (ADB won't work any more), but there are still easy way to do it.
Anyway, I ll write another guide for the radio upgrade when I ve got the time.
WORKED
I have a chinese version. I was unable to do anything. Bloat chinese software slowed my phone, and I can't use Google play.
Followed exactly the steps you gave and my t328w has become Desire V. Who cares? As long as everything works, and they are (google play, wifi, 3g, dual sim)
So thank you very much for Russion version (Europe?)
Can u give me another link plz????
jp1980 said:
Google is your friend: (remove spaces i'am a new member and no links allowed)
ht tps: // docs.google.com / uc?id=0B5l6 hlK799AFMFdma0xKRXNrYlU&export=download
edit : oh its an exe file although i think it is what you want to have
Run the .exe until a dialog appears. Leave the program (dont exit) and go to your %temp% folder. There you will find 2 subfolders with a hash ID (look at created date/time to find these). Inside 1 of these folders you will find rom.zip. In this file look for system.img and boot_signed.img
I'm currently trying this procedure to flash the Europe version. I will post the result.
Click to expand...
Click to collapse
PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05. 34D.25_20.20.30.22U_release_263747_signed ZIP NEEEEEEEDDDDD
ht tps: // docs.google.com / uc?id=0B5l6 hlK799AFMFdma0xKRXNrYlU&export=download
NOT WORKING
Nofear99 said:
PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05. 34D.25_20.20.30.22U_release_263747_signed ZIP NEEEEEEEDDDDD
ht tps: // docs.google.com / uc?id=0B5l6 hlK799AFMFdma0xKRXNrYlU&export=download
NOT WORKING
Click to expand...
Click to collapse
Try this (still you could have found this easally with google)
http: // hotfile.com/dl/158782968/55e3eb6/RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed.exe. html
generic rom?
I found a "Generic ROM" from a Chinese forum http :// bbs.zhangku. com/thread-102863-1-1.html.
http ://down2.zhangku.com/htcrom2/Desire_V/PL11IMG_PRIMO_DS_ICS_40A_HTC_Generic_1.37.997.1_Radio_1.04.34D.12_20.11.30.11U_test_256967.zip
I downloaded but failed to flash into my Desire V.
Any recommend?
kingcedz said:
I think the issue is with ur radio.
Check ur radio version, it sounds like u have the 1st release radio 1.04.34D.11_20.11.30.11U
That radio version has known issue including unstable signal and dropping lines randomly, thats why HTC issued an OTA for this.the OTA upgraded t328w is on 1.06.34D.05_20.22.30.23U.
The European and Taiwanese Desire V has radio 1.05.34D.25_20.20.30.22U and 1.05.34D.29_20.21.30.23U. I m not sure if the 1.06 radio is definitely newer as it could simply be a different regional release, but I would assume the 1.06 is the latest ROM for the t328w variant.
The Desire V is Radio S-On, which means only stock phone with locked bootloader can change radio version. As mentioned in my original post, flashing ROM won't update the radio.
The radio included in t328w s OTA is much better with significant stability improvement, and it worked very well on mine with the Taiwanese ROM. I would recommend restore the phone back to stock, OTA, then reFlash ur European ROM.
What u need to do is the following:
1) Do a backup in CWM recovery
2) relock bootloader
3) get the RUU ( the .exe file) for the first release of the phone, boot ur phone into fastboot, run RUU to restore ur phone to factory states
4) OTA
5) unlock bootloader again
6) flash modified recovery
7) wipe and restore from the backup in step 1. (or reFlash the European or Taiwanese rom from beginning )
I would also recommend root ur phone before starting this process. The OTA locked some partition on the phone, which makes rooting afterwards slightly tricky (ADB won't work any more), but there are still easy way to do it.
Anyway, I ll write another guide for the radio upgrade when I ve got the time.
Click to expand...
Click to collapse
Hi Kingdez, many thanks. I think it might be a radio problem. My radio is still 1.04.
I do have the europe RUU which contains radio 1.05. I can't find 1.06 anywhere.
I would love to update the radio.
I will be fine with the procedure except for step 4 and step 6. When you have time could you explain those in detail? Many many thanks!
koyfee said:
I found a "Generic ROM" from a Chinese forum http :// bbs.zhangku. com/thread-102863-1-1.html.
http ://down2.zhangku.com/htcrom2/Desire_V/PL11IMG_PRIMO_DS_ICS_40A_HTC_Generic_1.37.997.1_Radio_1.04.34D.12_20.11.30.11U_test_256967.zip
I downloaded but failed to flash into my Desire V.
Any recommend?
Click to expand...
Click to collapse
Not seen this ROM before, interesting as it is generic without regional codes ( HTCCN or Asia..etc). Have u tried taking out the system and boot.img from this file, and replaces them with my what's in my original post?
jp1980 said:
Hi Kingdez, many thanks. I think it might be a radio problem. My radio is still 1.04.
I do have the europe RUU which contains radio 1.05. I can't find 1.06 anywhere.
I would love to update the radio.
I will be fine with the procedure except for step 4 and step 6. When you have time could you explain those in detail? Many many thanks!
Click to expand...
Click to collapse
Once u factory reset with an RUU with a locked bootloader, OTA should ve straight forward. Check for update and accept.
The next 2-3 steps goes back to unlock the phone all over again.
I ll try to put sth together on radio upgrades
kingcedz said:
Not seen this ROM before, interesting as it is generic without regional codes ( HTCCN or Asia..etc). Have u tried taking out the system and boot.img from this file, and replaces them with my what's in my original post?
Click to expand...
Click to collapse
Not yet. I think it would work well.
I have unpackaged the system image file and I found some appliactions (Renren, Sina music, Sina weibo, etc.), customized for Chinese users . And NO mobile operators customized apps were found. NO google service apps stocked too.
So I think the name "Generic" is as distingushed from operators customized. It's still for China.
OK guys, i think that I found the solution that will be PERMANENT fix of the problem with the LTE network on our G3 [ I own D855 but i think that this will be equal to all other models ]
So.... i spent hours ... many hours to find this so i hope that you will appreciate my work and maybe buy me a coffee if this help to you too.
1. I had problem, when my phone connects to LTE network and WiFi at the same time my network coverage disappeared.
2. After few days my network coverage started to disappeare with no logic... every few minutes - i have network and in a minute i dont have network and that was a proccess that never stopped.
What i tried :
1. I tried 30b kdz
2. I tried 30b via TWRP
3. I tried all different modems that i found with all this rom variations
4. I tried to go back to stock lollipop kdz
5. I may be tried something more but i wont to think more for that annoying problem any more so... that is enought
So here is what i found:
1. Simply use a Prop Build editor [ i used ES File Explorer to edit Build.prop ] to go into the build.prop and change the "telephony.lteOnCdmaDevice” value from 0 to 1. There are two lines on in the G3 build prop. Make sure both have the value of 1. Then save. Then reboot.
This fix will basically have to be done everytime you/me flash a new rom or update but it works!
First make a backup of your build.prop file !!!!
2. Deleting the file LTEconfig.apk works sometimes. The file is located in the folder: / System /app
Just copy it to other location and delete the file and restart your phone. I said sometime because with some combination of roms and kernels and radios it helped me, but not in every variation. You have to try yourself.
This fix will basically have to be done everytime you/me flash a new rom or update but it works!
First make a backup of your LTEconfig.apk file !!!!
3. Next thing that i found is that editing the build.prop with this values have a massive effect too :
ro.telephony.default_network=11 or 13.
ro.ril.def.preferred.network=11 or 13.
ro.build.target_country=AU or COM or to your country code.
This fix will basically have to be done everytime you/me flash a new rom or update but it works!
First make a backup of your build.prop file !!!!
4. Try to Disable Fast Dormancy. You can do this by simply open the hidden menu in your G3. This can be done by simply dial *#546368#*855# on 6.0 D855 or 3845#*855# on 5.0 D855 [you will have to find the codes for the other variations of G3]
so hidden menu > Modem Protocol > PDP Setting > Set LG Fast Dormancy > disable
This fix will basically have to be done everytime you/me flash a new rom or update but it works!
So... i have no problems anymore with this network issues
If someone find something that can be done more permanent than this, i will be glad to hear and understand but for now this is OK i am sure because we can use our phones as phones.
some people (including me ) have data icon missing in stock kdz and lose sim options too after rooting :/ are they any solutions for us ? I searched for 5 days :/
iliashoshi said:
some people (including me ) have data icon missing in stock kdz and lose sim options too after rooting :/ are they any solutions for us ? I searched for 5 days :/
Click to expand...
Click to collapse
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/ try to download stock kdz or tot .... some older version like 10a for example. Flash it with flashtool 2014 or lgup but first in twrp advanced wipe and wipe everything... then when you start your phone "from beggining" try to OTA update to lollipop.... i hope that this will normalize your problem. I am not sure... you have to try it. You should restore backup from when you were stock ot efs partitions just in case before flashing new kdz...
Write if it helped because there are many people out there having strange problems with network connection.
GL.
I was on kdz 6.0 kingroot + twrp ==> factory reset/wipe everything/format data via twrp===> flash the kk tot file
now I'm doing Ota updates
iliashoshi said:
I was on kdz 6.0 kingroot + twrp ==> factory reset/wipe everything/format data via twrp===> flash the kk tot file
now I'm doing Ota updates
Click to expand...
Click to collapse
this means that now you dont have problems with data?
mccloud90 said:
this means that now you dont have problemIs with data?
Click to expand...
Click to collapse
I did all ota updates from kk to 21A then flashe the kdz
DATA ICON STILL MISSING in V30b :/ omg I did all ota for nothing (( it's a problem in the v30B
iliashoshi said:
I did all ota updates from kk to 21A then flashe the kdz
DATA ICON STILL MISSING in V30b :/ omg I did all ota for nothing (( it's a problem in the v30B
Click to expand...
Click to collapse
I think you download KDZ from here. I also same your case. I have 2 30B KDZ one is i downlaod from here http://devtester.ro/projects/lg-firmwares/ the other is i download UK 30b. when i flash first one it ok when i flesh the second one is cant see my connect number they are gone. I think this link KDZ will help you. (http://devtester.ro/projects/lg-firmwares/)
good luck for u .
sorry for my english
iliashoshi said:
I did all ota updates from kk to 21A then flashe the kdz
DATA ICON STILL MISSING in V30b :/ omg I did all ota for nothing (( it's a problem in the v30B
Click to expand...
Click to collapse
Ok, its not lost time in fact... this means that you dont have hardware problem its software related and mostly in 30b version that you have installed.
In fact my last rom flash was with file downloaded from here http://devtester.ro/projects/lg-firmwares/ as thurasisyein said.
I dont know why.. for no reason... i just coughn`t find 30b 16gb kdz with fast speed of download here in the forum and i tried.
Thanks for this thread!
I had no 4g/lte connection after i flashed MM KDZ, and no matter what rom i installed it didn't work, after i tried these fixes i found an old backup to restore, after that straight to 4g.
Now installed another rom via twrp and 4g sticks. For me i think it was a regional issue. (on 855) Denmark.
mccloud90 said:
Ok, its not lost time in fact... this means that you dont have hardware problem its software related and mostly in 30b version that you have installed.
In fact my last rom flash was with file downloaded from here http://devtester.ro/projects/lg-firmwares/ as thurasisyein said.
I dont know why.. for no reason... i just coughn`t find 30b 16gb kdz with fast speed of download here in the forum and i tried.
Click to expand...
Click to collapse
I downloaded the kdz file from here http://devtester.ro/projects/lg-firmwares/ and also from lgmobile
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
thurasisyein said:
I think you download KDZ from here. I also same your case. I have 2 30B KDZ one is i downlaod from here http://devtester.ro/projects/lg-firmwares/ the other is i download UK 30b. when i flash first one it ok when i flesh the second one is cant see my connect number they are gone. I think this link KDZ will help you. (http://devtester.ro/projects/lg-firmwares/)
good luck for u .
sorry for my english
Click to expand...
Click to collapse
I downloaded the kdz file from here http://devtester.ro/projects/lg-firmwares/ and also from lgmobile
iliashoshi said:
I downloaded the kdz file from here http://devtester.ro/projects/lg-firmwares/ and also from lgmobile
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
I downloaded the kdz file from here http://devtester.ro/projects/lg-firmwares/ and also from lgmobile
Click to expand...
Click to collapse
OK, try to insert your sim card into another android device. Remove your sim card while your G3 is into airplane mode... insert it into another android device and wait to connect to 4g... when this happened put it back to your G3 and airplane mode off and see if this will make things better.
Hey guys, I have an AT&T branded LG G3, unlocked, under a mexican network provider (TELCEL), every band is supported by the phone and I'm using their SIM. I'm currently using Fulmics 4.2 Rom, but even on stock rom, since I received the unit, whenever the LTE signal was too low, or I made a call, the phone would drop the signal and switch to 2G. The problem is, once this happens, the phone remains on 2G and won't change automatically to LTE. I have to turn it off and on for it to recover the LTE signal. Will this fix the issue? Or do you think I have a faulty unit? Thanks!
4g icon missing
Please Help My LG d855 On Stock 6.0 4g icon missing but data is still working fine , but in another rom like AOSP , 4g icon is appear and fine , Just in Stock Rom my 4g icon is missing , But Data is fine , Just a icon , Anyone Help , Thanks
This is what I was looking for all month, thanks OP. I use a h2o sim for mt vs985 and every time I booted up my phone would complain about a non-verizon SIM. Also, I would only get 3G.
Changing the target carrier to ATT and default band to 4 in these settings resolved this after a reboot. The error is gone and I now have 4G. Thanks for telling me about this!
@mccloud90, thanks for this thread. My problem is slightly different (it it can be called "problem" at all).
Using an app called LTE Discovery, I can see that modem always chooses LTE Band 3, which is more power-hungry than other ones. For example, in my country, LTE (4G) Band 20 is much more power-efficient, but, for any reason, modem never chooses it. I can force the selection of Band 20 thru the hidden menu, but this comes with other annoyances, like the fact that I cannot do or receive telephone calls. In the other hand, using Band 20, I feel much less power consumption.
So the question is: are there any way or workaound to tell the modem/sytem TO PREFER one LTE Band?. Maybe some build.prop configuration or a .sh script?
Thanks and, yes, I know this is not an easy question =). I just wanted to know your opinion.
After installing Marshmallow using the KDZ firmware, LTE was not working with a Cricket SIM card accessing the AT&T Network. I then made a phone call and received an automated text from Cricket to provision my phone and this fixed the LTE data connection. The SIM card method posted by Varna above may also work to generate a provisioning request from the carrier which could resolve some connection issues.