Hi,
I am facing an issue while trying to restore the original ROM of my Realme 6 Pro phone. I was using ProjectElixir_3.0_RMX2061-13.0 ROM with OrangFox recovery and encountered an error while trying to install the original ROM (RMX2061_11_OTA_0110_all_gJfej4qyJpZN.ozip) through custom recovery. I tried multiple custom recoveries but faced the same error. I then downloaded the original (RMX2063GDPR_11_C.21_2021121403010308), which was in the format ofp and required MsmDownloadTool_V2.0.67 -Rcsm.exe and a key which I don't have. I used the script https://github.com/italorecife/OppoRealme-OFP-Flash to flash the ROM and it worked, but with some errors. Upon reboot, the phone displayed a completely black screen. I tried flashing custom recovery again, but the phone remained a black screen. I also tried flashing the original recovery but it didn't solve the issue.
I tried running `sudo fastboot reboot recovery`, which did a reboot but didn't log into the recovery and the screen remained black. The device was still appearing in fastboot though, giving me some hope. However, at 4am, I ran the following commands in an attempt to solve the problem:
sudo fastboot erase recovery
sudo fastboot erase userdata
sudo fastboot erase boot
sudo fastboot erase bootloader
sudo fastboot erase cache
sudo fastboot erase dtbo
sudo fastboot erase system # run with error
sudo fastboot erase system_ext # run with error
sudo fastboot erase vbmeta
After re-flashing recovery, boot, and vbmeta, I rebooted but the issue persisted and the phone no longer appeared in fastboot even after pressing the keys.
Is there a solution to this issue that I can try at home without going to the maintenance center? Any help would be greatly appreciated.
Related
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---
I just got a moto z play today and the first thing I did was try to root it so I could work with TitaniumBackup. After unlocking the bootloader and booting into TWRP (Not installing it, just booting) I realized that I forgot to transfer my files to the phone. Derp. So I tried to restart my phone and now the only thing that pops up is a message saying
"Your device has been unlocked and can't be trusted. To learn more visit Motorola.com/unlockbootloader. ID: bad key. Your device will boot in 5 seconds." Then it loops. Endlessly, with the exception of occasionally going a screen with a circle which says "Erasing". I really wanted to stay on the stock rom, is there any way to fix this without installing a custom recovery or ROM?
GIR385 said:
I just got a moto z play today and the first thing I did was try to root it so I could work with TitaniumBackup. After unlocking the bootloader and booting into TWRP (Not installing it, just booting) I realized that I forgot to transfer my files to the phone. Derp. So I tried to restart my phone and now the only thing that pops up is a message saying
"Your device has been unlocked and can't be trusted. To learn more visit Motorola.com/unlockbootloader. ID: bad key. Your device will boot in 5 seconds." Then it loops. Endlessly, with the exception of occasionally going a screen with a circle which says "Erasing". I really wanted to stay on the stock rom, is there any way to fix this without installing a custom recovery or ROM?
Click to expand...
Click to collapse
Mine did this once. I ended up having to do a full restore to stock to fix it. It did though. I believe I flashed the Addison firmware.
Sent from my XT1635-02 using Tapatalk
PhilD41 said:
Mine did this once. I ended up having to do a full restore to stock to fix it. It did though. I believe I flashed the Addison firmware.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
Thanks for your response, sorry for taking so long.
When you say you did a full restore using Addison firmware, how did you do it? I thought that the stock firmware wasn't available. Did you perform a factory data reset through the recovery?
GIR385 said:
Thanks for your response, sorry for taking so long.
When you say you did a full restore using Addison firmware, how did you do it? I thought that the stock firmware wasn't available. Did you perform a factory data reset through the recovery?
Click to expand...
Click to collapse
Sorry for the long delay in response. My family and I have been on vacation for the last two weeks. I pulled the files for the FW from one of the forums here. I would have to go back searching for which one. The process I used is posted below. It was a full rewrite of the device so yes, I lost all my user data. I did not do a factory reset after flashing though, just booted it up. I also keep the stock recovery. I use fastboot to boot into TWRP. When I need to. For these instructions you don't need recovery, just fastboot.
Code:
sudo fastboot getvar max-sparse-size
sudo fastboot oem fb_mode_set
sudo fastboot flash partition gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash system system.img_sparsechunk.6
sudo fastboot flash system system.img_sparsechunk.7
sudo fastboot flash system system.img_sparsechunk.8
sudo fastboot flash system system.img_sparsechunk.9
sudo fastboot flash oem oem.img
sudo fastboot erase carrier
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase DDR
sudo fastboot oem fb_mode_clear
The full file name for the FW I used is "ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" Not sure if that helps any or not.
Is your Pixel C stuck in a never-ending bootloop after flashing TWRP? Meaning, you're in TWRP, you choose Reboot ===> System and instead of booting into Android, it just keeps booting back into TWRP?
Please reference the following thread/post:
https://forum.xda-developers.com/showpost.php?p=78028560&postcount=27
Hope this helps someone.
BJ
I am very beginner in these tweakings. Incidently I have also asked a question with similar problem. With my Google Pixel C only booting into twrp. I think I need to install stock rom/ factory image from https://developers.google.com/android/images according to method provided there. Is it okay to flasing "flash-all.bat" with twrp already installed? Because now my concern is avoiding a 'hard bricked' device.
I ended my boot looping by installing stock rom (ryu-opm8.190605.005-factory-25b457f3) downloaded from google website. For me flash-all.bat or flash-all.sh were not working and throwing multiple kind of errors. I did two things. First I used this guide from xda to set PATH variable "How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC". Then I copied the .zip ROM file into "platform-tools" folder. Importantly I also extracted the .zip file within the .zip to same platform-tool folder. I manually installed each .img file one by one:
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
System now working fine with stock ROM and recovery.
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
I wanted to root my Google Pixel C. So as a first step I tried to installed twrp3.4.0-0 using the commands like fastboot flash recovery TWRP.img etc as described in many webpages. My pixel C restarted in twrp. When Reboot>System, i get message "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 secs ", then a Beep sound then Google logo for few seconds and then again twrp. Fastboot reboot command again bring my Pixel C to twrp. I think it has softbricked and I don't want to lose it . Can someone kindly help what I do to restore it with stock or install custom rom and root it. My ultimate goal is to run Linux on Pixel C. I was using Windows 10 before but now I am using Linux usb. Thanks
I ended my boot looping by installing stock rom (ryu-opm8.190605.005-factory-25b457f3) downloaded from google website. For me flash-all.bat or flash-all.sh were not working and throwing multiple kind of errors. I did two things. First I used this guide from xda to set PATH variable "How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC". Then I copied the .zip ROM file into "platform-tools" folder. Importantly I also extracted the .zip file within the .zip to same platform-tool folder. I manually installed each .img file one by one:
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
System now working fine with stock ROM and recovery.
On 1st screen of TWRP, do not swipe to modify system partition, choose the leftmost option to skip that step.
It still allows you to flash zips like Magisk, but system partition remains intact and bootable.
satelliteseeker said:
On 1st screen of TWRP, do not swipe to modify system partition, choose the leftmost option to skip that step.
It still allows you to flash zips like Magisk, but system partition remains intact and bootable.
Click to expand...
Click to collapse
If only I had see this before I installed TWRP