[Q] Request for HTC Desire V T328w China Unicom ROM ver 1.56.1402 - Desire General

Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.

why don't you try to use the taiwan ROM, it comes with gapps

bigjimmy546 said:
why don't you try to use the taiwan ROM, it comes with gapps
Click to expand...
Click to collapse
it doesnt look like the taiwan ROM is flashable on mainland chinese version of t328w because of CID difference.

That's exactly the point!
I am trying to flash a Taiwan version of the ROM. But becouse of this SID difference, I'm unable to do it.
Any good soul knows how to do it? Bypass, change or fix this SID difference issue?
Best regards,

you need to flash a china version, then replace the rom and boot file with the taiwan rom

SokRatha said:
Does anyone have ROM version 1.56.1402 of HTC Desire V T328w China Unicom, please share. I have this version install on my device (HBOOT already updated to 1.14.0002).
My current rom is error by missing notification bar when I try to instaff gapps_201204xx to the rom, and bacause I failed to make backup before flash, now I want to revet it back to original rom.
I have try to flash the previous leaks rom 1.35.xxxx, but have no luck by both using RUU or PL111IMG.zip. (even I have done reverted recovery back to stock and relock).
Please kindly help me.
Click to expand...
Click to collapse
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.

cezent said:
what u need to do is the following:
1) *skip this step if your phone is still locked* if you have unlock your bootloader, you need to relock it using the same tool that unlocked the bootloader
2) download the RUU version of the original ROM. RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.35.1402.1_Radio_1.04.34D.11_20.11.30.11U_release_256137_signed.exe
address is here:
http://dl.dbank.com/c0ys4u58d7#
3) go into fastboot mode, and execute the RUU file.
4) follow the steps and your phone should be back to original factory states.
the thing to make sure: your bootloader needs to be locked to flash RUU.
Click to expand...
Click to collapse
This instruction I have follow many time already, but no luck.
I guest this only work when our device not yet receive 1.56.xxx OTA update. When we receive such this OTA update, our bootloader has been updated to 1.14.0002 which is newer then the 1 in the ROM you suggested to me. Finally, the update is failed with a report "HBOOT is older, update failed".
Anyway, really thanks for your great time for suggesting. And till now I have found solution on this issue, is that you could use the, what they called mini-RUU of China ROM (it's also same version suggested above, without HBOOT, and some other part of image file). Using flash zip file method in recovery mode, it work and you need to update software after complete flashing.

bigjimmy546 said:
you need to flash a china version, then replace the rom and boot file with the taiwan rom
Click to expand...
Click to collapse
Could you clearly explain what to do?

SokRatha said:
My current rom is error by missing notification bar
Click to expand...
Click to collapse
this is because old Kernel is used. I've got the same problem when played with roms on my device.
Try to unpack boot_signed.img from rom.zip of original RUU and flash it via fastboot
fastboot flash boot boot_signed.img
This should help.

Related

RUU Marvel S HTC Europe 2.26.401.3 Radio 47.23e.35.3038H 7.57.39.10M release 261695

RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
http://www.filefactory.com/file/7c4y4xrx25w3
MD5: 02f5c589d6d2bb0cc8678c7b76f2951b
Source: http://forum.xda-developers.com/showthread.php?t=1335368 (Football)
....and just after I finally managed to get the ota installed
Hi,
i have S-ON, bootloader unlocked, root, 2.13.401.3
after this update 2.26.401.3 stay still bootloader unlocked?
EDIT: maybe i need S-OFF, not possibly update my mobile...
you need to relock the bl in order to install any ruu.
i had a hard time updating my phone to 2.26
if you take a look at the first thread for this update, the ota update, there are details for how to update to this version and still keep bl-nlocked and easily root
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
Can anyone send me this file not via filefactory? There are no free slots in there at all
I relock bl and try new RUU 2.26, but problem with flashing. Can you pls describe steps by steps how can is possibly update from 2.13 to 2.26 ? I'm S-ON
I have Rom with 2.26 but I want update radio too....
Sent from my HTC Wildfire S A510e using xda premium
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
What's different in this new update 2.26. ?
Hi guys
I'm trying to download this new ruu for 2 days now from "filefactory" an still: "no free slots"! Ca anyone help me to download this new ruu from other sites?
Thank's in advance!
my current software version is 2.14.401.2, what is the difference if i update to 2.26.401.3? Does it gives any improvement on the performance or battery life?
Thx...
Gloris said:
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
Click to expand...
Click to collapse
I have problem with install RUU, why?
Zlobizlob said:
I have problem with install RUU, why?
Click to expand...
Click to collapse
what is the error code?
things to remember when you flash an ruu :-
you should not have modified system files (except for root)
you should have stock recovery to start with
you may need to create gold card
you should be relocked bootoader
if you are already on a software number which is higher than the ruu you are trying to install, you may need to downgrade first, using the guide posted above.
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Stevk said:
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Click to expand...
Click to collapse
if you're s-off already, can't you just flash the radio.img?
don't quote me on that, i'm not s-off myself, so i'm not reallu 'up' on all the thigns you can do and how you do them. but i was under the impression that with s-off you can flash it same as you flash recovery.img or system.img?
Do I need to flash radio? Because my girlfriends WFS has been t-mobile branded so I think I'm not able to flash RUU without gold crad?
Is it possible to flash system.img and boot.img only? Or will there be conflicts with radio/ramdisk etc...
BL is unlocked and device is rooted atm!
I installed this RUU to my Wildfire S by this tutorial
Code:
http://forum.xda-developers.com/showthread.php?t=1540952
My phone had unlocked bootloader (via htcdev.com), Root, S-On and my Hboot version was 1.09.0099. When I was trying to install RUU I got ERROR 140(bad hboot version). So I used mentioned tutorial to downgrade hboot and then I install new RUU.
I downloaded RUU 2.26.401.3 from this site because on Football's FileFactory link are allways full slots.
Code:
http://narod.ru/disk/51502291001.c558c29e878e383684edd1a956d417fd/RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.html
And there is a ZIP version if someone want
Code:
http://narod.ru/disk/51500892001.cf33d25826e44363856289cb11302527/PG76IMG%20-%20Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M.zip.html
Sorry for poor english.
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Any issues unlocking BL and rooting this update? Any compelling reason to stay with 2.13.401.2/3?
Heritz said:
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Click to expand...
Click to collapse
I can upload RUU from russian site. Choose on which file hosting server. I dont know which is good.
EDIT - I solved it.

Stock Recovery for HOX 1.29.709.12

This info is for those who only root their HOX Taiwan version phones without custom ROM. When trying the OTA update 2.17.709.2 (Taiwan unbranded version), I had a hard time to find the recovery of Taiwan version 1.29.709.12.
If you are in the same situation as mine, no need to relock, unroot or anything. Just follow the steps to get OTA installed:
1. Download the IMG file, place it in the same folder with fastboot files.
2. Make sure HOX is "Fastboot USB" mode.
3. In cmd: fastboot flash recovery recovery_signed.img
4. Click "Software Update"
5. Once you have install the latest OTA, you can flash whatever recovery you want.
For those who need the 1.29.709.12 RUU, someone else provided this link to download the file. PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.12_Radio_1.1204.107.14_release_261362_signed.zip
BrianInfo said:
This info is for those who only root their HOX Taiwan version phones without custom ROM. When trying the OTA update 2.17.709.2 (Taiwan unbranded version), I had a hard time to find the recovery of Taiwan version 1.29.709.12.
If you are in the same situation as mine, no need to relock, unroot or anything. Just follow the steps to get OTA installed:
1. Download the IMG file, place it in the same folder with fastboot files.
2. Make sure HOX is "Fastboot USB" mode.
3. In cmd: fastboot flash recovery recovery_signed.img
4. Click "Software Update"
5. Once you have install the latest OTA, you can flash whatever recovery you want.
For those who need the 1.29.709.12 RUU, someone else provided this link to download the file. PJ46IMG_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.12_Radio_1.1204.107.14_release_261362_signed.zip
Click to expand...
Click to collapse
hi
for the rom u can chek below link it should be available
link : http://forum.xda-developers.com/showthread.php?t=1543604
haree said:
hi
for the rom u can chek below link it should be available
link : http://forum.xda-developers.com/showthread.php?t=1543604
Click to expand...
Click to collapse
Checked the that link before.
They dont have this specific RUU. (the software number and baseband version).
thanks alot BrainInfo, you are about to save my phone, i'm downloading then lets try, thanks again mate
I was really looking for this stock rom, but unfortunately after downloading i found it .zip not RUU, so i couldn't flash it, how suppose i flash it to my HOX man? Appreciate ur help
Sent from my HTC One X using xda app-developers app
Hossam.Abdelsalam said:
I was really looking for this stock rom, but unfortunately after downloading i found it .zip not RUU, so i couldn't flash it, how suppose i flash it to my HOX man? Appreciate ur help
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not 100% since I only used stock recovery image.
Some links from other posters. Try it on your own risk.
http://forum.xda-developers.com/showthread.php?t=1658929
http://forum.xda-developers.com/showthread.php?t=1690692
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Stock ROM for HOX 2.17.709.2
BrianInfo said:
Not 100% since I only used stock recovery image.
Some links from other posters. Try it on your own risk.
http://forum.xda-developers.com/showthread.php?t=1658929
http://forum.xda-developers.com/showthread.php?t=1690692
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Click to expand...
Click to collapse
Now there is the latest update 2.17.709.7,
So I need to get the stock recovery from 2.17.709.2 then follow the same steps to get the latest OTA.
This is where I get the stock rom, http://pan.baidu.com/share/link?shareid=31046&uk=2248202954
thanks man, finally my HOX is back to stock

Needing repair in warranty: Back to stock having a 3.18 based Rom

Hello Everyone, as in the subject, my touch isn't working, so i need to ship my phone(under warranty) to the technical center,
so, I wanted to relock the bootloader and use a ruu .
Here it's my problem, i tryed many many method, but i cannot use the latest available ruu (3.14.x) since i installed before the originale stock 3.18.x rom.
The ruu. exe give me every times the error 140, even if i try after rewriting boot.img, signed_recovery.img and so on.
I tryed many things, but i cannot do it, so here my questions:
1) Someone already have the right working solution?
2) i thought to flash a stock rom based on 3.14.401.31 and retry to use the ruu, so can someone give me a link to download a "old" rom like that?
3) other suggests?
Thank you very very much in advance for your help!
Kashanir said:
Hello Everyone, as in the subject, my touch isn't working, so i need to ship my phone(under warranty) to the technical center,
so, I wanted to relock the bootloader and use a ruu .
Here it's my problem, i tryed many many method, but i cannot use the latest available ruu (3.14.x) since i installed before the originale stock 3.18.x rom.
The ruu. exe give me every times the error 140, even if i try after rewriting boot.img, signed_recovery.img and so on.
I tryed many things, but i cannot do it, so here my questions:
1) Someone already have the right working solution?
2) i thought to flash a stock rom based on 3.14.401.31 and retry to use the ruu, so can someone give me a link to download a "old" rom like that?
3) other suggests?
Thank you very very much in advance for your help!
Click to expand...
Click to collapse
Flash a custom recovery and then flash a stock 3.18 nandroid inc boot image that matches your cid. Once the nandroid has been flashed, flash the stock recovery and relock the bootloader. Perform a factory reset to remove the previous users data. You should then be able to send the phone back to HTC
Hope it helps
ghori1989 said:
Flash a custom recovery and then flash a stock 3.18 nandroid inc boot image that matches your cid. Once the nandroid has been flashed, flash the stock recovery and relock the bootloader. Perform a factory reset to remove the previous users data. You should then be able to send the phone back to HTC
Hope it helps
Click to expand...
Click to collapse
first of all thank you for your reply,
I already try to restore a 3.18 nandroid, downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1975140 (cid 032)
I restore it by trwp, but i was some problem, the touch doesn't work, after check and recheck i thought that the problem was in boot.img, so i try to download the 3.14 boot.img and i flash it, but i had same result, i tryed with others and every times i have a different problem, the last, i have no gsm signal and it looks like the phone had no imei.
Maybe i just need a correct boot.img, but i still didn't find it
do you think i'm right?
Kashanir said:
first of all thank you for your reply,
I already try to restore a 3.18 nandroid, downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1975140 (cid 032)
I restore it by trwp, but i was some problem, the touch doesn't work, after check and recheck i thought that the problem was in boot.img, so i try to download the 3.14 boot.img and i flash it, but i had same result, i tryed with others and every times i have a different problem, the last, i have no gsm signal and it looks like the phone had no imei.
Maybe i just need a correct boot.img, but i still didn't find it
do you think i'm right?
Click to expand...
Click to collapse
I would flash the firmwire zip again.
Here is the link http://forum.xda-developers.com/showpost.php?p=38781030&postcount=29
It contains the new touch image, stock recovery, boot image etc
If that does not help you could flash a stock rom created by Mike1986 using trwp or cwm. Flash the stock recovery and then lock the bootloader.
http://forum.xda-developers.com/showthread.php?t=1546970
ghori1989 said:
I would flash the firmwire zip again.
Here is the link http://forum.xda-developers.com/showpost.php?p=38781030&postcount=29
It contains the new touch image, stock recovery, boot image etc
If that does not help you could flash a stock rom created by Mike1986 using trwp or cwm. Flash the stock recovery and then lock the bootloader.
http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
Ok, the first suggest didin't work, but with the second suggest i flash the stock rom (odexed version) i flash the recovery, i lock the bootloader.
Now it looks ok!
I hope this topic could be useful to someone else: the only way (at least in my case) to have a stock rom if in the phone was a 3.18 version, is to upgrade to that 3.19....i don't know why, but...that's it!
Kashanir said:
Ok, the first suggest didin't work, but with the second suggest i flash the stock rom (odexed version) i flash the recovery, i lock the bootloader.
Now it looks ok!
I hope this topic could be useful to someone else: the only way (at least in my case) to have a stock rom if in the phone was a 3.18 version, is to upgrade to that 3.19....i don't know why, but...that's it!
Click to expand...
Click to collapse
Thats good to know that you got it back to stock. You should be able to send it back to be repaired.
And if you have trouble with TWRP touch(and you will because of flashing new firmware in stock JB OTA) you need to use TWRP 2.4.0.0 from main TWRP page but only TWRP 2.4.0.0 with JB string at the end, or TWRP 2.5.0.0 repacked also to work with JB from here:http://forum.xda-developers.com/showpost.php?p=40120901&postcount=509, and because of upgrade to JB firmware in this versions of TWRP you have touch but no mont usb storage and adb working in recovery, i think that new CWM 6.0.3.0 have adb support and mount usb storage but no touch..

