[Debrick] How to recover the hard bricked phone? - Amazon Fire Phone

Hello,
has anyone found a solution how to debrick the hard bricked FirePhone (64 GB)?
Currently the phone is recognized as QHSUSB_BULK -> Qualcomm HS-USB QDLoader 9008.
I tried the following tools for recovery:
ADB and FastBoot
- Cannot found device.
QFIL
QPST
- Which programmer can be used? (MPRG8974.mbn)
MiFlash
- Wrong programmer (error 0x8007000b).
BoardDiag
- How to prepare the partition.txt and extract the fw_image?
QBoot
- How to prepare the singleimage.bin?
QMSCT_DL_EMMC_TOOL
- Partitions are not recognized

Noone knows, Poke around and if you find anything, post here so we get to know too.

Little better situation for me ...
From TWRP Recovery, I restarted to system before flashing CM ROM and now I could not get to TWRP Recovery. Of course the phone is stuck at AMAZON logo while booting with no ROM installed. I could get into Fire's Recovery which is very constrained. I have just got access to ADB Sideload. Even when i tried to sideload the Fire OS Stock Rom, it failed at signature Verification. How do I toggle signature verification off when i give the command "adb sideload rom.zip" . Is anyone aware of any switch that I can append to toggle off the verification checking?? All Android Gurus out there... Kindly share your valuable suggestion... Thanks ..

manojvasanthram said:
Even when i tried to sideload the Fire OS Stock Rom, it failed at signature Verification. How do I toggle signature verification off when i give the command "adb sideload rom.zip"
Click to expand...
Click to collapse
The stock recovery doesn't support ZIP files, it's only for sideloading official BIN files released by Amazon.

Bingo Bronson said:
The stock recovery doesn't support ZIP files, it's only for sideloading official BIN files released by Amazon.
Click to expand...
Click to collapse
I did try the bin files. it threw up assert error for the device name "kodiak ,.. then i edited the relevant part of the script inside the bin file and rebuilt it and tried to side load, but the signature verification failed. Can you please let me know where can i get the signed versions of stock rom for Fire phone ?
Thanks

Any luck brother with this issue? We r on the same boat
BetaIQ said:
Hello,
has anyone found a solution how to debrick the hard bricked FirePhone (64 GB)?
Currently the phone is recognized as QHSUSB_BULK -> Qualcomm HS-USB QDLoader 9008.
I tried the following tools for recovery:
ADB and FastBoot
- Cannot found device.
QFIL
QPST
- Which programmer can be used? (MPRG8974.mbn)
MiFlash
- Wrong programmer (error 0x8007000b).
BoardDiag
- How to prepare the partition.txt and extract the fw_image?
QBoot
- How to prepare the singleimage.bin?
QMSCT_DL_EMMC_TOOL
- Partitions are not recognized
Click to expand...
Click to collapse
Ive read we need a system image of a running phone and flash it onto the bricked one to make it work, but I dont see any practical solution to this problem. I am a newbee, dont hae much knowledge. In experimenting, I have also deleted its eMMC paritions. Now, even the eMMC is not detected on the PC. Just connecting Qualcomm HS_USB QDLoad 9008 (Com4).

Related

hard brick lg g3 lollipop

I followed this guide http://forum.xda-developers.com/lg-...-root-bumpd-twrp-t3048845/page20#post59473703
excuse my English, then the procedure I did was download the KDZ for my terminal and I extracted as trained all the files in order to create the .img I took the super and I turned on the extension .zip .img I installed busybox and I launched the terminal, I gave the commands I came out recovery aborted and ended the procedure ... I wrote in the terminal and restart from there my terminal is not lit anymore. it does not go into download mode in recovery and it is not recognized by pc me qualcomm hs-usb qdloader 9008 ...
I have a question about this: I currently have the stock 20H firmware(rooted). If I install this with the LG Tool, will I lose TWRP and root?
Later edit: Sorry, I misclicked and posted in the wrong thread. I hope a mod will notice and delete this post.
aitanoddl said:
I followed this guide http://forum.xda-developers.com/lg-...-root-bumpd-twrp-t3048845/page20#post59473703
excuse my English, then the procedure I did was download the KDZ for my terminal and I extracted as trained all the files in order to create the .img I took the super and I turned on the extension .zip .img I installed busybox and I launched the terminal, I gave the commands I came out recovery aborted and ended the procedure ... I wrote in the terminal and restart from there my terminal is not lit anymore. it does not go into download mode in recovery and it is not recognized by pc me qualcomm hs-usb qdloader 9008 ...
Click to expand...
Click to collapse
What happens if you do a restore with LG PC Suite?
Razertje said:
What happens if you do a restore with LG PC Suite?
Click to expand...
Click to collapse
no is not recognized in any way .... guys I have the phone locked in it does it in revovery downloadmode You come revive Solutions

