So long story short, I bricked my A226b and after a week of trying different things I noticed the product code was different when I was using Android Utilities. This could be why (my other post) I'm getting errors.
Looking around, the closest I can find to my problem is "build.prop" where the device I.D has changed after flash
I'm stuck in BROM and I can't get to DM or ADB, I'm searching for the answer but I still don't understand how to achieve changing the device I.D / Product I.D back so SP flash tool sees it as a correct model or deactivated this check etc.
I'm hoping I'm close to finding solution, any ideas?
Thank you
Decmanager said:
So long story short, I bricked my A226b and after a week of trying different things I noticed the product code was different when I was using Android Utilities. This could be why (my other post) I'm getting errors.
Looking around, the closest I can find to my problem is "build.prop" where the device I.D has changed after flash
I'm stuck in BROM and I can't get to DM or ADB, I'm searching for the answer but I still don't understand how to achieve changing the device I.D / Product I.D back so SP flash tool sees it as a correct model or deactivated this check etc.
I'm hoping I'm close to finding solution, any ideas?
Thank you
Click to expand...
Click to collapse
If your device is in BROM mode, and you have the right firmware files, SPFT, don´t check the device model to flash it, only it is based on the scatter file. Maybe you can upload some screenshots from the message you are receiving. Note that to really be sure your device is entering to BROM mode, you have to check in device manager, that it is in preloader mode, and using other tool, device will stay in BROM mode. Can you describe what you have with?
I'm bricked in brom, I use auth bypass, then Android Utilities / A226b dead boot repair and when it reads it, it shows product code of A12 and hangs back to brom. I feel like I've flashed it to be a12 some how and when I try flash the correct files it's giving me an error.
*(in my other post are the details of why I'm doing it and some logs / I'm not sure how I bricked it)
Waiting for mtk usb device... ok
BootMode : BootRom[COM21]
DriverDesc : MediaTek USB Port
DriverPath : usb\vid_0e8d&pid_0003\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● BBChip ID MT6833
● BBChip Inf 989:8A00:CA00:0
● Chip PID Dimensity 700
● Chip UID Palmer
● Chip Ver CHIP_VER_E1
BRom::SEC:{0xe5}[SBC:ON:SLA:OFFAA:ON]
BRom stage Re-configuration
● BR_MEID:0x76206C45E7FF29381C34C136A484886F
Disabling watchdog timer0...
BRom::WinUSB:evHnd{0xefaf700}
BRom::WinUSB:evHnd{0xefb0218}
BRom::WinUSB:evHnd{0xefb07e0}
===== Bypass Authentication =====
Dumping Dram data(0xa47a0500)...
Re-connecting to BootROM...
Sending Download Agent(A037F)...
Booting Download Agent at(0x200000)...
Successfully received DA sync cahr
Start setup da environment...
Setup da device enviroment...
Successfully received 1st DA sync signal
Initialize Dram(0x1000)...
Dram initialized
Boot and enter 2nd DA...
Boot 2nd Da done! Getting Ram Info
● Sram 448.00KB
● Dram 4.00GB
Boot and enter 2nd SEC DA...
===== Power On HACC =====
Boot 2nd SEC DA done! Getting HW Info
● Storage eMMC
● BOOT1 4.00MB
● BOOT2 4.00MB
● RPMB 16.00MB
● GP1 00000000
● GP2 00000000
● GP3 00000000
● GP4 00000000
● USR 58.24GB
● MLC 00000001
● SLC 00000001
● EOL 00000001
● LCYCLE 00000000
● CID 13014E47314A395238101B685D0A29D1
● MFRID 0x13
● Vendor Micron
● Card BGA BGA (Discrete embedded)
● OEMID 0x4e
● Product G1J9R8
● Revision 1.0
● Card SN 0x1b685d0a
● MFDate 2/2022
● EMCP MT29VZZZAD8GQFSL_046W_9R8
● Capacity 0xe91000000:58.27GB
● RNID 07C80DE18DA944D652A025AC302451BA
Switching to usb high-speed...
===== wait for DA high speed port =====
Waiting for mtk da device... ok
BootMode : MTK DA VCOM[COM22]
DriverDesc : MediaTek DA USB VCOM (Android)
DriverPath : usb\vid_0e8d&pid_2001\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● USBSpeed high-speed
Gathering partitions info...
===== wait for DA S/W detection report =====
===== Download boot_section to device =====
BOOT-A/B region(s) successfully updated!
===== Download user_section to device =====
(P/S)-GPT header(s) and entries(s) successfully updated!
Rebooting device... Done
Waiting for samsung-dm usb device...
**AND THEN HANGS**
It's showing up as : ● Product - G1J9R8
Decmanager said:
Waiting for mtk usb device... ok
BootMode : BootRom[COM21]
DriverDesc : MediaTek USB Port
DriverPath : usb\vid_0e8d&pid_0003\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● BBChip ID MT6833
● BBChip Inf 989:8A00:CA00:0
● Chip PID Dimensity 700
● Chip UID Palmer
● Chip Ver CHIP_VER_E1
BRom::SEC:{0xe5}[SBC:ON:SLA:OFFAA:ON]
BRom stage Re-configuration
● BR_MEID:0x76206C45E7FF29381C34C136A484886F
Disabling watchdog timer0...
BRom::WinUSB:evHnd{0xefaf700}
BRom::WinUSB:evHnd{0xefb0218}
BRom::WinUSB:evHnd{0xefb07e0}
===== Bypass Authentication =====
Dumping Dram data(0xa47a0500)...
Re-connecting to BootROM...
Sending Download Agent(A037F)...
Booting Download Agent at(0x200000)...
Successfully received DA sync cahr
Start setup da environment...
Setup da device enviroment...
Successfully received 1st DA sync signal
Initialize Dram(0x1000)...
Dram initialized
Boot and enter 2nd DA...
Boot 2nd Da done! Getting Ram Info
● Sram 448.00KB
● Dram 4.00GB
Boot and enter 2nd SEC DA...
===== Power On HACC =====
Boot 2nd SEC DA done! Getting HW Info
● Storage eMMC
● BOOT1 4.00MB
● BOOT2 4.00MB
● RPMB 16.00MB
● GP1 00000000
● GP2 00000000
● GP3 00000000
● GP4 00000000
● USR 58.24GB
● MLC 00000001
● SLC 00000001
● EOL 00000001
● LCYCLE 00000000
● CID 13014E47314A395238101B685D0A29D1
● MFRID 0x13
● Vendor Micron
● Card BGA BGA (Discrete embedded)
● OEMID 0x4e
● Product G1J9R8
● Revision 1.0
● Card SN 0x1b685d0a
● MFDate 2/2022
● EMCP MT29VZZZAD8GQFSL_046W_9R8
● Capacity 0xe91000000:58.27GB
● RNID 07C80DE18DA944D652A025AC302451BA
Switching to usb high-speed...
===== wait for DA high speed port =====
Waiting for mtk da device... ok
BootMode : MTK DA VCOM[COM22]
DriverDesc : MediaTek DA USB VCOM (Android)
DriverPath : usb\vid_0e8d&pid_2001\6&39447387&0&2
DriverSRV : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
DriverCFG : oem25.inf
DriverOEM : MediaTek Inc.
● USBSpeed high-speed
Gathering partitions info...
===== wait for DA S/W detection report =====
===== Download boot_section to device =====
BOOT-A/B region(s) successfully updated!
===== Download user_section to device =====
(P/S)-GPT header(s) and entries(s) successfully updated!
Rebooting device... Done
Waiting for samsung-dm usb device...
**AND THEN HANGS**
It's showing up as : ● Product - G1J9R8
Click to expand...
Click to collapse
I saw you had "verified boot enabled" error, in the other post. You can try this https://www.hovatek.com/forum/thread-39260.html, but, excluding some files for the flash round, you can bypass that error, I have to see the files in SPFT, to can remember which (I also had the same issue with other device).
G1J9R8 it´s just the eMMc RAM product, not your device, the error may happen with UFI boxes.
You won´t have issues flashing any partition, through mtk-client.
SubwayChamp said:
I saw you had "verified boot enabled" error, in the other post. You can try this https://www.hovatek.com/forum/thread-39260.html, but, excluding some files for the flash round, you can bypass that error, I have to see the files in SPFT, to can remember which (I also had the same issue with other device).
G1J9R8 it´s just the eMMc RAM product, not your device, the error may happen with UFI boxes.
You won´t have issues flashing any partition, through mtk-client.
Click to expand...
Click to collapse
OK I setup and ready to flash with MTK client, can you point me to the simplest method to flash my MT6833 or what ever it is I need. I am also actively searching for info but if you have something please post. Thank you lots.
Decmanager said:
OK I setup and ready to flash with MTK client, can you point me to the simplest method to flash my MT6833 or what ever it is I need. I am also actively searching for info but if you have something please post. Thank you lots.
Click to expand...
Click to collapse
Simple, unlock bootloader through mtk-client (don´t erase metadata), then flash all the partitions available in the firmware.
SubwayChamp said:
Simple, unlock bootloader through mtk-client (don´t erase metadata), then flash all the partitions available in the firmware.
Click to expand...
Click to collapse
Couldn't find good solution to unlock bootloader, the phone stuck in Brom.
Related
my phone model- CENTRIC CM2221
android -6.0
problem- no service
i check imei blank and baseband unknown .
how to solve ?
please provide me stock rom or good solution ..
Phone Info Log .........
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 16 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6737
BB_CPU_NME : [MediaTek] MT6737M|MT6737_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x93
NAND Flash : NOT INSTALLED
eMMC Flash : 510001154D333238E8020042AF2EBAF4
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM328
[eMMC] : FLASH_CID : 150100513832334D420002E8F4BA73AF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xEF0B331D1BA71095953C8F7CFAA875FB
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro
abuk91 said:
You cm2 to Repaire baseband
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bro allready try but not done .....need flash file
no solution????????????????????????????????????????????????????????????
I have the same problem
phone accent neon no service imei not found
I'm looking for rom file for this model
need MTK6737 cpu .....nv data
please give me any read nv file for mt6737 cpu.....
Raj_App said:
need MTK6737 cpu .....nv data
please give me any read nv file for mt6737 cpu.....
Click to expand...
Click to collapse
That's not a wise request (and I don't think it's legal).
NVDATA contains IMEI information (and you know it). An IMEI is unique for a device. One device, one IMEI. What you're asking is requesting someone else to share their IMEI with you. Two phones with the same IMEI is not legal.
Restore your ORIGINAL NVDATA to get back your original IMEI.
Nonta72 said:
That's not a wise request (and I don't think it's legal).
NVDATA contains IMEI information (and you know it). An IMEI is unique for a device. One device, one IMEI. What you're asking is requesting someone else to share their IMEI with you. Two phones with the same IMEI is not legal.
Restore your ORIGINAL NVDATA to get back your original IMEI.
Click to expand...
Click to collapse
Wait for phone...
Phone found! [ 16 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6737
BB_CPU_NME : [MediaTek] MT6737M|MT6737_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x93
NAND Flash : NOT INSTALLED
eMMC Flash : 510001154D333238E8020042AF2EBAF4
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM328
[eMMC] : FLASH_CID : 150100513832334D420002E8F4BA73AF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xEF0B331D1BA71095953C8F7CFAA875FB
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!
[Info] : BaseBand : MT6735_S00_MOLY_LR9_W1444_MD_LWTG_MP_V79_P20_1_lwg_n
Read Error , NVRAM area is blank or damaged
Operation Failed
Elapsed: 00:00:29
Reconnect Power/Cable!
Raj_App said:
Read Error , NVRAM area is blank or damaged
Operation Failed
Click to expand...
Click to collapse
Use SP Flash Tools to flash your stock rom.
Nonta72 said:
Use SP Flash Tools to flash your stock rom.
Click to expand...
Click to collapse
bro i tired ..not found rom
please help me
Raj_App said:
bro i tired ..not found rom
please help me
Click to expand...
Click to collapse
Find it on your manufacturer's website or needrom.com
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
Wait for phone...
Phone found! [ 1087 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6755
BB_CPU_NME : [MediaTek] Helio[P10]|MT6755_S00
BB_CPU_EXT : 0xCB00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x01000000
BromVer : 0x0005
BLVersion : 0x00FE
PreLoader : NOT Active [ Erased ]
BootLdrSS : SIGNED with SPRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
DAgent configured successfully
Connection agent : BROM
[DA_ERROR] : DRAM Configure failed!
ErroCode : 0x2122and I get this message error if I try to flash it with MT6750
Error: STATUS_INSUFFICIENT_BUFFER
EMICFG_NOT_ACCEPTED_CONFIG
Boot Error!
Operation Failed
Elapsed: 00:00:52
Reconnect Power/Cable!
Click to expand...
Click to collapse
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
octopus82 said:
Hello
I've bricked Oppo F1s when I've tried to flash it
this is infinity read info log
it says that's an MT6755 processor , but when I try to flash it with Mt6755 with sp flashtool and NCK mtk soft it says that's version mismatch and it's and MT6750 device
Can you help to choose the right firmware please ?
Click to expand...
Click to collapse
I have pretty much the same problem with my MOTO M (XT1662). It happened after I did the "Format whole flash" in SP flash tool.
Now the SP flash tool is giving me the following,
Chip Info
=======
Chip name: MT6755
Chip Version: 0x0000cb00
Ext Clock: EXT_26M
Extern RAM Type: DRAM
Extern RAM Size: 0xc0000000 (!!!)
SRAM Size: 0x00040000
EMMC Flash
=========
Boot 1 Size: 0x400000
Boot 2 Size: 0x400000
RPMB Size: 0x400000
GP1 Size: 0x0 (same for GP2, GP3 and GP4)
UA Size: 0x747c00000
No matter what ROM I'm trying to flash (stock or custom) , I always get the error "STATUS_INSUFFICIENT_BUFFER (0xC0010007)".
It looks like it has to do something with the External RAM Size (0xc0000000).
I found this firmware "XT1662_Kungfu_m_MT6755_USR_S0924_1612291517_mp7V2.3_CN (RepairMyMobile.in)", which seems to be what I need but I can't get pass this error.
Any help will be greatly appreciated.
i have the same problem
STATUS_INSUFFICIENT_BUFFER (0xC0010007)
i try to update with OTA and failed too
anyone can help ?
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
t-mobile_mda said:
hey guys..
i have a module which called bus multimedia.. i need root or read full backup of this device.. but there is no usb socket only exist RX TX pinout and i cannot connect it to pc over putty.. is anyone help me to read backup.?
Click to expand...
Click to collapse
hey.. i removed the emmc and info..do u think that this device is android based..?
HiPower mode is On
Setting Interface to EasyJtag1/ISP_HiPower
Setting IO Levels to 3.3V
Setting Frequence to 21 Mhz
Setting BusWidth to 1 Bit
CMD Pullup Level: 2134 mV
CMD Active Level: 2609 mV
Setting HS Timing to Enabled
EMMC Device Information :
EMMC CID: 7001004D3732383038801500009374CA
EMMC CSD: D04F01320F5903FFFFFFFFEF8A400060
Manufacturer: KINGSTONE , NAME: M72808 , HEX: 4D3732383038 , S/N: 15000093 , Rev: 80
Manufacturer ID: 70 , OEM ID: 00 , Device Type: BGA (Discrete embedded) , Date: 7/2017
EMMC ROM 1 (Main User Data) Capacity: 7296 MB (0x0001C8000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (0x000000400000)
EMMC RPMB Capacity: 4096 KB (0x000000400000) , Counter: 0 , Response: Clean
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x00 , Device not boot enabled
Boot Bus Config: 0x00 , x1 (sdr) or x4 (ddr) bus width in boot operation mode
H/W Reset Function [RST_N_FUNCTION]: 0x00 , RST_n signal is temporarily disabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition settings [PARTITION_SETTING_COMPLETED]: 0x00
EMMC Init completed
Backup saved: M72808_15000093_20220611_141710.extcsd (new backup)
Connected successfully
Operation: Scan PartitionTable from Source (Vendor: Binary Read/Write)
Scanning soft partitions from ROM2
GPT header is not found
Scanning soft partitions from ROM3
GPT header is not found
Scanning soft partitions from ROM1
GPT header is not found
MBR header is not found
You need a usb to uart device to get started on that board. You can find one online for about 3 dollars.
I wanted to upload new rom to my Nokia TA-1188 via SP_Flash_Tool-5.1916_Linux.
Rom: https://drive.google.com/uc?id=1ORCq7T2H8ECCjqd4SDn9uODsGhKFcoff&export=download
and I have error:
$ ./flash_tool.sh
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-1
[email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0
[email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1665148920.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
DA Connected
executing DADownloadAll...
Stage:
[0] WRITE TO PARTITION [ preloader ]
Stage:
[4] WRITE TO PARTITION [ custom_a ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_IMG_TYPE_MISMATCH (-1073610710) , MSP ERROE CODE : 0x00.
[HINT]:
Verified boot is enabled.
Please download signed image(custom_a-verified.img) or disable verified boot.)((exec,../../../flashtool/Cmd/DADownloadAll.cpp,84))
Click to expand...
Click to collapse
and now I can't start fastboot mode on the phone and the phone can't be turned on.
I try:
- Vol- and usb kable to computer - 30s wait - nothing
- power on buttom - 60s wait - nothing
- https://forum.xda-developers.com/t/hard-reset-nokia-2-2.4000739/#post-81795587 - nothing
What did I do wrong and how to fix it?
Is my phone just for trash, or is it possible to get it working somehow?
Help please.