Database Users

Flashing problem

Hello guys
I am trying to flash cm13 on my Yureka(cm11 ) by following the steps
1.unlocked boot loader(by fastboot)
2.flashed twrp recovery (by fastboot)
3.flashed su update(by twrp)
4.copied CM13 Rom file and gapps file into my sd card
5.Rebooted in recovery mode
6.wiped cache,dalvik cache,system,data,internal(eXcept micro sd)
7.Done format system
8.Installed cm13 and gapps
9.Rebooted
Result is got stucked at yu logo :crying:
OTHER METHODS TRIED:
After 9th step i wiped dalvik cache and cache and rebooted
and aslo tried by formating nothing is worked still i stuck at yu logo
Then i thought the problem is with cm13 folder the i tried with RR marshmallo Rom ,miui7 and with infnitive Os but none worked
then i tried crDRoid kitkat version then my phone was properly booted.
i am unable to flash any rom other than crdroid kitkat version
please!!!!!!!!!!!!!!!!!!!!!!! help me with your suggestions:crying:
Thank you

akshay114 said:
Hello guys
I am trying to flash cm13 on my Yureka(cm11 ) by following the steps
1.unlocked boot loader(by fastboot)
2.flashed twrp recovery (by fastboot)
3.flashed su update(by twrp)
4.copied CM13 Rom file and gapps file into my sd card
5.Rebooted in recovery mode
6.wiped cache,dalvik cache,system,data,internal(eXcept micro sd)
7.Done format system
8.Installed cm13 and gapps
9.Rebooted
Result is got stucked at yu logo :crying:
OTHER METHODS TRIED:
After 9th step i wiped dalvik cache and cache and rebooted
and aslo tried by formating nothing is worked still i stuck at yu logo
Then i thought the problem is with cm13 folder the i tried with RR marshmallo Rom ,miui7 and with infnitive Os but none worked
then i tried crDRoid kitkat version then my phone was properly booted.
i am unable to flash any rom other than crdroid kitkat version
please!!!!!!!!!!!!!!!!!!!!!!! help me with your suggestions:crying:
Thank you
Click to expand...
Click to collapse
No mm rom will work unless u first upgrade the default cyanogen software from cm11 to cm12.1 since the bootloader of cm11 is 32bit and cm12.1 is 64bit and all roms mostly are 64bit so they wont boot
So follow the above steps you mentioned the same way but first flash cm12.1 fastboot images and boot then you will be able to flash any rom
Sent from my ONE E1003 using Tapatalk

Hearty thanks for your reply ,cuz i spent more than 5 nights on this but couldnt make it ,now I got clarity about the problem I'll try to implement what you said but how can I update to 12.1 n after that how to root and install twrp or cwm and finally thanks thanks thanks a lot for ur reply

I tried with several KitKat roms
I also tried to install several ROMs, which are based on CM 11, but only 2/20 ROMs have worked.
Rest 18 are not working, and they get stuck up at the 2nd boot screen.
How can I resolve this problem?
loveboy_lion said:
No mm rom will work unless u first upgrade the default cyanogen software from cm11 to cm12.1 since the bootloader of cm11 is 32bit and cm12.1 is 64bit and all roms mostly are 64bit so they wont boot
So follow the above steps you mentioned the same way but first flash cm12.1 fastboot images and boot then you will be able to flash any rom
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse

1) download cyanogen os 12.1 fastboot images from here http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
2) download flashing tools from here https://drive.google.com/file/d/0B48lBYmwzkD5cVA1dVFvU0plTW8/view?usp=sharing
3) extract files of both zip files in single folder
4)connect your phone in fastboot mode and check all drivers are installed
5) now open flash-all.bat and let it run
6) if everything went fine then you are done (first boot may take 20 mins after flashing )
7) use this for more http://forum.xda-developers.com/yureka/development/windows-yuware2013266073-t3193757

