Related
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
You will have to msm flash
anupsnair said:
You will have to msm flash
Click to expand...
Click to collapse
That is what i did - twice already... Still no Boot into twrp...
martinforum said:
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
Click to expand...
Click to collapse
From what firmware are you from?
Hitman478™ said:
From what firmware are you from?
Click to expand...
Click to collapse
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
martinforum said:
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
Click to expand...
Click to collapse
Thank you. Yes this was the reason why! I can boot in twrp again.
There are different howto's out there. What is the right order to install following packages - do I have to reboot after each package?
Twrp
Lineage rom
Openapps Pico
Su
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Hitman478™ said:
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Click to expand...
Click to collapse
Thank you. Blue_spark twrp is working.
Now i have installed lineage and without reboot oppengapps pico but I do get an error message.
To ensure twrp, i reinstalled as you said bstwrp. But the reboot brings me back to a black screen.
Any tips for the right order to install and reboot?
What is a brick?If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux UsersFor Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows UsersFor Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructionsSee Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Creditsxyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359
MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com
Reserved
I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?
HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?
youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!
DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks
HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.
I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.
Thanks for your works sir, you are super awesome!
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks
HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/moonstone-s-oss
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Xiaomi Poco X5
Installation:
1. fastboot devices
2. fastboot boot twrp-3.7.0_13-0-moonstone.img
3. if you were using magisk, reflash it now
Notes:
- 13 for A13
- 12 for A12
Source tree: github
Send me a beer: Paypal
Download: https://sourceforge.net/projects/win-abs/files/moonstone/recovery/
Is this for X5 only or also working on X5 PRO?
gmbhneo said:
Is this for X5 only or also working on X5 PRO?
Click to expand...
Click to collapse
only X5, if you are willing to test it I can make it
Erwin Abs said:
only X5, if you are willing to test it I can make it.
Click to expand...
Click to collapse
I have X5 pro (3 days left to unlock bootloader). If you need a tester I can propose myself if there are no big risks to seriously brick my phone
DevilNoobIN made a port for Poco X5 Pro recently, https://www.pling.com/p/1993245/
Enjoy!
cool, wish XDA had a dedicated forum for moonstone
ChromaCobble said:
DevilNoobIN made a port for Poco X5 Pro recently, https://www.pling.com/p/1993245/
Enjoy!
Click to expand...
Click to collapse
I installed it and test, It's a good recovery. I don't understand why a thread isn't dedicated to it.
Shouldn't Poco X5 (non pro) have its own forum?
I was very close to installing it on my X5 Pro.
quasyl said:
I installed it and test, It's a good recovery. I don't understand why a thread isn't dedicated to it.
Click to expand...
Click to collapse
Can you please tell me which of the three recoveries you used and how you installed it? Actually I tried all of them and in all cases it failed to boot to the custom recovery (boot to system instead).
If you want a tester for x5 pro let me know.
Foramin said:
Can you please tell me which of the three recoveries you used and how you installed it? Actually I tried all of them and in all cases it failed to boot to the custom recovery (boot to system instead).
Click to expand...
Click to collapse
This one:
Recovery For Redwood
ORANGEFOX Recovery For Poco X5 Pro
www.pling.com
This recovery is specific for poco x5 pro.
It would be good to have a specific thread for Poco X5 pro (Redwood).
Be careful!
At that link you will find 3 files. The first and the second are for android 13, the third (orange fox) is for android 12.
With the release of X5 5G (Moonstone) kernel source code, hopefully this device will get more love...
quasyl said:
This one:
Recovery For Redwood
ORANGEFOX Recovery For Poco X5 Pro
www.pling.com
This recovery is specific for poco x5 pro.
It would be good to have a specific thread for Poco X5 pro (Redwood).
Be careful!
At that link you will find 3 files. The first and the second are for android 13, the third (orange fox) is for android 12.
Click to expand...
Click to collapse
Do you know the method to flash these recoveries?
Code:
fastboot flash boot_ab image.file
or
Code:
fastboot boot image.file
and then patch ramdisk.
I tried the 2nd method and device doesn't boot to recovery. I was afraid to flash it directly using the 1st method, because X5 pro uses "Boot as Recovery (A/B)" and doesn't have a separate recovery partition.
I'm getting a "FAILED : 'error unknown remote command'" when I try to fastboot boot it. :/ (And yes : the device is indeed a moonstone X5)
Any advice, maybe ?
(I reinstalled the latest adb & QC drivers as well as the R34 platform tools straight from Google)
hadiceberg said:
Do you know the method to flash these recoveries?
Code:
fastboot flash boot_ab image.file
or
Code:
fastboot boot image.file
and then patch ramdisk.
I tried the 2nd method and device doesn't boot to recovery. I was afraid to flash it directly using the 1st method, because X5 pro uses "Boot as Recovery (A/B)" and doesn't have a separate recovery partition.
Click to expand...
Click to collapse
Which one did you use? Tomorrow I want to flash the recovery but I never used a phone with recovery (A/B)
Did it worked without problems?
Hans_Werner said:
Which one did you use? Tomorrow I want to flash the recovery but I never used a phone with recovery (A/B)
Did it worked without problems?
Click to expand...
Click to collapse
I haven't flashed it yet.
As I understand, my device doesn't have a recovery partition and the method to flash a custom one is to boot the phone using that recovery image and then patching the boot ramdisk.
But I couldn't boot using the image.
hadiceberg said:
I haven't flashed it yet.
As I understand, my device doesn't have a recovery partition and the method to flash a custom one is to boot the phone using that recovery image and then patching the boot ramdisk.
But I couldn't boot using the image.
Click to expand...
Click to collapse
Thank you. I will see tomorrow if i can managed to flash recovery and flash current xiaomi.eu rom. Finger cross.
Hans_Werner said:
Thank you. I will see tomorrow if i can managed to flash recovery and flash current xiaomi.eu rom. Finger cross.
Click to expand...
Click to collapse
I think you don't need to flash a custom recovery to install xiaomi.eu. Use fastboot method instead.
Installing with Fastboot: (ROM Type: Fastboot)
Download Xiaomi.eu ROM zip file
Extract the ROM zip to a new folder
Power off your device
Boot your device in Fastboot mode (Hold volume down + power buttons)
Connect to PC via USB cable
Run one of the installation scripts (according to your PC operating system):
- first_install_with_data_format - with data wipe, if you're flashing Xiaomi.eu ROM for the first time or downgrading.
- update_rom - without data wipe, if you're updating from an older Xiaomi.eu ROM.
Done!
Thanks' for the Infos. But I want also to use Magisk / Root.
Hans_Werner said:
Thanks' for the Infos. But I want also to use Magisk / Root.
Click to expand...
Click to collapse
I'm using magisk without custom recovery.
You can install magisk, then use it to patch a copy of your boot.img (extracted from xiaomi.eu zip file).
Then flash the patched boot.img in fastboot mode.
Hi, I am looking for the boot.img for LineageOS 18 20211002-nio-156
I had damaged boot on my device, and it goes to fastboot mode every time. I have tried looking for the boot.img on LineageOS website, but there is only LineageOS 20 images.
If anyone have the image, version of LineageOS 18 20211002-nio-156, would you kindly share with me? Thanks a lot!
Just look for a tool to unzip the ROM and get the boot.img
Deivid Soltoski said:
Just look for a tool to unzip the ROM and get the boot.img
Click to expand...
Click to collapse
Thanks for your reply, unfortunately I do not have the ROM.
Oh :l
Deivid Soltoski said:
Oh :l
Click to expand...
Click to collapse
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?
There are couple of game save files I have not backup. Is that possible to use fasboot mode or recovery mode to get those files out? Then I can flash the device.
fuluel said:
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?
Click to expand...
Click to collapse
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases
Deivid Soltoski said:
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases
Click to expand...
Click to collapse
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?
fuluel said:
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?
Click to expand...
Click to collapse
Mount just mounts the cell phone partitions to access and modify them, and the G100 only works with TWRP on Android 11 only, and don't even try to install another type of ROM/recovery from another device because you can have your device blocked and then just throw it in the trash XD
When I am tring to flash Lineage-images-18-20211002-nio-156, I always got signature verification failed message. When I click YES, the process just stopped.
I had followed this guide https://wiki.lineageos.org/devices/nio/install/variant1 Is there anything I did wrong? Or is that possible to disable signature vericication in LOS revocery?