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.
Related
Hi guys girls sorry i took so long to get this guide up had to find a few things first well this is a guide if you want to debrand your phone from orange to original firmware simfree. This will also remove the boot logo and the motionblur crap this guide can also be used if you have damaged your device and cannot get it to boot or damaged firmware shall we.
STEP 1 Download usb drivers here below
http://developer.motorola.com/docstools/USB_Drivers/Handset_USB_Driver/?pubid=987654
STEP 2 Download the debranded Firmware here (note you can also use the uk one with motionblur its your choice for debranded use the RUTEM_U3_01.14.2 Central Europe
http://and-developers.com/sbf:ruth#bootloaders
STEP 3 Download RDSLite Latest is v4.5.3 here below
http://www.motorolafans.com/forums/a1200-applications/13457-rsdlite-download-here.html
STEP 4 Install the USB Drivers and the RDSLite program and reboot PC
STEP 5 Extract the firmware file you downloaded a while ago to c:\Program files\Motorola\RSDLite place the folder you extracted there.
STEP 6 Start the RSDite program now where it says filename press the select area and find the downloaded firmware in c:\Program files\Motorola\RSDLite and select the (sbf) file some details will apear on the right hand side.
STEP 7 Now power down your phone and press the up button on the dpad and press the power button for 4 seconds and release the power button only you should see a bootmenu displayed reading the boot vershion and a simple battrey check etc.Now plug in your usb cable it should start loading usb driver wait for it to finish and your ready you should see where it says (port type) your usb connected in RDS Lite this means your ready to flash.
STEP 8 Press the start button on the RDS Lite and just relax while your device gets flashed,debranded etc. you will see a progress status on the right hand side wait till it reaches 100% but please do not disconect it will reboot the phone automaticly and restart the phone.And just wait untill android comes up and fully running untill you disconnect it should read (PLEASE START PHONE MANUALY) on RDS Lite when this shows it is safe to unplug.
STEP 9 Hopefully you now have a debranded phone and or unbricked your phone if it all went wrong for you please read carfully word by word and try the procedure again thankyou and enjoy.
Wow! Thank you!
I haven't tried this yet, but I'd really like to get rid of the moroblur, since currently it is only taking up space.
Does it mean that maybe in the not too distant future we might have custom roms? That's really cool!
awesome to know, I'm currently thinking of getting this phone and the only thing really holding me back is the motoblur on it.
DownTheCross said:
awesome to know, I'm currently thinking of getting this phone and the only thing really holding me back is the motoblur on it.
Click to expand...
Click to collapse
Well yes it does get rid of the motion blur and also the horrible orange logo is replaced by a android one and no orange branding anywhere its the official europe firmware. For those of you that want motionblur but debrand then simply just use the other uk with motionblur rom simple hope this guide help people thats what i am here for enjoy.Oh and its as easy as 123
who developed this roms ?
will it work on other country flipouts ?
matheusoc said:
who developed this roms ?
will it work on other country flipouts ?
Click to expand...
Click to collapse
They are all official motorola roms singned and only flash uk phone with the uk rom or europe rom uk rom is debranded motionblur rom and europe rom is debranded no motionblur rom.
but what is the diferecens betwen phones from other countrys? the frequency ? or the radio is separately from the rom ?
motorola relased the debranded no motoblur rom ?
matheusoc said:
but what is the diferecens betwen phones from other countrys? the frequency ? or the radio is separately from the rom ?
motorola relased the debranded no motoblur rom ?
Click to expand...
Click to collapse
Bands are diferent and launguage.
i'm used to htc win mobile, the rom is totaly separated from the band (radio)
So anyone actually tried this guide if you did and it worked please post your comments.
I have flash the to China rom an it works well on flipout which i bought it in uk.
Anyone can down the UK rom yet? I can't download the rom in that website.
RSD lite update to 4.6 now.
u.115.com/file/f391489d24 (chinese)
I flashed yesterday my flipout which was locked from orange.
The phone is now withouy motoblur and orange Brand but it still sim locked.
The phone is much faster and the guide is very easy to do it.
Thanks a lot
Thanx, worked for me quite easy ;-)
I have just one problem, my german keyboard layout (with ä, ö, ü usw.) is gone. any idea, how i can get the layout back?
jyfans110 said:
I have flash the to China rom an it works well on flipout which i bought it in uk.
Anyone can down the UK rom yet? I can't download the rom in that website.
RSD lite update to 4.6 now.
u.115.com/file/f391489d24 (chinese)
Click to expand...
Click to collapse
Try now with my debranding links the uk rom is now working in the downloads area.
German ROM
Anybody know where i can find the german original rom?
a friend of mine would make a fix for the keyboard layout.
Are there any de-branded images for the Motorola Charm MB502? From what I understand, hardware-wise it's almost identical to the Flipout.
Chahk said:
Are there any de-branded images for the Motorola Charm MB502? From what I understand, hardware-wise it's almost identical to the Flipout.
Click to expand...
Click to collapse
http://modmymobile.com/forums/579-motorola-charm/
probly get some here soon
Noob inside
Hi there,
just bought the flipout (mainly because of his formfactor) and looking forward to have fun making the most of it. But, because I'm a noob, I have questions
Is your guide specific to Orange operator (mine is Bouygues - french one)?
What do you mean by "original firmware simfree"? That's motorola's implementation?
Last but most important question : does my questions make sense?
Kisses to all, receiving my flipout tomorrow
I flashed the UK rom as stated here and it bricked my flipout. I got 3 of them from AT&T for a penny each because of a 3 hour special. I had one to play around and i bricked it. Fresh install of windows 7, fresh downloads and fresh installs. No funny hardware or RAID configurations and nothing but new updates and essential software installed.
RSD went through the process and everything finished with an OK and PASS. When phone rebooted, it said "Critical Error" and thats it. it then reboots few more times and goes into Recovery Mode. I flashed it again using the Chinese w/ Moto Blur rom and the same thing. I figured by this point its either needing an actual US Rom or it's really done for. I downloaded the bootloader and flashed that with no problems. same error and same recovery screen. tried flashing the chinese rom again and same error on reboot. Perhaps the phone was just a bad phone and already was going to have problems. I've rooted/flashed about 50 android phones and never ran into one that got bricked. Just thought I'd post this up for others..
pcnerd said:
I flashed the UK rom as stated here and it bricked my flipout. I got 3 of them from AT&T for a penny each because of a 3 hour special. I had one to play around and i bricked it. Fresh install of windows 7, fresh downloads and fresh installs. No funny hardware or RAID configurations and nothing but new updates and essential software installed.
RSD went through the process and everything finished with an OK and PASS. When phone rebooted, it said "Critical Error" and thats it. it then reboots few more times and goes into Recovery Mode. I flashed it again using the Chinese w/ Moto Blur rom and the same thing. I figured by this point its either needing an actual US Rom or it's really done for. I downloaded the bootloader and flashed that with no problems. same error and same recovery screen. tried flashing the chinese rom again and same error on reboot. Perhaps the phone was just a bad phone and already was going to have problems. I've rooted/flashed about 50 android phones and never ran into one that got bricked. Just thought I'd post this up for others..
Click to expand...
Click to collapse
Probly cause of it being a us phone they work on a different band so thats probly the problem i would say you need the rom for your region this was a debranding guide for uk orange rom as stated anything else is not guarenteed.
Dear guys,
I've been trying to get my LGE975 international device to run on E97520a-EUR-XX, but I had no success on flashing. My device was running on E97510h-232-10, yesterday I updated to E97520a-232-10. If I flash back the E97510H_00.kdz via KDZ Updater in 3GQCT, CS_Emergency, but it says that my sw version is E97510h-232-10... My apps and settings are gone for some times, but my background image...
I think, that the "232-10" part is referring to an MCC-MNC code. It is saying that the referred carrier is the Austrian H3G. I checked the kdz file size, and it is matching with the referred download link on the following site http://lg-phone-firmware.com/index.php?id_mod=20
What I really want is that make a full, clear flashing procedure to get the original E97510h-EUR-XX, and then update to E97520a-EUR-XX via the official LG support tool.
What lg firmware (kdz or zip) should I use, and
what is the proper method (software, and setting) to flash the file?
Thank you for your reply,
YS, Mate Palocska
You should use E97510H.kdz. I doubt it would work with the kdz updater, there is a better kdz flasher you can use. Flashing the E97520a.kdz will be exactly the same as updating via the support tool, so I'd recommend just flashing the 20a kdz.
Is that makink a full clear, deep software change? For me, it seems like that only the characters stated with underline "_" in the SW version "E975___-232-10" are changing.
Not clearing my apps, even my background image stays the same
Should I make a hard reset before flashing? Or should I install a CWM and format the entrie /system partition?
itsdacj said:
You should use E97510H.kdz. I doubt it would work with the kdz updater, there is a better kdz flasher you can use. Flashing the E97520a.kdz will be exactly the same as updating via the support tool, so I'd recommend just flashing the 20a kdz.
Click to expand...
Click to collapse
Is that makink a full clear, deep software change? For me, it seems like that only the characters stated with underline "_" in the SW version "E975___-232-10" are changing.
Not clearing my apps, even my background image stays the same
Should I make a hard reset before flashing? Or should I install a CWM and format the entrie /system partition?
I'm a little confused here, if you flash a kdz it restores your phone to a factory fresh-like software state.
itsdacj said:
I'm a little confused here, if you flash a kdz it restores your phone to a factory fresh-like software state.
Click to expand...
Click to collapse
I'm gonna try out a french or some different kdz's to see if the last 2 tag changes. If so, I am using the wrong kdz.
I'm gonna report soon what happened
thanks for your cooperate
No problem, any time.
itsdacj said:
No problem, any time.
Click to expand...
Click to collapse
So I tried to hard reset, and flash - SW version stayed [...]_232-10
Rooted, installed FreeGee, and flashed TWRP:
made a full wipe, including all caches, and system partition - no OS to boot.
put into download mode and flashed the kdz, same result
So it seems like that I'm using the wrong KDZ to install. (E97510H_00.kdz - 1 026 643 KB)
I really need the exact link to the KDZ to E97510H-EUR-XX
palomatE said:
So I tried to hard reset, and flash - SW version stayed [...]_232-10
Rooted, installed FreeGee, and flashed TWRP:
made a full wipe, including all caches, and system partition - no OS to boot.
put into download mode and flashed the kdz, same result
So it seems like that I'm using the wrong KDZ to install. (E97510H_00.kdz - 1 026 643 KB)
I really need the exact link to the KDZ to E97510H-EUR-XX
Click to expand...
Click to collapse
I have found the link to E97510D which is a little outdated yes but you can do a software update once you're installed. Here's the link http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238386573210987654321/E97510D_00.kdz
itsdacj said:
I have found the link to E97510D which is a little outdated yes but you can do a software update once you're installed. Here's the link http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW238386573210987654321/E97510D_00.kdz
Click to expand...
Click to collapse
Thanks for the link.
It seems like that my SW version is changing well 10H, 20A, 10D. But my version postfix "232-10" stays the same. As I wrote previously, is it possible, that the postfix number is referring to a specific carrier's mcc-mnc? If so, is it possible, that my bootloader somehow locked to that carrier, and no matter what eur-xx version is being installed, the sw version postfix "232-10" is every time stays the same?
palomatE said:
Thanks for the link.
It seems like that my SW version is changing well 10H, 20A, 10D. But my version postfix "232-10" stays the same. As I wrote previously, is it possible, that the postfix number is referring to a specific carrier's mcc-mnc? If so, is it possible, that my bootloader somehow locked to that carrier, and no matter what eur-xx version is being installed, the sw version postfix "232-10" is every time stays the same?
Click to expand...
Click to collapse
Have the same "problem' to 466-92 and I'm on Artmod that is v20A euro-xx based, flashed befor the euro KDZ and nothing, the same numbers.
I think is the flash method used, because I used the simple method that works with my windows 8.1.
I dont understand whats wrong with having 232-10 as the sw postfix. Seems fine to me.
itsdacj said:
I dont understand whats wrong with having 232-10 as the sw postfix. Seems fine to me.
Click to expand...
Click to collapse
Well, the 232-10 version is not containing any information about my carrier (21601). Therefore when I'm on 3G, there are a lot of wakelocks keeping my device awake (like 1hr awake vs 12min screen time). After some research, it seems liket that this is because my carrier does not provide fast dormacy, and my device is not receiving any confirmations so the 3g modem wont close the connection after the data transmit completed. That is caught in the huge amounts of wakelock "msm_hsic_host", and the com.android.internal.telephony.ACTION_CHECK_NETSTAT alarm.
I tried to modify telephony.db / dcm_settings table, but there is no record for 21601, just for 21630 - which is an another carrier here). I modified the row to 21601 and turned fastdormancy to 0. The result is that there are still a lot of wakelocks, but from another activities. This wakelock-killing chain leaded to the point, where I had to disable a lot of google service that I find useful and innovative, and I'm getting tired of this.
I also tried to flash a custom kernel, but with the stock firmware, I found it impossible
I hope I can fin a solution soon
Not sure about European OGs and carrier specifics. In the UK the only OGs are unlocked E975s.
for me i locked in gsm mode, any thing i flash it just keep in gsm, i dont know what to do now, restore to carrier stock and its the same , some one what can i do?
syverman said:
for me i locked in gsm mode, any thing i flash it just keep in gsm, i dont know what to do now, restore to carrier stock and its the same , some one what can i do?
Click to expand...
Click to collapse
maybe it is because somehow flashed an other country's modem, and that modem is trying to use a different frequency for 3G/4G/LTE, than your carrier does. so your phone cannot access the network throught that bad freq.
flash the corresponding modem from here http://drive.google.com/folderview?id=0B3AKIYS66ogAOUVOa2VjVjl1Uk0, and you might be getting correct 3G or LTE
I've already tested and is not a problem with the modem, it is a problem with m9kefs1 file, which contains the information of the Radio, i can get signal, but only gsm, that is why i need to know if anyone can give me a copy of that file, ideally someone from South America, because that way I can replace it with the copy that i have of my efs folder that i made with freegee.
For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.
manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.
Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.
manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.
Hi All,
Currently got no radio signal on my EE HTC 10 due to flashing an incorrect rom. I lost my original backup - amateur.
Have spent a serious amount of time flashing various RUU, ROMS, radio.imgs, firmwares, even with @Kratos90 's patient assistance i'm stuck at square one.
If you have an EE HTC 10 - I'd really appreciate if you could let me know which RADIO/Baseband you are using, along with the OS and possibly ROM you are
using so i can try and give that combination a go.
Example: [email protected]_76.02F / 1.90.401.5
Trying really hard to get this fixed and not sure of the best avenue so hoping this may help.
Many thanks in advance.
Did you perhaps flash SuperSU through TWRP, or use a non-specific for the HTC 10 SuperSU file?
I just read online that doing so can alter the encryption flag and thus break phone signal. (https://www.andromods.com/fix-troubleshoot/rooted-htc-10-no-signal-lost-radio-issues.html)
If so, I am not too sure of what can be done, except maybe flashing the specific SuperSU?
killerojrc said:
Did you perhaps flash SuperSU through TWRP, or use a non-specific for the HTC 10 SuperSU file?
I just read online that doing so can alter the encryption flag and thus break phone signal. (https://www.andromods.com/fix-troubleshoot/rooted-htc-10-no-signal-lost-radio-issues.html)
If so, I am not too sure of what can be done, except maybe flashing the specific SuperSU?
Click to expand...
Click to collapse
Thanks for your suggestion, I have only ever flashed SuperSU once, when i first rooted the phone back in May. So I just did it again, I just tried the steps jcase provides here https://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
3) Using adb, in twrp run - adb shell "echo KEEPFORCEENCRYPT=true>>/data/.supersu"
4) flash latest supersu from http://forum.xda-developers.com/apps...v2-05-t2868133
used - SR2-SuperSU-v2.79-SR2-20170103215521.zip
No Success unforunately - perhaps this SuperSU is not good for the current firmware i've got on there - have reverted back to 1.21.401 TWRP Backup for EVE__001 ( My carrier) but nothing is working.
Hopefully something will work! Welcome to any suggestions!
Thanks.
Is this a specific ee branded phone ? Is your device s off ?
Edit
I See you are s off. Which version of twrp you using ? this may be relevant
Currently 3.0.2-6pme but also had 3.0.3-unofficial-pme on there.
RUU should work if you're using the correct one for your device . Has this phone now been de-branded ?
I would try to format all data in twrp 3.0.3 then Ruu again . Leave root until you're back to square one
I've flashed various RUU and they all go fine but still no radio. I think i have broken encryption or something. Would format data in twrp fix that? I'm away from my pc and phone as am at work for now but will try when I'm back
Read twrp xda thread faq . Check you have the right ruu for your phone ( which I assume is non branded )
You should be good to sort this out, aside from hardware failure but it does sound as if encryption somewhere along your way has caused this
Hello.
Tried Ubuntu Touch on my device - it was working excellent (for linux). Decided to try Pixel Expirience ROM, but on a step of flashing stock global ROM I found that IMEIs are lost. Blame myself for not making backup and probably pressing "format all" somewhere, but I have again installed Ubuntu Touch and it did have IMEIs (both) and they match numbers on a sticker. Why does manufacturer's firmware does not "see" IMEIs and why Ubuntu Touch does?
Flash ENG ROM, than flash stock or custom rom.
ENG ROM has IMEI's right, official ROM (fastboot images, oldest available on android 9 from different regions) does not.
ENG ROM looks cool but can't understand anything in mandarin
Maybe I am doing something wrong? Should I try recovery (not fastboot) images after ENG ROM?
avi9526 said:
ENG ROM has IMEI's right, official ROM (fastboot images, oldest available on android 9 from different regions) does not.
ENG ROM looks cool but can't understand anything in mandarin
Maybe I am doing something wrong? Should I try recovery (not fastboot) images after ENG ROM?
Click to expand...
Click to collapse
If you want to find out reason, maybe you will need to wait lots of time. Or maybe you just use new temporary IMEI fix module, and just let it go
Phone was turned off for a week
Using ENGinnering ROM (thanks dzli) I get into Engineering menu using *#*#3646633#*#*
Tried to use AT+EGMR command with same IMEI1 (ENG ROM does see IMEIs correctly) but it failed with error 100.
Decided to fix my WiFi MAC being weird sometimes by setting it to correct one but with last digit changed (+0x01 to see if it works)
Flashed old global official firmware that was not showing IMEIs previously even after ENG ROM (firmware is the oldest that I have found on some weird site that gives links to miui dirrect downloads). Also I have removed anti_rollback check and lock command from flashing script (how my phone is not bricked? guess I am lucky with that)
Suddenly IMEI are correct and everything is working, I don't know which of this steps fixed my issue (probably WiFi MAC).
Anyway. I don't know if my phone is clean (there is non-zero chance I flashed some backdoored image somewhere before). Probably should
Kirasu2080 said:
just let it go
Click to expand...
Click to collapse
:sad: