How To Guide Redmi 8A (DUAL) Working TWRP (UNOFFICIAL) - Xiaomi Redmi 8A Dual

Hey Guys Today i am happy to publish TWRP for Redmi 8A DUAL
Install Process:-
1. Go to bootloader mode by pressing (vol down + power)
2.type this below command
fastboot flash recovery twrp.img
3.press (vol up + power) it will boot into TWRP.
TWRP DOWNLOAD LINK :- Download
If you want contribute to twrp device tree here is the Link
https://github.com/Aghora7/android_device_xiaomi_olivewood/tree/twrp

Reserved

Thanks great work. Btw, I've a favor to ask, my r8adual is in bootloop as i resized and recreated system,cust and userdata with parted, now it's messed up and device boolooping even after getting into fastboot mode.. My last resort is to resize the internal partition exactly as someone else's device. Could you please send me the partition table's picture if you've this device?

.excalibur said:
Thanks great work. Btw, I've a favor to ask, my r8adual is in bootloop as i resized and recreated system,cust and userdata with parted, now it's messed up and device boolooping even after getting into fastboot mode.. My last resort is to resize the internal partition exactly as someone else's device. Could you please send me the partition table's picture if you've this device?
Click to expand...
Click to collapse
nvm i got it fixed by service center, replicating the partition also didn't guarantee it'd fix

.excalibur said:
Thanks great work. Btw, I've a favor to ask, my r8adual is in bootloop as i resized and recreated system,cust and userdata with parted, now it's messed up and device boolooping even after getting into fastboot mode.. My last resort is to resize the internal partition exactly as someone else's device. Could you please send me the partition table's picture if you've this device?
Click to expand...
Click to collapse
Never play with partitions. i see you fixed it with reflashing entire system.anyway if you want anything related join official redmi 8a dual group.

Thanks for recovery but I have a doubt.
Should I need to patch the boot before flashing this?

Pavan__pavan said:
Thanks for recovery but I have a doubt.
Should I need to patch the boot b
Click to expand...
Click to collapse
no need to patch boot image from rom , patching boot image via yaalex site , that patching method is only needed while flashing magisk zip to root the phone
First boot phone into fastboot
Then flash recovery image through CMD or shell by fastboot flash recovery recovery.img command

I am unable to download recovery file giving 404 error
Please help me out

Adityasalil95 said:
no need to patch boot image from rom , patching boot image via yaalex site , that patching method is only needed while flashing magisk zip to root the phone
First boot phone into fastboot
Then flash recovery image through CMD or shell by fastboot flash recovery recovery.img command
Click to expand...
Click to collapse
Can you provide me twrp file i you have cause i am unable to download recovery file

Link is dead. Can someone provide a mirror please ?

Related

[Q] Which partition to format to remove CWM ?