System corrupted, laf removed, fastboot doesnt work, stock recovery is useless.

Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse
Did you ever find a fix for this?
No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.
i just had the same problem. any fixes?
flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others
That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.
Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.
Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.
I have same problem, no download mode, system corrupted and recovery is useless.
mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:
Thats exactly what i tried but didn't work because D851

Secure Booting Error! Cause: boot certification verify

Good day mate. My brick phone is F460S variant. I got this error when I tried to go back to Lollipop using Lg flash tool 2014, it got stuck on 5% and remove usb cable and start again, after that I got this error Secure Booting Error! Cause: boot certification verify.
No download mode
No recovery
anyone can help me please?:crying:
anyone?
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
西村大一 said:
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
Click to expand...
Click to collapse
What does QFUSE mean?
anmino said:
What does QFUSE mean?
Click to expand...
Click to collapse
I second you on this. I just uninstalled MultiROM and got the secure booting error. Depending on the ROM you have, find a bumped kernel and flash it. Most of the kernels on XDA are pre-bumped unless the developer states so. Boot into recovery, tutorials on the internet, then flash the kernel and voila.
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
HardStyl3r said:
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
Click to expand...
Click to collapse
Yes, no DOWNLOAD mode and RECOVERY mode.. Anyone have an idea how to fix this?
anyone?
Hello, i got the same probleme and i've trying a lot of things but not resolved..
My phone is a LG G3 Beat F470s..
Please help us..
Dowblnload adb and fastboot drivers
Download laf.img for your device
Download LG Drivers
Get you G3 to fastboot mode. Hold volume up and connect it to PC
Open fastboot and adb folder in PC, ctrl+shift+right click and open cmd. Type fastboot devices...if ur device is listen then proceed, if not u did not do something cotrectly...if yes just flash laf img to your G3 and voila
I remember me that I was in the same situation:
No TWRP, no download mode, so i have use in pat this thread:
https://forum.xda-developers.com/showthread.php?t=1752270
And an other that i haven't found again (xda thread), in some lines:
=> download the last img file from: https://eu.dl.twrp.me/d855/
=> no download mode available so no possibility to flash manually twrp file from an LG Flash Tool
==> so setup an adb connexion to the phone, cp command to copy the img file on the sdcard or where you want
=> command: "flash recovery twrp-2.8.x.x-xxx.img" (https://www.xda-developers.com/how-to-install-twrp/
=> if it's as worked, you could reboot manually in twrp, make again the partitions if needed and flash any ROM.

Moto g5s hard brick no fastboot only blinking notification light

Mine motog5s updated to stock fw and root uninstalled after it it hangs on boot screen. I flashed stock fw again with fastboot but after restart mobile didn't display anything not even vibrate just blinking notification when connect usb wire . how to unbrick only shows qualcomm hs dloader 9008 what to do, pls. reply.
You cannot log into fastboot mode?
qualcomm hs dloader 9008 = EDL mode, you should be able to restore with QFIL: https://forums.lenovo.com/t5/MOTO-E-1st-Gen/Moto-E-Not-Boot-Up/td-p/3231144 but it looks like motorola doesn't provide the files ... most likely you'll need a service center
Do not use QFIL. To unbrick, we need the blankflash file for G5S. And it is not on the Internet yet. Do not use the blankflash of any other models. Your best bet is to take the phone to a service center.
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Did you try holding the power down button and turning on the phone to enter bootloader?
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
ASHDCBZ said:
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
Click to expand...
Click to collapse
You downloaded the unlock key from Moto website by giving them your device serial number. That's how they know you unlocked bootloader. Service center won't help you. But fortunately, there is a way to revive your phone. But I'm not getting the blankflash file anywhere.
Tell me what exactly did you do to your phone.
Thank you,
Ok I just flahsed & tried stock roms, root & custom roms. Then I flashed stock rom of mine region firmware npp26.102.19 then motorola gave the updates to npp26.102.55-1 Dec. patch. Then next day new update came Feb patch npp26.102.55-4 just after it mobile started hanging & when restart it stuck on boot, not booting just stuck on boot animation. I tried TWRP recovery it said encrypted then I entered the unlock pin then it shows all the folders. Then I again fastboot npp26.102.19 to solve the issue but after flashing & restart it did not boot nor screen on no vibration tried several times but no response, when connect with pc or charger a white notification light blinking only & it detected as QHUSB_BULK something like that then I searched for it & install driver then shows as qualcomm dloader 9008.
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
ShattrdChain said:
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
Click to expand...
Click to collapse
Hmmmmmmmm
Please provide blankflash soon file I'll try.
there is no notification light on my g5s. what is blinking on yours?
Andrew Joseph said:
there is no notification light on my g5s. what is blinking on yours?
Click to expand...
Click to collapse
Next to front flash right side a white light is blinking. Try pressing power button then it will show.
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Andrew Joseph said:
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Click to expand...
Click to collapse
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
does this only happen when you root your phone?
Can someone Help Us?
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
brunovsc said:
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
Click to expand...
Click to collapse
Yes tried this & other blank flash it show only this-----
Failed identify board. Wrong package?
ERROR: error loading package
FAILED: qb_flash_singleimage()->error loading package
other tried this also----------
Found this can anyone try
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
qfil also not flashing sahara error.
I have tried this but there's an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
ASHDCBZ said:
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
Click to expand...
Click to collapse
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
brunovsc said:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Same error shows in Qfil.
Andrew Joseph said:
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
Click to expand...
Click to collapse
So is it not switch on or displaying anything.

Unbrick realme x

Hi it's me again
i've bicked my phone last week, it only shows the image of realme and then a text that says the boot/recovery image have been destroyed, the problem with this brick its THE BOOTLOADER ITS BLOCKED AND THE PHONE CANT START THE RECOVERY, so the options are pretty limited, plus my device is china version.
The things and tools that i've been trying are:
*ADB FASTBOOT (i know i already said that the bootloader it's blocked but i had to try)
*Qualcomm snapdragon flash tool QIFL
*Qualcomm premium tool
*XTM Inferno tool
*OPPO download tool
*MSMDownload tool
Yeah, i've tried a few things already (not too much to be honest), but with everyone theres a problem.
Adb dont recognice because its not in fastboot, QIFL needs a xml file but the roms don't have it, and i dont know how to program it, XTM inferno tool dont recognice the device, and oppo and msm download tool needs an account, if anyone knows what can i do now, please let me know, i'm a little bit sad cause i haven't made it to unbrick
So sad that you can't enter fastboot. It seems that means you can't send commands to your phone.
Recently, I saved my "soft brick" China version RMX. I also get "boot/recovery image have been destroyed" notification, but I can enter fastboot mode (power+Volume-), and my fastboot is unlocked. I used "fastboot flash recovery" cammand to flash TWRP and another command for vbmeta (https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556). However, the response in "Windows Command Prompt" is "Failed unknown error".
So I decided to power off and charge my phone. After power off, there is thunder icon, a symbol for charging in powe off state, on the screen. Sunddenly, the phone boot into TWRP automaticly. I connected it to my laptop at once and find TWRP MTP service works which means I can copy the 2.6 GB stock Color OS zip (RMX1901CN_flashable_A17.zip, https://forum.xda-developers.com/realme-x/how-to/guide-to-stock-rom-stock-recovery-t3974607
, https://sourceforge.net/projects/rmx1901/files/custom_recovery_StockROM_flashable_files/) to internal storage (/sdcard), and I installed it successfully, though there was "Unmount to mount storage" error when I wiped Data in TWRP.
Reboot to system succesfully and showed Color OS setting guide, which showed at the first time you turn on the phone. Recovery changed to oppo stock Recovery, but the unlocked fastboot mode didn't change.
I am not sure wether the link is useful for cracked MSMDownload tool :https://www.techoxygen.com/msm-download-tool/
00002972 said:
So sad that you can't enter fastboot. It seems that means you can't send commands to your phone.
Recently, I saved my "soft brick" China version RMX. I also get "boot/recovery image have been destroyed" notification, but I can enter fastboot mode (power+Volume-), and my fastboot is unlocked. I used "fastboot flash recovery" cammand to flash TWRP and another command for vbmeta (https://forum.xda-developers.com/re...very-unofficial-twrp-realme-x-stable-t3959556). However, the response in "Windows Command Prompt" is "Failed unknown error".
So I decided to power off and charge my phone. After power off, there is thunder icon, a symbol for charging in powe off state, on the screen. Sunddenly, the phone boot into TWRP automaticly. I connected it to my laptop at once and find TWRP MTP service works which means I can copy the 2.6 GB stock Color OS zip (RMX1901CN_flashable_A17.zip, https://forum.xda-developers.com/realme-x/how-to/guide-to-stock-rom-stock-recovery-t3974607
, https://sourceforge.net/projects/rmx1901/files/custom_recovery_StockROM_flashable_files/) to internal storage (/sdcard), and I installed it successfully, though there was "Unmount to mount storage" error when I wiped Data in TWRP.
Reboot to system succesfully and showed Color OS setting guide, which showed at the first time you turn on the phone. Recovery changed to oppo stock Recovery, but the unlocked fastboot mode didn't change.
I am not sure wether the link is useful for cracked MSMDownload tool :https://www.techoxygen.com/msm-download-tool/
Click to expand...
Click to collapse
Thank you very much, i will keep looking, and will see the tool u shared, any step forward i make i will post it, and thanks again
Flash official ofp format stock ROM in EDL mode might be helpful. The links offer ofp ROM, guide & password for download tool. An XDA post also mentioned this link. But I'm still confused about the difference between RMX1901 and RMX1901EX model. Some custom ROM is universal for India and China variant on XDA .
https://boycracked.com/2019/05/06/official-realme-x-rmx1901-stock-rom/
https://forum.xda-developers.com/realme-x/how-to/color-os-stock-rom-redmi-x-rmx1901-t3952399/page2
00002972 said:
Flash official ofp format stock ROM in EDL mode might be helpful. The links offer ofp ROM, guide & password for download tool. An XDA post also mentioned this link. But I'm still confused about the difference between RMX1901 and RMX1901EX model. Some custom ROM is universal for India and China variant on XDA .
https://boycracked.com/2019/05/06/official-realme-x-rmx1901-stock-rom/
https://forum.xda-developers.com/realme-x/how-to/color-os-stock-rom-redmi-x-rmx1901-t3952399/page2
Click to expand...
Click to collapse
i can´t see the username and password, its what i need to open the msm download tool, i already have downloaded the files
hello bro.
i was having custom recovery and i tried to relock bootloader and now my device is bricked.
i am not able to go in fastboot mode.
please help
imteyajch said:
hello bro.
i was having custom recovery and i tried to relock bootloader and now my device is bricked.
i am not able to go in fastboot mode.
please help
Click to expand...
Click to collapse
Y
Hi dude, at this time I have not found a way to do it without realme tech support, or remote flash tool.
This device needs a “permission” of realme servers to get flashed. If your device is India version you can ask to boy cracker staff, if your device is China version maybe combine file staff can help.
If you have the option of send it to realme tech support, you should take it
Irvinukis said:
Y
Hi dude, at this time I have not found a way to do it without realme tech support, or remote flash tool.
This device needs a “permission” of realme servers to get flashed. If your device is India version you can ask to boy cracker staff, if your device is China version maybe combine file staff can help.
If you have the option of send it to realme tech support, you should take it
Click to expand...
Click to collapse
Its indian version. please help i did many things. i cannot go to booloader and fastboot mode
Bro yesterday I got an update from reami I updated to android 11 my bootloader was not unlocked and update was failed no recovery stuck on logo i Tryed to flash with msm but still no responce its indian version 1901 any solution please ?
But I can't tried ufs

Categories

Resources