Related
Huawei recently shipped update B180.
They advised to unroot the phone first, but I have been stupid and updated with TWRP installed on the second recovery partition (e-recovery?) and the update failed.
My phone now won't boot. I can put it in fastboot/recovery mode and access TWRP, so I guess all I need is a stock ROM.
I cannot find anything useful for Honor 7 with Google, I would like a recent ROM (most recent I found is a B130).
I would also appreciate some advice on how to recover from this boot freeze.
Would flashing a stock ROM with TWRP be enough?
Thank you very much.
I'm kinda pissed since that phone is quite expensive.
You cannot flash a stock rom with TWRP.
You have to flash the stock recovery then a stock rom, using fastboot.
The more recent stock rom available is the B130, unfortunatly.
Have a look at my posts, I have done similar (although I had the normally recovery.img installed) you need to downgrade using the marshmallow downgrade ROM then to the full 121 or 130 ROM after putting the stock recovery back (for the version your phone was on before this happened I assume it was 170 if you were going to 180) once you are back on 130 you can then upgrade up to 180 through the usual process. I have done this a few times and it has been fine whilst experimenting with the device.
The current version of the phone appears to be burned in to it (I think curver.img is doing this inside the UPDATE.APP but I haven't found a way of flashing this file back to the phone to play around with downgrading without the MM downgrade ROM), this I think is what causes it to hang if it has a boot.img and recovery.img that does not match the version the phone thinks it is.
I am in the same boat with @rbuccia.
I can only access fastboot and recovery (twrp).
I also found that I must have something wrong with 3rdmodem because if i wipe form inside twrp I always get an error message on that partition.
Also I have a rom from Kangvip flashable with twrp but veven this has no effect.
I think that we cannot unbrick it without a completely and full stock rom but I think there is no one.
Any idea?
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
james194zt said:
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
Click to expand...
Click to collapse
Thanks for the tips, but
1. Where can i download the B180 full firmware?
2. I can't access the VOL+ VOL- POWer AKA updater mode, it just bootloops.
Thx :laugh:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
james194zt said:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
Click to expand...
Click to collapse
I must be blind, but i can only find the ota updates, not the full stock firmware :/
Thx tho, i'm starting to understand a bit better how it works and how i can fix it.
I'll just try to flash boot and recovery for B100 and B130 untill i cant make it work, for the system.app tho i can't take the B180 as i can't find it.
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
james194zt said:
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
Click to expand...
Click to collapse
Thx for the reply ! But that's what i said earlier, when i flash boot.img, system.img and recovery.img from the B130 update.app, the phone still bootloops.
I have access to the Huawei E-recovery if i do VOL+ POWER while the phone is plugged in the pc
I have access to the fastboot mode if i do VOL- POWER while the phone is plugged in he pc
I DON'T have access to the software mode upgrader if i do VOL+ VOL- POWER, no matter is the phone is plugged in or not
The phone still bootloops, plugged in or not.
:/
You need to flash boot.img and recovery.img from 180 and system.img from 130, sorry if that was not clear above! the boot loop is being caused because the boot.img doesn't match the version your phone thinks its on, if 180 doesn't work try the version before you upgraded i.e. 170 the system.img is just the android OS if you see HONOR glowing then you are booting system.img at that point but if it isn't glowing then you are still in the bootloader at that point so you need to sort out boot.img.
I've never been in 180, and as i said, i can't take the boot and recovery.img from the OTA update, i need a full stock firmware of B180 ! :/
Thx for the help tho.
I already tried to flash boot.img from B100 b121 and B130, and the phone still bootloops :/
http://forum.xda-developers.com/hon...dating-to-b180-fastboot-t3317249#post65420964
This fixed it!
Found this and it worked for me.
Download latest Official Full ROM from EMUI's site, HuaweiUpdateExtractor and adb / fastboot.
2. Unzip ROM and open UPDATE.APP with HuaweiUpdateExtractor.
3. Extract SYSTEM.img and RECOVERY.img (delete .header files that HuaweiUpdateExtractor generates you need only .img files) and put them in adb folder.
4. Boot in fastboot and conect to PC. (You can achieve this from TWRP to boot to bootloader, adb dosent work but fastboot will there is also key combination to get to bootloader/repair mode or what it is).
5. Open cmd.exe from adb folder and type (or copy-paste) the follow commands one by one:
Code:
fastboot devices
Code:
fastboot flash recovery RECOVERY.img
Code:
fastboot flash system SYSTEM.img
And finally where i had some trouble:
If you got no permissions try again or take usb cable off etc. Took me while to get back from same situtation. Few reboots to TWRP and to bootloader and USB replugging while in bootloader.
And for LINUX: i used split_updata.pl-master from github to extract the .APP/Firmware needed to sudo fastboot aswell.
Hiiiii guys
Please help me respected sir and other friends.
Anyone have twrp backup of stock rom ?
Because I want go back to stock rom and I have only twrp not pc please thanks in advance
Disregard
I used a payload extraction tool to open up the OTA file and then flashed each partition via fastboot manually (saw it in a oneplus thread) phone is currently at the boot screen which is much further than it was any time before this, going to give it a little more time before trying anything further as I did a factory reset before upgrading so it could just be first booting.
thoughtlesskyle said:
I messed up while trying to install the android 10 update, I have backups of my stock boot images but not my system paritionwas on MP2) my system partition is now wiped
I can only get to the bootloader but accessing anything else just results in a bootloop so I can't install the OTA updates, I do however still have a working fastboot.
does anyone have a backup of their paritions that I can flash via fastboot?
I also can't seem to boot twrp from fastboot anymore either
any help is appreciated
Click to expand...
Click to collapse
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
KM7 said:
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
Click to expand...
Click to collapse
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
Good to know that you managed to boot it. Hope things are working well for you.
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
22 sections.
Yes, all the partitions had to be flashed to run it.
Code:
fastboot flash xbl_config_a rom/xbl_config.img
fastboot flash xbl_a rom/xbl.img
fastboot flash vendor_a rom/vendor.img
fastboot flash vbmeta_a rom/vbmeta.img
fastboot flash uefisecapp_a rom/uefisecapp.img
fastboot flash tz_a rom/tz.img
fastboot flash system_a rom/system.img
fastboot flash qupfw_a rom/qupfw.img
fastboot flash modem_a rom/modem.img
fastboot flash keymaster_a rom/keymaster.img
fastboot flash imagefv_a rom/imagefv.img
fastboot flash hyp_a rom/hyp.img
fastboot flash dtbo_a rom/dtbo.img
fastboot flash dsp_a rom/dsp.img
fastboot flash devcfg_a rom/devcfg.img
fastboot flash custom_a rom/custom.img
fastboot flash cmnlib64_a rom/cmnlib64.img
fastboot flash cmnlib_a rom/cmnlib.img
fastboot flash boot_a rom/boot.img
fastboot flash bluetooth_a rom/bluetooth.img
fastboot flash aop_a rom/aop.img
fastboot flash abl_a rom/abl.img
All writing* [OK].
But having root on board this operation passes with the format userdata error.
In the flash writing* [FAILED].
Only by deleting hidden folders and files via the /data/directory... in internal storage, writing* [OK].
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
you should have flashed vbmeta.img so that you don't get in bootloop
You mean your phone wouldn't go into bootloader by "Vol. down button + power button" holding from power off state?
T59y9 said:
fastboot flash magisk_patched.img
Click to expand...
Click to collapse
Do you mean "fastboot flash recovery magisk_patched.img"??
the correct command is fastboot flash boot magisk_patched.img
Maybe he wrote fastboot flash magisk_patched .img
but I think it would have returned an error
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
Maybe the rom you downloaded and the base rom running on your device is not the same version, that may cause the error. {Mod edit}
@T59y9
Hi
did you solve in some way?
My realme 7 5G is not rooted.
Just arrived me friday, I udated to new firmware trought recovery. After the reboot did not woke up anymore.
Black screen. no realme logo. nothing.
tried all button combinations, nothing. no boot, no logo, recovery, no fastboot.
tried also with charger attached, with usb on PC.
Nothing...
Any idea to solve my problem?
thank you.
how did you unlock the bootloader?
in depth test app says my model does not support in-depth test
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
gannjunior said:
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
Click to expand...
Click to collapse
oh sorry
any idea how to solve?
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
same anyone know how to solve this pls :/
First you all. Say the Model Number. You talk about Realme 7/Pro or 5G...
This issues is fixable. Just need extra tools to bypass Google FRP and a factory images ROM versions. Fixed few devices with the same situation!
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
did you find soultion of this at now because i also have same problem?
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
martinbrettphilo said:
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
Click to expand...
Click to collapse
It'll be kinda hard. You're gonna have to find a stock ROM - not an OTA update - and you're gonna need to use python to extract the contents from the .OFP file. This should be it. https://firmwarefile.com/oppo-realme-7-5g-rmx2111
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
immns said:
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
Click to expand...
Click to collapse
good. this for Realme 7 :
- Textguide : https://telegra.ph/Hard-Brick-Fix-for-Realme-7-01-25
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
Hi everyone,
I tried to install Lineage OS on my Xperia Tablet Z Wifi and followed the instructions here: https://wiki.lineageos.org/devices/pollux_windy/install
I am on Ubuntu and I did unlock the bootloader successfully. Then I tried to flash twrp but this is where things went wrong.
After entering
Code:
fastboot flash boot ./twrp-3.5.2_9-0-pollux_windy.img
the device did not start anymore. I can still enter fastboot mode and the device is recognized on the PC but else the only thing that happens is the LED blinking red.
Any ideas where to go from here are appreciated.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I tried this but flashing the boot.img does not change anything unfortunately.
brickedmytablet said:
I tried this but flashing the boot.img does not change anything unfortunately.
Click to expand...
Click to collapse
You can reflash stock ROM via Flashtool v.0.9.18.6. or flash another boot.img to check if it boots or not.
Thank you, this worked for me.
Should have used the right twrp form the beginning. flash to boot works if it is the right version in my case scorpion_windy