loveboy_lion said:
1) download cyanogen os 12.1 fastboot images from here http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
2) download flashing tools from here https://drive.google.com/file/d/0B48lBYmwzkD5cVA1dVFvU0plTW8/view?usp=sharing
3) extract files of both zip files in single folder
4)connect your phone in fastboot mode and check all drivers are installed
5) now open flash-all.bat and let it run
6) if everything went fine then you are done (first boot may take 20 mins after flashing )
7) use this for more http://forum.xda-developers.com/yureka/development/windows-yuware2013266073-t3193757
Click to expand...
Click to collapse
Thanks for your reply
lovely boy am done as u said now how to enter into recovery and how to unlock the device,???
i tried by using
adb reboot bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery recovery-yu.img
and tried to enter into recovery mode but i see a blank screen for few seconds and rebooted into normal mode and switched on

akshay114 said:
Thanks for your reply
lovely boy am done as u said now how to enter into recovery and how to unlock the device,???
i tried by using
adb reboot bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf flash recovery recovery-yu.img
and tried to enter into recovery mode but i see a blank screen for few seconds and rebooted into normal mode and switched on
Click to expand...
Click to collapse
you have to flash 64 bit recovery 32 bit wont work
http://forum.xda-developers.com/yur...recovery-twrp-2-8-4-0-touch-recovery-t3004699

can`t Unlock the boatloader or enter the recovery (Stuck in 1+ LOGO) Plz Help

I Have a big issue and need your help
I was OOS3 and do all the correct steps to get modified TWRP to setup custom rom and succeeded on this they I decide to back agaon to OOS3 as it`s more sable
So I download OOS3 and flash it from my Modified Recovery and works fine
Than I decide to enter the recovery just to clear the cash for agood performance and here .. the issue started ...
when I click reboot to recovery , the mobile stopped @ 1+ LOGO So I remmember that this modified recovery is not working with oos3
so I get the steps for unloacking the boatloader again to flash the recovery compatible with OOS3
and HERE .. I see my device when I type
fastboot devices ,,,
but once I type "fastboot oem unlock" it`s show my ok and device rebooted in the same 1+ LOGO
SO I now Stuck in this logo
Cannot enter the recovery Or even the OOS3 just can enter the fastboat mode
Please I need your help how can I manage this

I think your thread will get moved to the General section. But in the meantime try this it worked for me
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Sent from my ONE A2005 using XDA-Developers mobile app

Use the search button before posting.. There atleast 4 threads with the solution.

Wrong section

the command you're looking for is not the unlock one but this one: fastboot flash recovery "twrp-2.8.x.x-xxx.img" just replace "twrp-2.8.x.x-xxx.img" with the name of the recovery .img you have in the same folder as fastboot.

Ahmed Shawky said:
I Have a big issue and need your help
I was OOS3 and do all the correct steps to get modified TWRP to setup custom rom and succeeded on this they I decide to back agaon to OOS3 as it`s more sable
So I download OOS3 and flash it from my Modified Recovery and works fine
Than I decide to enter the recovery just to clear the cash for agood performance and here .. the issue started ...
when I click reboot to recovery , the mobile stopped @ 1+ LOGO So I remmember that this modified recovery is not working with oos3
so I get the steps for unloacking the boatloader again to flash the recovery compatible with OOS3
and HERE .. I see my device when I type
fastboot devices ,,,
but once I type "fastboot oem unlock" it`s show my ok and device rebooted in the same 1+ LOGO
SO I now Stuck in this logo
Cannot enter the recovery Or even the OOS3 just can enter the fastboat mode
Please I need your help how can I manage this
Click to expand...
Click to collapse
First read the Forum Rules on posting, moved here out of the Development Section....

fastfreddy101 said:
the command you're looking for is not the unlock one but this one: fastboot flash recovery "twrp-2.8.x.x-xxx.img" just replace "twrp-2.8.x.x-xxx.img" with the name of the recovery .img you have in the same folder as fastboot.
Click to expand...
Click to collapse
How Can I do this and I even can not unlock the boatloader ?

should still be unlocked - put phone in fastboot mode, check for it via: fastboot devices. If its there then just flash the recovery with: fastboot flash recovery "twrp-2.8.x.x-xxx.img" then reboot into recovery. should work

fastfreddy101 said:
should still be unlocked - put phone in fastboot mode, check for it via: fastboot devices. If its there then just flash the recovery with: fastboot flash recovery "twrp-2.8.x.x-xxx.img" then reboot into recovery. should work
Click to expand...
Click to collapse
I can`t unlock the phone

