RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
@AumAum here's my thread for the Red Hydrogen One in case you want to help me get it going. Thanks
I have an unlocked AT&T variant but cannot reboot into fastboot. Holding down vol- and power from power-off only results in a looping RED logo.
Any ideas?
If I can get this working, I can dump a stock AT&T 8.0 ROM.
xeper said:
I have an unlocked AT&T variant but cannot reboot into fastboot. Holding down vol- and power from power-off only results in a looping RED logo.
Any ideas?
If I can get this working, I can dump a stock AT&T 8.0 ROM.
Click to expand...
Click to collapse
Try adb reboot bootloader
Mohsin6643 said:
Try adb reboot bootloader
Click to expand...
Click to collapse
Wow I feel dumb.
This worked before, but I didn't have an Android bootloader driver for the phone. :|
Updated the driver while it's in the bootloader and it works!
xeper said:
Wow I feel dumb.
This worked before, but I didn't have an Android bootloader driver for the phone. :|
Updated the driver while it's in the bootloader and it works!
Click to expand...
Click to collapse
Glad to know it all worked out. Bugjaeger for Android, works if you need ADB/Fastboot without a pc.
KlutchApex said:
Here is the best link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
Android 9 ROM package
ATTENTION: IT WILL WIPE ALL OF YOUR USER DATA
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
This file does not contain the ADBWinAPI.dll file, but I have fixed it here:
File on MEGA
mega.nz
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Saloomy83 said:
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Click to expand...
Click to collapse
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
I'm waiting for the file my friend. I hope you upload it as fast as u can.
I'm still waiting for the Qcn file, plz.
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
I'm still here waiting for the file
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
Friend , are you there? I'm still waiting for the Qcn file or efs back up , plz
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
Friend, I'm really in trouble. I can't use my phone anymore. You can save my phone if you upload a dump for modemst1 and modemst2 or efs backup or QCN FILE OR NV .
Saloomy83 said:
Friend, I'm really in trouble. I can't use my phone anymore. You can save my phone if you upload a dump for modemst1 and modemst2 or efs backup or QCN FILE OR NV .
Click to expand...
Click to collapse
Give me your IMEI and other relevant info in a DM and I will send you the corrected files
Saloomy83 said:
I excuted this command in fastboot,.
Fastboot erase modemst1 and same for modemst2.
Now no signal at all and imei is 0.
I have been flashing the phone with ur rom for 2days but not signal nor imei back.
Please, who can share me Qcn file for this phone, i Will be grateful for him.
Click to expand...
Click to collapse
the QCN is included in the ROM
KlutchApex said:
I'll see what I can do for you. Give me a few minutes and I'll get it uploaded
Click to expand...
Click to collapse
What were you thinking erasing those partitions? Please follow the instructions correctly
KlutchApex said:
Give me your IMEI and other relevant info in a DM and I will send you the corrected
Click to expand...
Click to collapse
Thank u.
I have solved the problem
KlutchApex said:
the QCN is included in the ROM
Click to expand...
Click to collapse
Where?
Which one.
KlutchApex said:
What were you thinking erasing those partitions? Please follow the instructions correctly
Click to expand...
Click to collapse
Cuz when I was inserting my CDMA sim card , there was no service. I found some posts suggesting erasing these two partitions to solve the problem.
Saloomy83 said:
Im
Click to expand...
Click to collapse
Solved.
Or you can give me the file and I will edit it and add my IMEI and other information.
Hi for those people that doesnt know much;
This is for those that cant enter to fastboot , or hard bricked after update like me.
QFIL ROM FOR RED HYDROGEN ONE (NOT TITANIUM)
ROM
Respective credit in the post
1-To put in edl mode you need to hold volume up and down , with power botom holding;
you will see In device manager Something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2- you need to Install Qfill. ONLY qfil NOT drivers...
If you install Newest Qfil driver you may see " qualcomm hs usb qdloader 9008 " and your flash will give you errors ,
QFIL Download
Drivers TO solve QUSB_BULK DOWNLOAD
3- You need to disable signature drivers (Windows)
Install manually , updating Qusb_BULK like the image
Here How to install .INF drivers (IN GENERAL)
3- In Qfil You import all files like this
3.1 ONLY select Rawprogram 0 to 3
IF you select the umparsed you will have filehose error.
4. Select Patchs 0 to 4 ... and flash
Who has att stock Rom? Tell me where to download. How to restore the att version?
about device
(bootloader) Model:H1A1000
(bootloader) version-baseband:MPSS.AT.2.0.c4-00933-8998
(bootloader) display-id:H1A1000.007ho.01.01.01r.230
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot getvar current-slot
vendor.img from firmware H1A1000.082ho.01.00.10r.118_userdebug_fastboot
userdata.img from firmware H1A1000.082ho.01.00.10r.118_userdebug_fastboot
I installed TWRP-3.5.0_9-0-V2-Hydrogenone.img
The touch did not work
I took the mouse and OTG and unlocked the screen
Made a backup att firmware
got a bootloop
I mixed up the firmware and vendor in the phone
got a phone with a non-working Wi-Fi
I mixed Boot.img, System.img and Vendor.img from rundom firmware and finaly start the wi-fi.
To launch Wi-Fi, I sewed TWRP-3.5.0_9-0-V2-hydrogenone.img and restored the Vendor section from ATT
then
fastboot erase system_b
fastboot erase vendor_b
fastboot erase userdata
fastboot flash -S 100M system_b PixelExperience_ARM64AB-10.0-20200118-2138-GSI.img
fastboot flash -S 100M vendor_b vendor_118.img
fastboot flash userdata userdata.img
fastboot flash boot magisk_patched_9.pkq1.190118.001_118.img
fastboot rebot
Wi-Fi turned on. The camera works. SIM works
repeated everything for Slot a
bugs:
then phone is off and charging screen light is on.
KlutchApex said:
RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
I FLASH BUT STUCK ON LOGO
EDL FLASH Waiting for HS-USB QDLoader 9008... COM43
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:4096] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist [ext4:32 MiB]->persist [8]... OK 1.102s
Writing system.img [sparse:3.49 GiB]->system_a... OK 152.018s
Writing vendor.img [sparse:565.78 MiB]->vendor_a... OK 21.497s
Writing userdata.img [sparse:5.49 MiB]->userdata... OK 1.222s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:2.56 MiB]->xbl_a... OK 0.164s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.105s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing xbl.elf [elf:2.56 MiB]->xbl_b... OK 0.167s
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.106s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.054s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch3.xml... OK
Processing LUN4 - rawprogram_unsparse0.xml
Writing persist [ext4:32 MiB]->persist [8]... OK 0.901s
system_a->system_1.img is not exists!!!
system_a->system_2.img is not exists!!!
system_a->system_3.img is not exists!!!
system_a->system_4.img is not exists!!!
system_a->system_5.img is not exists!!!
system_a->system_6.img is not exists!!!
system_a->system_7.img is not exists!!!
system_a->system_8.img is not exists!!!
system_a->system_9.img is not exists!!!
system_a->system_10.img is not exists!!!
system_a->system_11.img is not exists!!!
system_a->system_12.img is not exists!!!
system_a->system_13.img is not exists!!!
vendor_a->vendor_1.img is not exists!!!
vendor_a->vendor_2.img is not exists!!!
vendor_a->vendor_3.img is not exists!!!
vendor_a->vendor_4.img is not exists!!!
vendor_a->vendor_5.img is not exists!!!
vendor_a->vendor_6.img is not exists!!!
vendor_a->vendor_7.img is not exists!!!
vendor_a->vendor_8.img is not exists!!!
userdata->userdata_1.img is not exists!!!
userdata->userdata_2.img is not exists!!!
userdata->userdata_3.img is not exists!!!
userdata->userdata_4.img is not exists!!!
userdata->userdata_5.img is not exists!!!
userdata->userdata_6.img is not exists!!!
userdata->userdata_7.img is not exists!!!
userdata->userdata_8.img is not exists!!!
userdata->userdata_9.img is not exists!!!
userdata->userdata_10.img is not exists!!!
userdata->userdata_11.img is not exists!!!
userdata->userdata_12.img is not exists!!!
userdata->userdata_13.img is not exists!!!
userdata->userdata_14.img is not exists!!!
userdata->userdata_15.img is not exists!!!
userdata->userdata_16.img is not exists!!!
userdata->userdata_17.img is not exists!!!
userdata->userdata_18.img is not exists!!!
userdata->userdata_19.img is not exists!!!
userdata->userdata_20.img is not exists!!!
userdata->userdata_21.img is not exists!!!
userdata->userdata_22.img is not exists!!!
userdata->userdata_23.img is not exists!!!
userdata->userdata_24.img is not exists!!!
userdata->userdata_25.img is not exists!!!
userdata->userdata_26.img is not exists!!!
userdata->userdata_27.img is not exists!!!
userdata->userdata_28.img is not exists!!!
userdata->userdata_29.img is not exists!!!
userdata->userdata_30.img is not exists!!!
userdata->userdata_31.img is not exists!!!
userdata->userdata_32.img is not exists!!!
userdata->userdata_33.img is not exists!!!
userdata->userdata_34.img is not exists!!!
userdata->userdata_35.img is not exists!!!
userdata->userdata_36.img is not exists!!!
userdata->userdata_37.img is not exists!!!
userdata->userdata_38.img is not exists!!!
userdata->userdata_39.img is not exists!!!
userdata->userdata_40.img is not exists!!!
userdata->userdata_41.img is not exists!!!
userdata->userdata_42.img is not exists!!!
userdata->userdata_43.img is not exists!!!
userdata->userdata_44.img is not exists!!!
userdata->userdata_45.img is not exists!!!
userdata->userdata_46.img is not exists!!!
userdata->userdata_47.img is not exists!!!
userdata->userdata_48.img is not exists!!!
userdata->userdata_49.img is not exists!!!
userdata->userdata_50.img is not exists!!!
userdata->userdata_51.img is not exists!!!
userdata->userdata_52.img is not exists!!!
userdata->userdata_53.img is not exists!!!
userdata->userdata_54.img is not exists!!!
userdata->userdata_55.img is not exists!!!
userdata->userdata_56.img is not exists!!!
userdata->userdata_57.img is not exists!!!
userdata->userdata_58.img is not exists!!!
userdata->userdata_59.img is not exists!!!
userdata->userdata_60.img is not exists!!!
userdata->userdata_61.img is not exists!!!
userdata->userdata_62.img is not exists!!!
userdata->userdata_63.img is not exists!!!
userdata->userdata_64.img is not exists!!!
userdata->userdata_65.img is not exists!!!
userdata->userdata_66.img is not exists!!!
userdata->userdata_67.img is not exists!!!
userdata->userdata_68.img is not exists!!!
userdata->userdata_69.img is not exists!!!
userdata->userdata_70.img is not exists!!!
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.054s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Applying patch4.xml... OK
Processing LUN5 - rawprogram_unsparse4.xml
Writing rpm.mbn [elf:228.19 KiB]->rpm_a... OK 0.107s
Writing tz.mbn [elf:1.82 MiB]->tz_a... OK 0.147s
Writing hyp.mbn [elf:264 KiB]->hyp_a... OK 0.109s
Writing pmic.elf [elf:49.94 KiB]->pmic_a... OK 0.104s
Writing NON-HLOS.bin [fat:104.05 MiB]->modem_a... OK 3.764s
Writing BTFM.bin [fat:412 KiB]->bluetooth_a... OK 0.114s
Writing mdtpsecapp.mbn [elf:1.03 MiB]->mdtpsecapp_a... OK 0.128s
Writing mdtp.img [raw:16.98 MiB]->mdtp_a... OK 1.039s
Writing abl.elf [elf:148 KiB]->abl_a... OK 0.098s
Writing keymaster64.mbn [elf:308.66 KiB]->keymaster_a... OK 0.078s
Writing boot.img [kernel:44.34 MiB]->boot_a... OK 1.300s
Writing cmnlib.mbn [elf:221.32 KiB]->cmnlib_a... OK 0.108s
Writing cmnlib64.mbn [elf:292.71 KiB]->cmnlib64_a... OK 0.111s
Writing devcfg.mbn [elf:56.84 KiB]->devcfg_a... OK 0.104s
Writing adspso.bin [ext4:16 MiB]->dsp_a... OK 0.603s
Writing rpm.mbn [elf:228.19 KiB]->rpm_b... OK 0.110s
Writing tz.mbn [elf:1.82 MiB]->tz_b... OK 0.247s
Writing hyp.mbn [elf:264 KiB]->hyp_b... OK 0.110s
Writing pmic.elf [elf:49.94 KiB]->pmic_b... OK 0.105s
Writing NON-HLOS.bin [fat:104.05 MiB]->modem_b... OK 2.989s
Writing BTFM.bin [fat:412 KiB]->bluetooth_b... OK 0.113s
Writing mdtpsecapp.mbn [elf:1.03 MiB]->mdtpsecapp_b... OK 0.128s
Writing mdtp.img [raw:16.98 MiB]->mdtp_b... OK 0.677s
Writing abl.elf [elf:148 KiB]->abl_b... OK 0.108s
Writing keymaster64.mbn [elf:308.66 KiB]->keymaster_b... OK 0.111s
Writing boot.img [kernel:44.34 MiB]->boot_b... OK 2.009s
Writing cmnlib.mbn [elf:221.32 KiB]->cmnlib_b... OK 0.110s
Writing cmnlib64.mbn [elf:292.71 KiB]->cmnlib64_b... OK 0.109s
Writing devcfg.mbn [elf:56.84 KiB]->devcfg_b... OK 0.105s
Writing adspso.bin [ext4:16 MiB]->dsp_b... OK 0.493s
Writing splash.img [raw:10.56 MiB]->splash... OK 0.389s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.104s
Writing storsec.mbn [elf:48.02 KiB]->storsec... OK 0.104s
otafs->otafs_ufs_2gb_1.img is not exists!!!
otafs->otafs_ufs_2gb_2.img is not exists!!!
otafs->otafs_ufs_2gb_3.img is not exists!!!
otafs->otafs_ufs_2gb_4.img is not exists!!!
otafs->otafs_ufs_2gb_5.img is not exists!!!
otafs->otafs_ufs_2gb_6.img is not exists!!!
otafs->otafs_ufs_2gb_7.img is not exists!!!
otafs->otafs_ufs_2gb_8.img is not exists!!!
otafs->otafs_ufs_2gb_9.img is not exists!!!
otafs->otafs_ufs_2gb_10.img is not exists!!!
otafs->otafs_ufs_2gb_11.img is not exists!!!
otafs->otafs_ufs_2gb_12.img is not exists!!!
otafs->otafs_ufs_2gb_13.img is not exists!!!
otafs->otafs_ufs_2gb_14.img is not exists!!!
otafs->otafs_ufs_2gb_15.img is not exists!!!
otafs->otafs_ufs_2gb_16.img is not exists!!!
otafs->otafs_ufs_2gb_17.img is not exists!!!
otafs->otafs_ufs_2gb_18.img is not exists!!!
otafs->otafs_ufs_2gb_19.img is not exists!!!
otafs->otafs_ufs_2gb_20.img is not exists!!!
otafs->otafs_ufs_2gb_21.img is not exists!!!
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.104s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.104s
Rebooting... OK
Total transfer : 4.43 GiB
Transfer Speed : 23.36 MiB/s
UNLOCKTOOL 2022.10.05.2
Elapsed time : 3 minutes 48 seconds
KlutchApex said:
RED HYDROGEN ONE
Android 9 ROM packageATTENTION: THIS PROCESS WILL WIPE ALL OF YOUR USER DATA. PROCEED AT YOUR OWN RISK. I am not responsible for your phone.
christian.farmerf provided an updated link to the ROM package. Thank you!The file below has the ADBWinAPI.dll file. https://mega.nz/file/D8UhUITA#fvFHE0tRHaFHqKZW5ikPokp026fhqn0UzOHZx2fzuDA
(Original Link)Here is the original link provided by member @114514Beast.
DOWNLOAD (GOOGLE DRIVE)
source
https://drive.google.com/file/d/1FvuqfC28e7tmVGjGDgCZixVpATKtT2sB/view?usp=sharing
Click to expand...
Click to collapse
HOW I RESTORD MY PHONE
Related
Hey all, yesterday I only flashed 4.4.4 Kitkat in my phone (previously running custom 5.1.1).
(PS also received 3 5.0.2 updates as I was on soak test)
Anyways, the problem I am facing is that:
MY logo.bin is getting flashed, but still showing "Warning bootloader unlocked"
WHY?
I must mention here that I didnot flash gpt.bin and motoboot.img..... Do these files have anything to do with it?
Please help.
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
[/B]
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
UjRock said:
[/B]
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
Click to expand...
Click to collapse
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response Faiz, please find the screenshot of the errors when I try to flash from SD card and the mfastboot cmd.
These are the commands in the install ROM .bat file;
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
pause
mfastboot.exe reboot
This is what i get in mfastboot cm whe i run the istall ROM .bat file;
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.491s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash motoboot motobo
ot.img
target max-sparse-size: 256MB
error: cannot load 'motoboot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.077s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
error: cannot load 'boot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash recovery recove
ry.img
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
error: cannot load 'NON-HLOS.bin': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.039s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.028s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.094s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.135s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>pause
Press any key to continue . . .
Screenshot of SD card flash;
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Faiz Syed said:
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I tried, but it failed nevertheless.
This is what it returned:
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot devices
ZX1B33CH8Z fastboot
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>Fastboot erase system -w
'Fastboot' is not recognized as an internal or external command,
operable program or batch file.
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mFastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.930s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>
The problem is I do not have a proper service centre here and as per customer experiences, they have been asked to replace the motherboard. Now that is as goo as buying a new handset. Please Faiz, let me know if this is solvable or I have to simply shut down the handset and buy a new one?
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thank you very much Faiz, you were helpful in providing quick answers. I very much appreciate your time and effort. I'll buy a new phone as that seems to be a more doable option here.
You have a good day ahead!
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I'll try relocking.
IMAGE ATTACHMENTS:
i cudnt attach image pls mail at:[email protected]
One day while i was using my phone i kept it away for sme time wen i took it back i found that the phone is off and when i tried to switch it on i found the phone it stucked on the warning bootloader screen(i hav unlocked the bootloader and rooted the phone 1 month ago)i found that the phone is bricked i entered the bootloader and selected recovery(i hav been using twrp recovery)wen i tried to factory reset the phone in twrp it gives an error message:
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/persist'
E:Unable to mount '/firmware'
E:Unable to mount '/fsg'
E:Unable to mount '/pda'
E:Unable to mount '/storage'
(i hav attached an image regarding the error)
so i googled and found that i can use command prompt to flash stock rom i tried all the steps carefully.
i found that my device is detected by the CMD
wen i give mfastboot.exe devices the cmd shows my device name
but no other command is successfull each and every command fails except the one to display the devices and the command to reboot the phone works(the phone responds to every command pls check the attached images)
pls help me.
The commands that i hav used in Command promt are:
mfastboot.exe devices
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.bin
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system
system.img_sparsechunk.0
mfastboot.exe flash system
system.img_sparsechunk.1
mfastboot.exe flash system
system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
can you provide me some more info? Send me a pic of your bootloader screen, tell me your phone model no. , firmware/rom which you were using, latest logs, tweaks you had done on your phone like Xposed modules, apps with root access that you had installed, apps2sd or link2sd or similar memory affecting tweaks. I own a moto E xt1022 and i have flashed it a lot. I wld try to help to every possible extnt. Just give me the needed info. if you are unable to attach files, pm me
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.bin
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system
system.img_sparsechunk.0
mfastboot.exe flash system
system.img_sparsechunk.1
mfastboot.exe flash system
system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Click to expand...
Click to collapse
what was the output in cmd after these commands?
sziraqui said:
can you provide me some more info? Send me a pic of your bootloader screen, tell me your phone model no. , firmware/rom which you were using, latest logs, tweaks you had done on your phone like Xposed modules, apps with root access that you had installed, apps2sd or link2sd or similar memory affecting tweaks. I own a moto E xt1022 and i have flashed it a lot. I wld try to help to every possible extnt. Just give me the needed info. if you are unable to attach files, pm me
Click to expand...
Click to collapse
xda is preventing me from attaching images as im a new user can u find some way so that i can send u those images,i hav rooted the phone but was not using any app that need root access,i hav been using twrp as my recovery pls mail me at [email protected] so that i can sent images personally
sziraqui said:
what was the output in cmd after these commands?
Click to expand...
Click to collapse
MY PHONE MODEL IS XT1022
OUTPUT IN CMD
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>stock.bat
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.563s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash motoboot motoboo
t.bin
target max-sparse-size: 256MB
error: cannot load 'motoboot.bin': No error
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.063s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.012s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.354s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 6.031s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.028s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.0
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.1
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.2
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.491s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 6.510s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.015s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.021s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.109s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.125s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.011s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.019s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe reboot
rebooting...
finished. total time: 0.003s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>
dont use stock.bat file
Download the factory images (5.1 rom files) from the below link
follow these instructions to flash stock 5.1 rom files (dont flash older 4.4.x, motoboot of old version may fail to flash)
FLASH IN THE GIVEN SEQUENCE, FIRST FLASH GPT.BIN, IF OUTPUT IS 'FAILED' FLASH THE GTP.BIN THREE MORE TIMES, IF YOU GET 'SUCCESS' MESSAGE IN CMD, FLASH THE OTHER FILE, DONT HURRY, GIVE EACH COMMAND AFTER YOU GET 'SUCCESS' MSG ON CMD FOR PREVIOUS FILES
sziraqui said:
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
Click to expand...
Click to collapse
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
Also, flashing will fail if your battery is low
---------- Post added at 12:08 PM ---------- Previous post was at 11:52 AM ----------
email me a pic of your bootloader screen
sziraqui said:
dont use stock.bat file
Download the factory images (5.1 rom files) from the below link
follow these instructions to flash stock 5.1 rom files (dont flash older 4.4.x, motoboot of old version may fail to flash)
FLASH IN THE GIVEN SEQUENCE, FIRST FLASH GPT.BIN, IF OUTPUT IS 'FAILED' FLASH THE GTP.BIN THREE MORE TIMES, IF YOU GET 'SUCCESS' MESSAGE IN CMD, FLASH THE OTHER FILE, DONT HURRY, GIVE EACH COMMAND AFTER YOU GET 'SUCCESS' MSG ON CMD FOR PREVIOUS FILES
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
Also, flashing will fail if your battery is low
---------- Post added at 12:08 PM ---------- Previous post was at 11:52 AM ----------
email me a pic of your bootloader screen
Click to expand...
Click to collapse
bro as u said i was using 5.1 and wen my phone got bricked i tried to go back to stock 4.4 using cmd
now wen i tried to flash 5.1 using the above files the bootloader failed
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.480s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.044s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.559s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>
try this
Code:
mfastboot erase system
mfastboot erase gpt
mfastboot flash gpt gpt.bin
if you get success msg after flashing gpt, proceed with my first post
sziraqui said:
try this
Code:
mfastboot erase system
mfastboot erase gpt
mfastboot flash gpt gpt.bin
if you get success msg after flashing gtp, proceed with my first post
Click to expand...
Click to collapse
i didnt get success message
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot erase gpt
erasing 'gpt'...
(bootloader) Invalid partition name gpt
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash gpt gpt.bin
target max-sparse-size: 256MB
sending 'gpt' (32 KB)...
OKAY [ 0.018s]
writing 'gpt'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>
just to get rid of the 'permission denied' and 'pre flash validation' errors, try this
Code:
fastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
this should hopefully bring your phone back to 'out of the box' state
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
please clean your adb_fastboot folder. delete all flash files, and then copy the files from XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip TO ENSURE you are flashing the correct files, dont show laziness towards this
sziraqui said:
just to get rid of the 'permission denied' and 'pre flash validation' errors, try this
Code:
fastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
this should hopefully bring your phone back to 'out of the box' state
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
please clean your adb_fastboot folder. delete all flash files, and then copy the files from XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip TO ENSURE you are flashing the correct files, dont show laziness towards this
Click to expand...
Click to collapse
again fail
C:\Users\ANANTHU RAJ\Desktop\5.1\new>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot oem lock begin
...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
try flashing philz recovery .img via fastboot
place CWM_PhilZ_Touch_6.57.9.img (do not rename it) in your fastboot folder and flash it with this command
fastboot flash recovery CWM_PhilZ_Touch_6.57.9.img
then reboot your phone to recovery mode. If it reboots to philz recovery, then your emmc is alright, but if it doesnt your emmc has become either 'read only' or it is corrupted.
if its read only, it can be reset using JTAG, (give your phone to a professional for doing this)
sziraqui said:
try flashing philz recovery .img via fastboot
place CWM_PhilZ_Touch_6.57.9.img (do not rename it) in your fastboot folder and flash it with this command
fastboot flash recovery CWM_PhilZ_Touch_6.57.9.img
then reboot your phone to recovery mode. If it reboots to philz recovery, then your emmc is alright, but if it doesnt your emmc has become either 'read only' or it is corrupted.
if its read only, it can be reset using JTAG, (give your phone to a professional for doing this)
Click to expand...
Click to collapse
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash revovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'revovery' (8824 KB)...
OKAY [ 0.313s]
writing 'revovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.313s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
ananthu0000 said:
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash revovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'revovery' (8824 KB)...
OKAY [ 0.313s]
writing 'revovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.313s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
Click to expand...
Click to collapse
dude its 'recovery' not 'revovery'
sziraqui said:
bro its 'recovery' not 'revovery'
Click to expand...
Click to collapse
bro again failed
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash recovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'recovery' (8824 KB)...
OKAY [ 0.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.307s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
you need to send your phone for JTAG Flashing, just approach a local mobile repairer.
it seems you are not the only person facing emmc failure, your phone's emmc and dram are by 'micron' and 'elpida' respectively. I also have xt1022 but with 'hynix' emmc and dram and my phone is still working well after several flashes.
Just by searching 'micron elpida moto e' on google you will find many other people like you, i would conclude this brands emmc is faulty, thats why many moto e users are facing emmc failure
here are few guys like you-
http://forum.gsmhosting.com/vbb/f783/moto-e-xt1022-partition-error-possible-fix-2007708/
http://forum.gsmhosting.com/vbb/f78...2-jamesjerss-1965102/index6.html#post11215151
sziraqui said:
it seems you are not the only person facing emmc failure, your phone's emmc and dram are by 'micron' and 'elpida' respectively. I also have xt1022 but with 'hynix' emmc and dram and my phone is still working well after several flashes.
Just by searching 'micron elpida moto e' on google you will find many other people like you, i would conclude this brands emmc is faulty, thats why many moto e users are facing emmc failure
here are few guys like you-
http://forum.gsmhosting.com/vbb/f783/moto-e-xt1022-partition-error-possible-fix-2007708/
http://forum.gsmhosting.com/vbb/f78...2-jamesjerss-1965102/index6.html#post11215151
Click to expand...
Click to collapse
wat to do now..?? should i take it for jtag flashing.?? if so where should i take it to.?
look if ur emmc can be recovered by a reset (using jtag) then your phone would be fine otherwise its bricked forever. So i would say yes u should take it for jtag flashing, just give it to any reliable mobile repairer and tell him its not booting up, all mobile repairers generally flash using different boxes and not through fastboot. So you really dont need to mention what you have done on your phone.
Facing same problem
ananthu0000 said:
again fail
C:\Users\ANANTHU RAJ\Desktop\5.1\new>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot oem lock begin
...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
Click to expand...
Click to collapse
Someone please help, I'm facing the same problem
I know that there are a lot of threads regarding similar issues, unfortunately I still could not figure out how to solve my problem.
The Problem
The phone is stuck on Logo.
I have access to fastboot and can flash recovery, unfortunately noting happens afterwards.
Volume Down + Power does not boot into recovery.
ADB not accessible
Code:
./fastboot --version
fastboot version 3db08f2c6889-android
Code:
./fastboot flash recovery OPX_MM_recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.486s]
writing 'recovery'...
OKAY [ 0.318s]
finished. total time: 0.805s
Code:
./fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (11128 KB)...
OKAY [ 0.350s]
writing 'boot'...
OKAY [ 0.238s]
finished. total time: 0.588s
Code:
./fastboot oem device-info
< waiting for any device >
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.008s
EDIT:
Found the OnePlus_14_A.04.rar in the Mega Unbrick Guide for A Hard Bricked OnePlus X this finaly contains the files I needed to flash everything via fastboot.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
hi... can you help me. my oneplus x stuck on oneplus logo everytime i try to get into recovery mode but the phone is working perfectly. -sorry for my bad english-
elioo said:
hi... can you help me. my oneplus x stuck on oneplus logo everytime i try to get into recovery mode but the phone is working perfectly. -sorry for my bad english-
Click to expand...
Click to collapse
just flash recovery from Rasher app. Download it from Play Store
Hi
These are the steps that were followed to make the global ROM work for you...
Please follow the instructions step by step
Try these steps at your own risk and I am not responsible for losing your phone or data
1- You must open the bootloader with this link .
2- Download the global ROM A.09 ( img) file with this link .
3- Download the INDIN ROM A.14 ( img) file with this link . Thanks to ( MrVeverything )
4- Extract the img files ( 44 items) img .
5- Download the adb file and install it and it will be rooted on disk c
6- Put the files extracted in step 3 and put them in the adb folder
7- Boot your Phone into Fastboot Mode
8- In the adb folder hold the SHIFT key and right-click on an empty spot inside the folder, then select the ‘Open PowerShell window here’ option.
9- Connect your device to the computer and follow the following commands :
.\fastboot devices
.\fastboot getvar all ........ ( This step is very important in order to know what is the path of solt a or b )
If it is solt b follow the following commands... Thank you very much to srsbsns89 . and hmdqa
Now follow the commands
Code:
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
.\fastboot reboot fastboot ...... ( you see phone after this command on recovery mod )
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cpucp cpucp.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash engineering_cdt engineering_cdt.img
.\fastboot flash featenabler featenabler.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash my_carrier my_carrier.img
.\fastboot flash my_company my_company.img
.\fastboot flash my_engineering my_engineering.img
.\fastboot flash my_heytap my_heytap.img
.\fastboot flash my_manifest my_manifest.img
.\fastboot flash my_preload my_preload.img
.\fastboot flash my_product my_product.img
.\fastboot flash my_region my_region.img
.\fastboot flash my_stock my_stock.img
.\fastboot flash odm odm.img
.\fastboot flash oplus_sec oplus_sec.img
.\fastboot flash oplusstanvbk oplusstanvbk.img
.\fastboot flash product product.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash qweslicstore qweslicstore.img
.\fastboot flash shrm shrm.img
.\fastboot flash splash splash.img
.\fastboot flash system system.img
.\fastboot flash system_ext system_ext.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash vendor vendor.img
.\fastboot flash vendor_boot vendor_boot.img
.\fastboot flash vm-bootsys vm-bootsys.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot -w
.\fastboot reboot
Now after completion, the phone will enter recovery mode and format and the global ROM will work with you
__________________________________________________________________________________________________________
How to fix “Device is not Play Protect certified” errorGet your Device ID. This is a 16-digit alphanumeric ID which you will need to certify your device with Google.
If you are still able to access the Play Store, install the Device ID app. If not, you can download the APK file here and install/sideload it on your device.
Go to Google’s Device Registration page here and paste/type your Google Services Framework ID on the Android ID box and tap Register.
After registering, you may enter your Google credentials on the Play Store. And you might as well reboot your device for good measure.
after that clean data for google play ... and reboot your device and done
Done ....
Did you unlock your bootloader?
Kenora_I said:
Did you unlock your bootloader?
Click to expand...
Click to collapse
yes
Try that.
Someone from this forum posted this in another thread.
The error is because the flash tool dosent support the GT yet.
Kenora_I said:
Try that.
Someone from this forum posted this in another thread.
Click to expand...
Click to collapse
i try this my device now is dead
lmacaber1 said:
i try this my device now is dead
Click to expand...
Click to collapse
Try flashing again. I succeeded in rooting after flashing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rakoncwy said:
Try flashing again. I succeeded in rooting after flashingView attachment 5364079
Click to expand...
Click to collapse
it is dead bro how can i flshing can you help me
lmacaber1 said:
it is dead bro how can i flshing can you help me
Click to expand...
Click to collapse
Can't even see the bootloader screen?
rakoncwy said:
Can't even see the bootloader screen?
Click to expand...
Click to collapse
No . just blak screen
lmacaber1 said:
No . just blak screen
Click to expand...
Click to collapse
Did you not unlock the bootloader?
rakoncwy said:
Did you not unlock the bootloader?
Click to expand...
Click to collapse
i unlock the bootloader befor my phone dead bro
lmacaber1 said:
i unlock the bootloader befor my phone dead bro
Click to expand...
Click to collapse
I did it before, but it turned on by pressing the power button for a long time.
rakoncwy said:
I did it before, but it turned on by pressing the power button for a long time.
Click to expand...
Click to collapse
Be patient and hold down the power button
rakoncwy said:
Be patient and hold down the power button
Click to expand...
Click to collapse
i try this and my phone put in download mod
lmacaber1 said:
i try this and my phone put in download mod
Click to expand...
Click to collapse
can you show me the picture?
rakoncwy said:
can you show me the picture?
Click to expand...
Click to collapse
just blak screen bro . but my pc is reading my phone
What is the pc reading it as.
Check device manager.
rakoncwy said:
Try flashing again. I succeeded in rooting after flashingView attachment 5364079
Click to expand...
Click to collapse
bro .. can you tell me how succeeded in rooting after flashing ...
Kenora_I said:
What is the pc reading it as.
Check device manager.
Click to expand...
Click to collapse
Qualcomm device
hello ,
My brother bought a new RMX2086 and wanted a custom rom on this it , i got it running without a problem for him everything was working fine till he connected the phone and he mistakenly formated the phone storage using UnlockTool using the "Snapdragon" tab.
I Tried reviving it using QFil and Unlocktool but it got no success and the phone only connect into EDL mode 9008.
i tried many firmwares but i got no luck.
but the other day i tried another RMX2086 firmware but the phone is hard hard bricked now , what i mean is the phone is not connecting to the pc anymore No 9008 no Fastboot no nothing it is dead , i read on this forum that SDM855+ has ram over it so i can't dig to ISP pinout.
anyone can help
i think i found the test point for this stupid phone ,
i flashed the same firmware that i used to revive this phone with but i got no EDL without shorting or fastboot , nothing , i have to short it to get 9008 port .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FOUND a new way to get 9008 port without shorting , just format data and the phone will connect every time you flash rawprogram0-8.xml ...
hey guys i tried 3 difrrent ofp , extracted them and flashed the firmware using Unlocktool's SDM module , with the help of prog_firehose.mbn from Unlocktool server. the one that came with the firmware does not work .
but the phone is still dead and with the usb plugged in it draws 0.25 to 0.30 Amps
here's the log..
Version:0.9 StartHTML:-1 EndHTML:-1 StartFragment:000128 EndFragment:017079 SourceURL:file%3a%2f%2f
EDL FLASHSelected Model : Realme X3 SuperZoom
Code Name : RMX2086
Operation : Auth Flash
Authenticating... OK
Retrieving data... OK [291.56 KiB]
Initializing data... OK
Waiting for HS-USB QDLoader 9008... COM7
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:0] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist.img [ext4:32 MiB]->persist... OK 0.815s
Writing custom.img [sparse:4.12 MiB]->custom... OK 0.219s
Writing cache.img [sparse:68.17 KiB]->cache... OK 0.107s
Writing metadata.img [sparse:44.07 KiB]->metadata... OK 0.103s
super->super.img is not exists!!!
Writing super.0.3743af72.img [sparse:3.9 GiB]->super... OK 100.494s
Writing super.1.ad242118.img [sparse:2.23 GiB]->super... OK 59.572s
Writing super.2.ad8e3c51.img [sparse:1.01 GiB]->super... OK 26.933s
Writing userdata.img [sparse:345.32 MiB]->userdata... OK 9.409s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:3.04 MiB]->xbl... OK 0.196s
Writing xbl_config.elf [elf:120.66 KiB]->xbl_config... OK 0.105s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.101s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing oppo19710.bin [raw:48 bytes]->cdt... OK 0.051s
Writing zeros_5sectors.bin [raw:20 KiB]->ddr... OK 0.102s
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.052s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch3.xml... OK
Processing LUN4 - rawprogram4.xml
Writing aop.mbn [elf:196.05 KiB]->aop... OK 0.106s
Writing tz.mbn [elf:3.04 MiB]->tz... OK 0.195s
Writing hyp.mbn [elf:476.88 KiB]->hyp... OK 0.148s
Writing NON-HLOS.bin [fat:140.21 MiB]->modem... OK 3.515s
Writing BTFM.bin [fat:860 KiB]->bluetooth... OK 0.126s
Writing abl.elf [elf:160 KiB]->abl... OK 0.106s
Writing dspso.bin [ext4:64 MiB]->dsp... OK 1.689s
Writing km4.mbn [elf:253.03 KiB]->keymaster... OK 0.108s
Writing boot.img [kernel:96 MiB]->boot... OK 2.368s
Writing cmnlib.mbn [elf:385.75 KiB]->cmnlib... OK 0.113s
Writing cmnlib64.mbn [elf:503.61 KiB]->cmnlib64... OK 0.115s
Writing devcfg.mbn [elf:52.79 KiB]->devcfg... OK 0.103s
Writing qupv3fw.elf [elf:69.07 KiB]->qupfw... OK 0.103s
Writing vbmeta.img [raw:8 KiB]->vbmeta... OK 0.101s
Writing vbmeta_system.img [raw:4 KiB]->vbmeta_system... OK 0.051s
Writing vbmeta_vendor.img [raw:4 KiB]->vbmeta_vendor... OK 0.051s
Writing dtbo.img [raw:24 MiB]->dtbo... OK 0.760s
Writing recovery.img [kernel:80 MiB]->recovery... OK 2.087s
Writing uefi_sec.mbn [elf:122.62 KiB]->uefisecapp... OK 0.104s
Writing imagefv.elf [elf:30.5 KiB]->imagefv... OK 0.102s
Writing dpAP.mbn [elf:13.19 KiB]->apdp... OK 0.101s
Writing dpMSA.mbn [elf:13.19 KiB]->msadp... OK 0.102s
Writing splash.img [raw:516.63 KiB]->splash... OK 0.117s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.102s
Writing storsec.mbn [elf:20.08 KiB]->storsec... OK 0.103s
Writing oppo_sec.mbn [elf:111.52 KiB]->oppo_sec... OK 0.104s
Writing multi_image.mbn [elf:13.3 KiB]->multiimgoem... OK 0.103s
Writing sec_smt.dat [raw:512 bytes]->secdata... OK 0.102s
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch4.xml... OK
Processing LUN5 - rawprogram5.xml
Writing dynamic_nvbk.bin [raw:10 MiB]->oppodycnvbk... OK 0.446s
Writing static_nvbk.bin [raw:10 MiB]->oppostanvbk... OK 0.434s
Writing emmc_fw.bin [raw:4 MiB]->opporeserve1... OK 0.349s
Writing opporeserve2.img [sparse:5.05 MiB]->opporeserve2... OK 0.398s
Writing DRIVER.ISO [raw:22.69 MiB]->DRIVER... OK 0.685s
Writing gpt_main5.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup5.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch5.xml... OK
Rebooting... OK
Total transfer : 7.97 GiB
Transfer Speed : 38.14 MiB/s
UNLOCKTOOL 2023.05.25.0
Elapsed time : 4 minutes 14 seconds
I did everything , i have UnlockTool.
i flashed all these roms :
RMX2086GDPR_11_F.06_2022101321340000.zip
RMX2086GDPR_11_C.13_2022051901570000.zip
RMX2086export_11_C.13_2022051901560000.zip
RMX2086PU_11_A.33_200625_33c9c266.zip
RMX2085export_11_C.13_2022051901550466_2.7z
RMX2081PU_11_A.53_210404_719ee533.zip
RMX2081EU_11_A.52_210404_719ee533.zip
RMX2081PU_11_A.53_210404_719ee533.zip
I extracted all of them , flashed them one by one , one time using Unlocktool , the 2nd time using Qfil after making some changes in Rawprogram3.xml "oppo19711.bin in cdt" and Rawprogram4.xml " sec_smt.dat in secdata ".
I edited Rawprogram.xml and got rid of those weird logs from Port_trace.txt " QFil logs "
I try to keep the battery voltage from being sucked by the phone " i keep it above 3.7V " , the phone always is drawing from 0.20 A to 0.32 A using my usb doctor.
Sometimes QFil won't flash unless i use prog_fwupdate.mbn , prog_firehose.mbn won't work .
The phone won't automatically connect to the pc ''9008" unless you short testpoint , and fix this "sometime" i use Format Storage from UnlockTool , then the phone will automatically get detected by the pc ''9008" eachtime you plug it or unplug it from the pc , it will get recognized without shorting the pins.
Before getting to this point , the phone was working fine i installed a custom rom and everything was ok. when i tried to root it i faced many problems of the phone not booting etc , i used to fix everything just by flashing "RMX2086GDPR_11_C.13_2022051901570000.zip" then the phone will boot without a problem , as a fresh start or something then i start ''rooting and installing custom roms etc ''.
Wow, it looks like you've tried a lot of stuff.
Maybe if you could find the UART interface it could give you some feedback on what's going wrong.
I was just wondering what's in those patch XMLs? (No, this has nothing to do with fixing this, I'm just wondering why they have to do that.)
Renate said:
Wow, it looks like you've tried a lot of stuff.
Maybe if you could find the UART interface it could give you some feedback on what's going wrong.
I was just wondering what's in those patch XMLs? (No, this has nothing to do with fixing this, I'm just wondering why they have to do that.)
Click to expand...
Click to collapse
yeah i don't i know why it had to do that , i mean i didn't find it on the internet or something , i just analyzed the xlm file because of the flash tool giving me errors '' sec.dat not exist " , so i had to dig and find a file named sec_smt.dat so i renamed it to sec.dat , the other one is '' oppo does not exist " so i found the file named " file_sector_offset="0" filename="oppo19696.bin" label="cdt ".
Today i downloaded 3 diff roms " RMX2085 " and mine is " RMX2086" i'm just trying everthing to revive this phone .
is there a paid tool or something like unlocktool " without a dongle " that is the best for Q9008 " SDM " phones ?
i need to try another flashtool , i mean i tried with QFIl and unlocktool only , MSMdownloadtool doesn't work , i installed cert for Codemeter enabled that bomb thing and it didn't start giving me error " packed does not exist " , and some username thing that i don't have and don't want to buy.
Deadmau73 said:
hey guys i tried 3 difrrent ofp , extracted them and flashed the firmware using Unlocktool's SDM module , with the help of prog_firehose.mbn from Unlocktool server. the one that came with the firmware does not work .
but the phone is still dead and with the usb plugged in it draws 0.25 to 0.30 Amps
here's the log..
Version:0.9 StartHTML:-1 EndHTML:-1 StartFragment:000128 EndFragment:017079 SourceURL:file%3a%2f%2f
EDL FLASHSelected Model : Realme X3 SuperZoom
Code Name : RMX2086
Operation : Auth Flash
Authenticating... OK
Retrieving data... OK [291.56 KiB]
Initializing data... OK
Waiting for HS-USB QDLoader 9008... COM7
Connecting to device... OK
Writing flash programmer... OK
Connecting to flash programmer... OK
Configuring device... OK
Setting boot LUN1... OK
Firehose config : UFS [Sector:4096] [Target:0] [Host:1048576]
Processing LUN0 - rawprogram0.xml
Writing persist.img [ext4:32 MiB]->persist... OK 0.815s
Writing custom.img [sparse:4.12 MiB]->custom... OK 0.219s
Writing cache.img [sparse:68.17 KiB]->cache... OK 0.107s
Writing metadata.img [sparse:44.07 KiB]->metadata... OK 0.103s
super->super.img is not exists!!!
Writing super.0.3743af72.img [sparse:3.9 GiB]->super... OK 100.494s
Writing super.1.ad242118.img [sparse:2.23 GiB]->super... OK 59.572s
Writing super.2.ad8e3c51.img [sparse:1.01 GiB]->super... OK 26.933s
Writing userdata.img [sparse:345.32 MiB]->userdata... OK 9.409s
Writing gpt_main0.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup0.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch0.xml... OK
Processing LUN1 - rawprogram1.xml
Writing xbl.elf [elf:3.04 MiB]->xbl... OK 0.196s
Writing xbl_config.elf [elf:120.66 KiB]->xbl_config... OK 0.105s
Writing gpt_main1.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup1.bin [raw:20 KiB]->BackupGPT... OK 0.101s
Applying patch1.xml... OK
Processing LUN2 - rawprogram2.xml
Writing gpt_main2.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup2.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch2.xml... OK
Processing LUN3 - rawprogram3.xml
Writing oppo19710.bin [raw:48 bytes]->cdt... OK 0.051s
Writing zeros_5sectors.bin [raw:20 KiB]->ddr... OK 0.102s
Writing gpt_main3.bin [raw:24 KiB]->PrimaryGPT... OK 0.052s
Writing gpt_backup3.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch3.xml... OK
Processing LUN4 - rawprogram4.xml
Writing aop.mbn [elf:196.05 KiB]->aop... OK 0.106s
Writing tz.mbn [elf:3.04 MiB]->tz... OK 0.195s
Writing hyp.mbn [elf:476.88 KiB]->hyp... OK 0.148s
Writing NON-HLOS.bin [fat:140.21 MiB]->modem... OK 3.515s
Writing BTFM.bin [fat:860 KiB]->bluetooth... OK 0.126s
Writing abl.elf [elf:160 KiB]->abl... OK 0.106s
Writing dspso.bin [ext4:64 MiB]->dsp... OK 1.689s
Writing km4.mbn [elf:253.03 KiB]->keymaster... OK 0.108s
Writing boot.img [kernel:96 MiB]->boot... OK 2.368s
Writing cmnlib.mbn [elf:385.75 KiB]->cmnlib... OK 0.113s
Writing cmnlib64.mbn [elf:503.61 KiB]->cmnlib64... OK 0.115s
Writing devcfg.mbn [elf:52.79 KiB]->devcfg... OK 0.103s
Writing qupv3fw.elf [elf:69.07 KiB]->qupfw... OK 0.103s
Writing vbmeta.img [raw:8 KiB]->vbmeta... OK 0.101s
Writing vbmeta_system.img [raw:4 KiB]->vbmeta_system... OK 0.051s
Writing vbmeta_vendor.img [raw:4 KiB]->vbmeta_vendor... OK 0.051s
Writing dtbo.img [raw:24 MiB]->dtbo... OK 0.760s
Writing recovery.img [kernel:80 MiB]->recovery... OK 2.087s
Writing uefi_sec.mbn [elf:122.62 KiB]->uefisecapp... OK 0.104s
Writing imagefv.elf [elf:30.5 KiB]->imagefv... OK 0.102s
Writing dpAP.mbn [elf:13.19 KiB]->apdp... OK 0.101s
Writing dpMSA.mbn [elf:13.19 KiB]->msadp... OK 0.102s
Writing splash.img [raw:516.63 KiB]->splash... OK 0.117s
Writing logfs_ufs_8mb.bin [fat:16 KiB]->logfs... OK 0.102s
Writing storsec.mbn [elf:20.08 KiB]->storsec... OK 0.103s
Writing oppo_sec.mbn [elf:111.52 KiB]->oppo_sec... OK 0.104s
Writing multi_image.mbn [elf:13.3 KiB]->multiimgoem... OK 0.103s
Writing sec_smt.dat [raw:512 bytes]->secdata... OK 0.102s
Writing gpt_main4.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup4.bin [raw:20 KiB]->BackupGPT... OK 0.103s
Applying patch4.xml... OK
Processing LUN5 - rawprogram5.xml
Writing dynamic_nvbk.bin [raw:10 MiB]->oppodycnvbk... OK 0.446s
Writing static_nvbk.bin [raw:10 MiB]->oppostanvbk... OK 0.434s
Writing emmc_fw.bin [raw:4 MiB]->opporeserve1... OK 0.349s
Writing opporeserve2.img [sparse:5.05 MiB]->opporeserve2... OK 0.398s
Writing DRIVER.ISO [raw:22.69 MiB]->DRIVER... OK 0.685s
Writing gpt_main5.bin [raw:24 KiB]->PrimaryGPT... OK 0.102s
Writing gpt_backup5.bin [raw:20 KiB]->BackupGPT... OK 0.102s
Applying patch5.xml... OK
Rebooting... OK
Total transfer : 7.97 GiB
Transfer Speed : 38.14 MiB/s
UNLOCKTOOL 2023.05.25.0
Elapsed time : 4 minutes 14 seconds
Click to expand...
Click to collapse
Hi, can you send me link to that tool?
maskalicz said:
Hi, can you send me link to that tool?
Click to expand...
Click to collapse
UnlockTool - Flash - Unlock Bootloader Xiaomi - Without Credit (Find My Phone ON)
unlocktool.net