Hey,
I have been given Motorola Xoom and when I'm booting into recover it has got broken or wrong CWM. Tablet goes in the loop and I see that CWM Droid with exclamation and parts and pieces coming out of his stomach
I know that partition with CWM can be formatted from ADB, but i haven't done it for long time and never on tablet.
Could someone tell me / confirm which partition installed CWM sits on ?
Also, what's the chance that something will go wrong and I won't be able to flash new CWM ?
birkopf said:
Hey,
I have been given Motorola Xoom and when I'm booting into recover it has got broken or wrong CWM. Tablet goes in the loop and I see that CWM Droid with exclamation and parts and pieces coming out of his stomach
I know that partition with CWM can be formatted from ADB, but i haven't done it for long time and never on tablet.
Could someone tell me / confirm which partition installed CWM sits on ?
Also, what's the chance that something will go wrong and I won't be able to flash new CWM ?
Click to expand...
Click to collapse
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
AlEsC said:
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
Click to expand...
Click to collapse
I don't have root. I also cannot flash recovery because CWM sit's there and is broken
birkopf said:
I don't have root. I also cannot flash recovery because CWM sit's there and is broken
Click to expand...
Click to collapse
fastboot will overwrite you broken CWM
1) reboot in bootloader (command : adb reboot bootloader)
2) fastboot flash recovery twrp.img
You can find TWRP image here :
http://forum.xda-developers.com/motorola-xoom/development/recovery-twrp-2-8-0-0-t2880998
AlEsC said:
fastboot will overwrite you broken CWM
1) reboot in bootloader (command : adb reboot bootloader)
2) fastboot flash recovery twrp.img
You can find TWRP image here :
http://forum.xda-developers.com/motorola-xoom/development/recovery-twrp-2-8-0-0-t2880998
Click to expand...
Click to collapse
I don't think I can flash recover over existing recovery. This will most likely lead to soft brick...
Before flashing twrp.img I need to format the partition where CWM sits currently.
- Do you know which partition is it and how to do it ?
birkopf said:
I don't think I can flash recover over existing recovery. This will most likely lead to soft brick...
Before flashing twrp.img I need to format the partition where CWM sits currently.
- Do you know which partition is it and how to do it ?
Click to expand...
Click to collapse
Without root you won't be able to issue a mkfs command (as far as I know).
You can use :
fastboot format recovery
and/or
fastboot erase recovery
AlEsC said:
If you can boot into Android (and you have root access), you can use Flashify.
Otherwise you can use "fastboot flash recovery you_recovery.img".
Click to expand...
Click to collapse
AlEsC said:
Without root you won't be able to issue a mkfs command (as far as I know).
You can use :
fastboot format recovery
and/or
fastboot erase recovery
Click to expand...
Click to collapse
Sounds good. So, just to confirm
- I need to first clear the recovery partition with commands you wrote above
- Flash new recovery from the link you submitted in the post above
- Flash selected ROM from the SD card using new recovery
Does it all sound fine ?
birkopf said:
Sounds good. So, just to confirm
- I need to first clear the recovery partition with commands you wrote above
- Flash new recovery from the link you submitted in the post above
- Flash selected ROM from the SD card using new recovery
Does it all sound fine ?
Click to expand...
Click to collapse
Correct.
Choose carrefully you recovery image (BigPart or non-BigPart) depending on the ROM you wish to install.
AlEsC said:
Correct.
Choose carrefully you recovery image (BigPart or non-BigPart) depending on the ROM you wish to install.
Click to expand...
Click to collapse
Thanks!
Just quick question : what is the BigPart or non-BigPart ?
Googling that doesn't produce any sensible results

How can I root project spectrum?

Are there any tools around for rooting Spectrum on the R7Plusf?
W1F1 said:
How am I able to root project spectrum on the Oppo R7 Plus?
Thanks in advance!
Click to expand...
Click to collapse
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
EximusCode said:
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
Click to expand...
Click to collapse
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
W1F1 said:
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
Click to expand...
Click to collapse
Bingo my friend. If you want the links you need only ask. :good:
EximusCode said:
Bingo my friend. If you want the links you need only ask. :good:
Click to expand...
Click to collapse
The links would be fantastic, thanks so much!
W1F1 said:
The links would be fantastic, thanks so much!
Click to expand...
Click to collapse
Will post them ASAP
Thanks!
W1F1 said:
Thanks!
Click to expand...
Click to collapse
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
EximusCode said:
Will post them ASAP
Click to expand...
Click to collapse
I'm sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
EDIT: Whoops disregard that I managed to download it.
W1F1 said:
I'm so so sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
Sorry again.
EDIT: Sorry disregard that I managed to download it.
Click to expand...
Click to collapse
Hope it works for you like it did for me :good:
EximusCode said:
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
Click to expand...
Click to collapse
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
W1F1 said:
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
Click to expand...
Click to collapse
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
EximusCode said:
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
Click to expand...
Click to collapse
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
W1F1 said:
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
Click to expand...
Click to collapse
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
EximusCode said:
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
Click to expand...
Click to collapse
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
W1F1 said:
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
Click to expand...
Click to collapse
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
EximusCode said:
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
Click to expand...
Click to collapse
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
W1F1 said:
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
Click to expand...
Click to collapse
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
EximusCode said:
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
Click to expand...
Click to collapse
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
W1F1 said:
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
Click to expand...
Click to collapse
Okay, good luck