Thanks for your reply
My situation now that I`m stuck in boot loop and I can`t enter any think , only the fastboat mode and I can not unlock my device
every time I tried to Unlock it , till me Fail to unlock
I follow this steps with no change
http://www.technobuzz.net/unbrick-oneplus-2/
In this video also with no hope
https://www.youtube.com/watch?v=R4SVSovw4Jo

Ahmed Shawky said:
Thanks for your reply
My situation now that I`m stuck in boot loop and I can`t enter any think , only the fastboat mode and I can not unlock my device
every time I tried to Unlock it , till me Fail to unlock
I follow this steps with no change
http://www.technobuzz.net/unbrick-oneplus-2/
In this video also with no hope
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 to get back your old twrp and then follow the instructions from here https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/ carefully (use the tread for users already have twrp)

When did you lock the phone again after unlocking it?

Assuming the phone shows up when running "fastboot devices" try running this "fastboot -i 0x2a70 oem unlock-go" - worked for me

OP2 stuck in bootloop on upgrading 3.0.2 .. even after trying tons of things

First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out

Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk

Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again

Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.

Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!

Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!

Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.

OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...

ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??

No i forgot to enable...

No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?

ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.

ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.

ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?

Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).

When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings

Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android

ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help

ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Unable to flash TWRP on Moto e3 power with latest software update

I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.

you can try this
ajyotirmay said:
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
Click to expand...
Click to collapse
Get into the fastboot mode try again unlock your oem
'fastboot oem unlock'(volume up on your phone and select yes ) --->'fastboot format userdata' now flash the twrp recovery the link is below try this it may work worked fine for me and dont know really why the updated twrp is not flashing
My Google Drive link for TWRP recovery:-https://drive.google.com/file/d/0BylQ6RZ2mIP_cElxMzFoRVEyRDg/view?usp=sharing

Real Me 2 Pro Boot / Recovery Image have been damaged

today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!

vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
Hi, how about your phone? is your problem have solved?
i have same problem like you. and i want to know about to solve it
thank you

hi, my problem a bit different with recovery.
i have stock recovery with unlocked bootloader. im with coloros 5.2 and can not install coloros 6 update. stock recovery cant find update file in phone storage, wifi doesnt work and starting update from os, returns update failed after one reboot. and suggestion?

vishnusai.karumuri said:
today , I unlocked the bootloader of my Real Me 2 Pro and everything was fine and after I tried to boot it back to system after flashing magisk and the decryption.zip , I got this message saying " The current boot / recovery image have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
I can just flash the official firmware or any ohter ROM but the PC can't seem to detect the fastboot mode and neither am I able to boot into fastboot / recovery.
can someone please help.!
Click to expand...
Click to collapse
I face the same issue. Flashed twrp. Then flashed boot+magisk+patched img file. Now the phone halts at the fastboot mode and is not booting up. It also unable to be power off. plz help. The model is Realme2 RMX 1805

Dont worry you do have a unlocked device so u need a pc to do that download system.img, vendor.img for your device and just open cmd then type this fastboot flash system system.img then fastboot flash vendor vendor.img and reboot it second method if you dont have an pc not sure that it will work you need a second device with otg support download bugjaeger app from playstore and use the same commands which i mention in pc method