HTC desire 628 dual sim stock rom file and flashing with SP flash tool - HTC Desire 630 Questions & Answers

Hi,
I was having an issue with my HTC Desire 628 dual sim phone. Earlier it was automatically restart. Then i tried to flash the firmware using SP flash tool and forgot to make a back up. I have selected format all & download option in the flash tool. After that, flashing was succeeded with 100%. But now my phone is not starting up. any thing to do with it. Really appreciate your support.
***Locked***
HTC_V36BML 128 SHIP S-ON
CID-HTC__060
LK-1.01.0000
OS-1.17.400.1
I have used below firmware file name which i have downloaded for SP flash tool.
2PVGIMG_V36BML_DUGL_L51_DESIRE_SENSE70_HTC_India_S EA_1.17.400.1_Radio_0.1524V28P45.0504.0422_1_relea se_504976_combined_signed_2_4.zip
Thank you in advance.

Related

Desire X Bricked EMMC

Hi,
if Desire X EMMC is bricked and phone stuck on htc boot logo screen.
so via CWM can we partition our external SD as EMMC and boot the phone.
Regards
Bluffmaster
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
vogonpoetlaureate said:
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I think maybe is a guide not an help thread from his post..
xpirt
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
bluffmaster said:
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
Click to expand...
Click to collapse
Find the decrypted rom.zip somewhere and extract the boot.img. Flash that. Then flash Desire X 1.18 stock rooted rom to give them root and deodex. Tell your customer they're rooted and that everything should work fine...
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
bluffmaster said:
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
Click to expand...
Click to collapse
Yes!
Dear Stereo 8,
I Just Follow all you instruction , but i got black screen after htc sound ?
any suggestion
Weird... I'm clueless...
Flowed from my HTC branded muffin...
Hi,
Riff box release new DLL, so after resurrection with new dll i flash with stock ruu but phone stuck at boot screen and also not go to recovery.
from old dll it stuck on boot screen but can go to recovery so i can flash CWM but after new dll no recovery ?
What can i do .. confused
Fastboot flash recovery if you can go to fastboot.
Flowed from my HTC branded muffin...
i can boot to fast boot and i install CWM Recovery via fastboot.
but when i go to recovery its stuck at htc logo then restart it
Well, it's probably dead if you can't boot it whatever you flash....
Flowed from my HTC branded muffin...
You are wrong, Riff box restores the EMMC to stock plus if you get successful Resurrection with Riff it should be fine this means the problem is NOT EMMC which leads me to believe the device has a hardware fault but then you say if you install rom to Sd-ext the phone boots although unstable it atleast boots up. Which now leads me to think the device may have a unstable EMMC which means it needs the chip replacing. what you need to do is go to fastboot mode and open up a new CMD window and cd into your fastboot dir and type fastboot oem lock. Then run the Stock RUU and let it reboot into android. if that still dont help then PM me and send me your logs of resurrection from riff box and ill take a look at them see what the errors are thanks

[Q] Cannot flash any other firmware in fastboot on XT909?

Hi guys i am in bit of a pinch here.
I have a Moto Razr Xt909 which beloged to the carrier KIDDI. In order to get the sim Unlocked i flashed a firmware (9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml) on it and even though i can get the phone started using BP tools and it seems to be working fine except for he fact that my PC is unable to detect its internal memory even though it is connected to it and all the drivers are installed.
Problem is that I have tried many times but i am unable to flash any new firmware on it like VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml.zip.
Its a guess but I think that i can only flash firmwares from Europe now. All the other firwares i try to flash using RSD lite 6.0 don't complete and some get stuck at "boot.img" while others at "cdt.bin". I have been trying to flash multiple firmwares but till now all my efforts are in Vain :crying:
I want to flash other firmwares so please tell me how can i fix this issue.
System Version:
982.124.14.XT910.Retail.en.EU
The other details that my phone displays in about phone are attached as pic. please check the pic and guide me.
Thanks in advance
I see you've already erased your cid without backup, but if you have backupwhen try. If you wanna flash different region firmware on your Razr, you should root it when install BMM. Reboot to BMM & use Firmware Flashing to Backup CID and then erase it. After that you could try to flash XT912 JB via RSD or system + boot.img dump via BMM.

[Q] bootloader unlock

Hello, XDA!
I have a question.
I want to try to unlock my bootloader.
But there is no method for my device.
But I find a device with same specs as mine that has a method for unlocking.
Can I use that method for my device?
It says that I need to flash these files: lk.bin, recovery.img, preloader.bin via SP Flash Tools.
These files are for unlocking Alcatel Pop 4S but as I said before, it's a phone with same specs..
I'm affraid of damaging the bootloader.
If I will damage it, can I recover or reflash my phones rom back via flash tool without problem?
Or the phone will be totally dead?
Thank you for your time and help.
Odesláno z mého VFD 700

Bricked k8 plus (3gb ram indian variant)

hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself

SP tool error chip type not match after wrong stock rom

Dear all,
I have flashed the wrong stock rom on my tablet (lenovo). Now i have the right stock rom, but when i use SP tool to flash i get the error "Chip type not match. Target chip is MT6580. load scatter chip is MT6582."
First i flashed stock rom Lenovo tab 3 710I, i tried to boot, but i got only a black screen with vibrating every 2-3 seconds. Then i knew the right model for the device, which is lenovo tab 2 A7-30HC , so i tried to flash it but i got the "chip type not match" error.
could you please help me solve this problem?
best regards,
Format the device with wrong scatter file and after that load orginal one and try
also try flashing recovery (if avilable ) via adb
Trex2017 said:
Format the device with wrong scatter file and after that load orginal one and try
also try flashing recovery (if avilable ) via adb
Click to expand...
Click to collapse
good idea.format the device and then re flash the correct firmware.
Also have the same error
I also have the same thing going on. except that i haven't flashed the device yet. I have an AG Boost Dual SIM. I downloaded the ROM from firmwarefile[dot]com but the chip type of the phone is MT6572 While the scatter of the ROM has MT6580. Should i look for another ROM or is there some kind of hacks and back doors to flash the same ROM?
how to format with wrong scatter?

Categories

Resources