T-mobile Firmware issue help required

i have a t-mobile version of htc one m8 but when flashing ROMs , i flash international version of the ROM which i'm flashing. The phone is sim-unlocked.
Lately i'm having problem of my phone getting stuck on boot and only way out is wipe cache and dalvik on every time i reboot. And also GPS is not working (tried every fix but no avail) I'm guessing his is some firmware problem.
So the thing is I want to get back to Android 4.4.4 version ( on which it was earlier before i flashed any Lollipop rom , so that i could flash T-mobile's OTA to Lollipop back ( for firmware update ) and after reading and some research , i have understood that i have to be stock recovery and relock the bootloader and get T-mobile RUU ( very confused about RUU thing)
Could someone confirm if this is the correct procedure and explain what steps i need to follow IN ORDER to get this done ( and if links to corresponding guides i will be really helpful) .
I AM S-ON.
Hboot - 3.19
Radio - 1.22.213311491.08G
Please help , really frustrated by these issues and apparently previous threads of mine have gone unanswered.
Unfortunately, if you want to revert to KK (or any older version), you will have to be S-off to do so. So, pay the $25, get S-off (which will helpfully unlock your bootloader at the same time), run T-Mobile RUU for desired version.
However, even if you are S-on, you should be able to use a current or newer RUU to get the firmware up to date, then move on to installing the ROM of your choice. You are probably better off going to the latest firmware and running an alternate ROM, but that's just me.
jshamlet said:
However, even if you are S-on, you should be able to use a current or newer RUU to get the firmware up to date, then move on to installing the ROM of your choice. You are probably better off going to the latest firmware and running an alternate ROM, but that's just me.
Click to expand...
Click to collapse
So if i were to follow S-on steps , i will have to first flash stock recovery , relock bootloader and run t-mobile RUU for firmware upgrade ?
When i relock bootloader everything will be wiped , right ?
So i connect my phone to pc with relocked bootloader and stock recovery and run t-mobile latest RUU on windows ?
Is this the correct procedure?
rahulsethi said:
So if i were to follow S-on steps , i will have to first flash stock recovery , relock bootloader and run t-mobile RUU for firmware upgrade ?
When i relock bootloader everything will be wiped , right ?
So i connect my phone to pc with relocked bootloader and stock recovery and run t-mobile latest RUU on windows ?
Is this the correct procedure?
Click to expand...
Click to collapse
That is all true; except you do not need to install stock recovery to RUU.
Stock recovery is only needed to OTA, not for RUU.

RUU Failed, OPJAIMG not recognized

Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
@Flippy498 maybe you have an idea? You have so much knowledge on this!
I haven't seen a 4.x RUU for the SKU 401, yet. You therefore would need to flash one of Sneakyghost's 3.x firmware packs before you're able to use a 3.x RUU, again. The encryption key changed between firmware 3.x and 4.x. Therefore you can't use 4.x RUUs on firmware 1.x to 3.x and vice versa.
In contrast to the flashing command the command for booting TWRP via fastboot needs to be used while the phone is booted to the bootloader instead of the download mode. However, since I haven't seen a publicly available TWRP backup for the latest 401 firmware, yet, TWRP won't help you much in your situation. (Or do you have your own backup?)
That means on the other hand that you currently need to downgrade to 3.35.401.12 and to re-install the OTAs for 3.35.401.32 and 4.14.401.7 since the latest RUU is for version 3.35.401.12.
Edit: Oh, and the only RUU.exe for SKU 401 that I know is for that 1.x firmware wird the 17 at the end. You shouldn't use that one. The corresponding OTA only got distributed for one single CID (I forgot which one it was). That means that you won't receive OTAs if you aren't using that specific CID on your phone. That means you would need to flash another RUU afterwards for getting away from that firmware version. And instead of flashing two RUUs you could save some time and directly flash the second one.
Sent from my HTC One M9 using XDA Labs
mrsmtt said:
Hi guys i'll explaine what happened:
1. I was on nougat rom rooted trying to get back to stock.
2. I run an old lollipop ruu.exe from my computer but it reboots the phone to bootloader mode without going on.
3. I manually reboot to bootloader to see it if does move on but nothing.
4. I disconnect the phone.
Now there's no OS and recovery and flashing TWRP succeeds but when I try to reboot to recovery it say that's not possible.
I tried to flash via sdcard the OPJAIMG but it seems like it doesn't see it (screenshot in attachements).
I can access download mode
I'm S-OFF on Nougat firmware.. what can i do?
EDIT: I tried to live-boot TWRP but it stays forever on booting in cmd and flashing in phone
Click to expand...
Click to collapse
1 - Try 0(zero)PJAIMG and not O
2 - Restore to stock recovery
3 - Start phone in download mode and push volume UP
benshoes said:
1 - Try 0(zero)PJAIMG and not O
Click to expand...
Click to collapse
Oh, I missed that typo.
benshoes said:
2 - Restore to stock recovery
Click to expand...
Click to collapse
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Flippy498 said:
Oh, I missed that typo.
That's actually not needed. The RUU will flash the stock recovery by its own. You only need a working download mode.
Click to expand...
Click to collapse
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
mrsmtt said:
Tried to live-boot TWRP from bootloader since I have my own backup but it fails with the following message:
FAILED (remote: dtb not found)
About 0PJAIMG it is named correctly in SD it's just me that made a mistake writing here.
So last chance for me is to head to Sneakyghost's thread and flash the 3.35.401.32 fullstock firmware then head to your google sheet and pick the 3.35.401.12 RUU and flash it right?
Click to expand...
Click to collapse
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Flippy498 said:
Correct. Although you can use the 3.35.401.12 firmware pack, as well. It doesn't matter which one of the two firmware versions you choose.
Click to expand...
Click to collapse
Thanks for your support! Anyway i'm going to do the whole thing tomorrow.. I was reading the instructions on Sneakyghost's thread and he recommend to use his tool because it contains the htc_fastboot that works better than google's one but I don't see any option to lunch the flash zip firmware command from the tool so I decided to get the htc_fastboot.exe file and move it inside another folder (a new one) in wich i'll put both firmware and rom zip to flash. I'm saying this because i'm not 100% sure this is correct so just to clear all doubts..
Once again @Flippy498 you saved me and I say thank you a million times I promise i'll take a break at trying to destroy my m9 so you'll definitely not hear me / see me here anymore hehe

Categories

Resources