[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1

Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27
So we can flash either through TWRP or Fastboot right?
Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%
Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.
Thank you very much.
Is there any userdata.img available?
alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.
sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found
I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?
Thanks. Both methods work fine. Don't ask how I found out.....
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1
Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it
Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?
Does Nokia 1 support DT2W?
Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance
Can any please repost the firmware , the link isn't working

Unbrick your Realme C12

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 Users​For 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 Users​For 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 instructions​See 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/
Credits​xyzz / 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

How to flash corvus os 15 Android r in redmi 10x 5g

341 redmi 10x 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
https://unofficialtwrp.com/wp-content/uploads/2019/11/vbmeta.zip
1 flash miui recovery img
Go to fastboot and type fastboot flash recovery recovery1.img
After that hold power button and volume up button until you see a Chinese menu with three options first select option two after that option one and after that option two after wiping data you will see that three options again select option one and select option one then hold volume down button until you see fastboot
Type fastboot reboot fastboot
Wait
You will see fastbootd then rename corvus image to system.img
Then type
Fastboot flash system.img
Click power button
Wait
When you see corvus boot animation hold power button and volume down button until you see fastboot
Rename twrp image to recovery.img
Then type
Fastboot flash recovery recovery.img
Fastboot flash vbmeta vbmeta.img
Fastboot flash misc misc.bin
Fastboot boot recovery.img
In twrp flash permissiver 5 then reboot to system
Done.
If you want gapps download magisk app
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
When it's download rename it to magisk.zip
Go to twrp
Flash it
Reboot to system rename it to magisk.apk and install it after that download this file
https://sourceforge.net/projects/magiskgapps/files/r/Core/MagiskGApps-core-V1.0.zip/download
After that go to magisk in modules go to install from storage and select zip you downloaded flash it with magisk after reboot you will see play store is added to your app drawer install Google apps you need from play store
https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20210329/Corvus_v15.0-RavenClaw-treble_arm64_ab-nonlite-29032021-Unofficial-1117.img.xz/download
While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug me in
resirch26 said:
While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug
Click to expand...
Click to collapse
You flashed permissive in twrp?
Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
If not flash it
Hsnmastoor said:
If not flash it
Click to expand...
Click to collapse
sim card inactive
Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.
resirch26 said:
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.
Click to expand...
Click to collapse
Hold power button and volume down for fastboot. Power with volume up for recovery
dothaison said:
sim card inactiv
Click to expand...
Click to collapse
Can you check IMEI?
Hsnmastoor said:
Bạn có thể kiểm tra IMEI không?
Click to expand...
Click to collapse
I can't test IMEI
Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
can you give me nvdata backup? . I have lost my IMEI.
Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
I have lost IMEI. Can you give me a backup nvram ? thank you.
dothaison said:
I have lost IMEI. Can you give me a backup nvram ? thank you.
Click to expand...
Click to collapse
Nvram.img
drive.google.com
Has anyone flashed this successfully?
any bugs? i flashed crdroid. it's too buggy
Hi everybody,
Still mad at myself for buying this phone (with MediaTek SOC) because of the lack of custom ROM support. Never had this issue before with any of my phones. If only i knew this before. The hardware of the phone is great, but the software makes it really frustrating to work with.
So i've tried a lot of things to either mod the original (Chinese) ROM so it's at least functional. And i have also tried multiple of these GSI ROM install methods. Everytime without succes.
I've tried your previous method with the 'GSI installer' and the one from this guide. Neither of them worked. (Boot loop). I have a feeling i run into trouble because (if i'm correct) the original ROM uses a 'super' partition and not a 'system' partition.
If i remember correctly the GSI installer couldn't continue because it couldn't find the system partition.
In this guide (for corvus) i figured i'd flash the system.img to my super partition. Of cource that doesn't work either. If only it was that simple.
Everytime it fails i have to flash back to a standard xiaomi ROM and start all over again. Because for some reason the TWRP backups also dont work for me.
So maybe i'm missing a step in the guide or i've already tried so much to mod my phone i've changed settings/partitions that shouldn't have been changed for this guide to work.
My bootloader is unlocked, i have/had TWRP 3.41 installed.
After a fail i flash back to the original ROM using Xiaomi ABD/Fastboot Tools (xiaomiABDFastbootTools.jar)
Any help would be appreciated!
I never had issue when I flashed the GSI from the crdroid guide did you make sure that you put the GSI installer.zip and the image file rename to system.img to the root internal storage??
Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?
Abducted23 said:
Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?
Click to expand...
Click to collapse
First I flashed crdroid. but did not like it. then I flashed blissrom using the same guide for crdroid. i just downloaded the rom posted on the guide. while for the bliss rom the arm64-bgN
Did you wipe data first before flashing?

Categories

Resources