Database Develop

asus memo pad 7 (me176cx) "unable to mount /factory"

Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)

kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal

I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?

paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black

I have the same problem and can't find any solution yet :crying::crying:

sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error

kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.

Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?

kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot

[RECOVERY] ALL Stock recovery.img and boot.img for ZD551KL (Z00T)

Hi All,
So Marshmallow 6.0 was just released today for ZD551KL Zenfone Selfie and I had basically trouble upgrading manually since I already have unlocked bootloader and have TWRP flashed instead of the original recovery.img which is needed to do the manual firmware upgrade from ASUS.
Since I no longer have my original recovery.img I was able to find the complete list of recovery.img, I'm glad someone uploaded it and i was able to find it.
If you're having trouble upgrading to Marshmallow from LP because of TWRP installed, flash the stock 1.15.40.1582 first and then flash the ASUS official MM firmware.
The recovery.img can be found here:
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!V0tUXT6a
I hope this helps.
Thanks

Finally you got the stock recovery. ?
Hit Thanks If I Helped

pjl3dm said:
The recovery.img can be found here:
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!V0tUXT6a
I hope this helps.
Thanks
Click to expand...
Click to collapse
Recovery images for ZE550KL/ZE600KL and ZE601KL/ZE551KL can be found here
It would be nice if you download are recovery images and provide direct download links here. Make a clean well documented thread. This will benefit many users

signature verification failed
I have ZD551KL Selfie,
I Got error as
E: failed to verify whole-file signature
E: signature verification failed
while update to MM Stock update.
i flashed stock recovery.
i previously installed CM-13 RR Rom
Help Need
Advance Thanks

Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."

Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
I think you need to update to latest LP firmware so that boot and recovery img get updated. Then it might not stuck at verifying update package. Although it did took time around 10 minutes in my Z00L to complete verifying image process while upgrading to MM.
Hope it helps
Hit Thanks If I Helped

kunalchitara said:
I think you need to update to latest LP firmware so that boot and recovery img get updated. Then it might not stuck at verifying update package. Although it did took time around 10 minutes in my Z00L to complete verifying image process while upgrading to MM.
Hope it helps
Hit Thanks If I Helped
Click to expand...
Click to collapse
well, I've been waiting for about 1 hour. What I did was to install the recovery from this thread then the latest L update, so I can also get the latest recovery, then tried updating to M. Adb sideload doesn't seem to work. I'll try once again.

Fulga666 said:
well, I've been waiting for about 1 hour. What I did was to install the recovery from this thread then the latest L update, so I can also get the latest recovery, then tried updating to M. Adb sideload doesn't seem to work. I'll try once again.
Click to expand...
Click to collapse
Well, did you booted the latest LP once, before upgrading to MM?
Hit Thanks If I Helped

kunalchitara said:
Well, did you booted the latest LP once, before upgrading to MM?
Hit Thanks If I Helped
Click to expand...
Click to collapse
Yes, ofc I dod boot it. I've been waiting since I last replied.

Fulga666 said:
Yes, ofc I dod boot it. I've been waiting since I last replied.
Click to expand...
Click to collapse
I am not sure but wiping system through fastboot might help.
Might lead devs like @sziraqui can help you on this more precisely.
Hit Thanks If I Helped

raindaddy said:
I have ZD551KL Selfie,
I Got error as
E: failed to verify whole-file signature
E: signature verification failed
while update to MM Stock update.
i flashed stock recovery.
i previously installed CM-13 RR Rom
Help Need
Advance Thanks
Click to expand...
Click to collapse
Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
No need to flash stock recovery and last lollipop update. Just flash twrp and then use this guide

sziraqui said:
No need to flash stock recovery and last lollipop update. Just flash twrp and then use this guide
Click to expand...
Click to collapse
In the end I have simply placed the update zip in the internal memory and that did the job, I'll use twrp to flash the smoothified room when it's available for Z00T. Thanks anyway!

boot.img and recovery.img for zenfone 2 laser ZE500KL (vesion 13.10.7.1) ???

Hi,
I also had cm13 installed, now want to go back to asus stock rom WW-1.15.40.1582, I have installed original boot and recovery from link posted in original post, however when I try flashing through adb I am getting error 'can not read zip' while installing from sd card I get message 'verifying update package' and it goes back to recovery home screen thereafter
Please help

Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
Did u whipe data before update..?
Reboot ur phone first and wait after loading complete try to update..
Hope this help

is there a recovery img for ZE550KL? 21.40.1220.1877 new update. tnx

Has someone the stock recovery.img for ze551kl z00td WW_user_21.40.1220.1615 ?
Sent from my ASUS_Z00TD using XDA-Developers mobile app

Stock Recovery for WW-21.40.1220.1943 (Zenfone 2 Laser ZE550KL @ 2 GB)
Please provide the download links

I need ZE601KL Files to Recover IMEI.
I need help. Whoever has ZenFone 2 Laser model ZE601KL SKU WW has root or system comstum, could you send me these files so I repair my system that does not recognize the imei.
Do the following process below.
Active in Android:
Active USB Depuration
Select Acess Root ADB Mode
Commands Terminal use ADB.exe
adb shell
su
cat /dev/block/mmcblk0p17 > /mnt/sdcard/fsc.mbn
cat /dev/block/mmcblk0p16 > /mnt/sdcard/fsg.mbn
cat /dev/block/mmcblk0p41 > /mnt/sdcard/modemst.img
cat /dev/block/mmcblk0p18 > /mnt/sdcard/modemst1.img
cat /dev/block/mmcblk0p19 > /mnt/sdcard/modemst2.img
Take these files saved in your internal memory and send me, thank you.


[QUOTE="raindaddy, post: 67571907, member: 7561460"]I have ZD551KL Selfie, I Got error as E: failed to verify
how did you successfully flashed stock rom UL-Z00T-WW-1.15.40.1582-user.zip? i have ZD551KL Selfie too. i tried to flash many stock roms for my Zenfie but no luck.
please help

Black Screen Recovery

Hi, I've got a problem regarding TWRP and the recovery partition.
I have downloaded and flashed TWRP following the guide in the development section, but everytime I boot into recovery I get a black screen and the notification led glows white.
If I use the "fastboot boot" command I can access TWRP, but that's only temporary and won't work for me. I've tried flashing from fastboot in windows and flashing from the temporarily booted TWRP on the phone. If the custom recovery won't work at all, I'd at least like to get back to stock recovery.
Thx for your help!

lspflr said:
Hi, I've got a problem regarding TWRP and the recovery partition.
I have downloaded and flashed TWRP following the guide in the development section, but everytime I boot into recovery I get a black screen and the notification led glows white.
If I use the "fastboot boot" command I can access TWRP, but that's only temporary and won't work for me. I've tried flashing from fastboot in windows and flashing from the temporarily booted TWRP on the phone. If the custom recovery won't work at all, I'd at least like to get back to stock recovery.
Thx for your help!
Click to expand...
Click to collapse
i had this problem did you update to 3.5.3 version? or you are still on 3.5.1

btouareg said:
i had this problem did you update to 3.5.3 version? or you are still on 3.5.1
Click to expand...
Click to collapse
Still on 3.5.1

lspflr said:
Still on 3.5.1
Click to expand...
Click to collapse
that's why you have this problem
download 3.5.3 and flash it manually
try to open twrp via fastboot
then do a clean flash for 3.5.3
then everything will work normally

btouareg said:
that's why you have this problem
download 3.5.3 and flash it manually
try to open twrp via fastboot
then do a clean flash for 3.5.3
then everything will work normally
Click to expand...
Click to collapse
Ok, I ended up dirty flashing 3.5.3 via booted TWRP and then it worked! I'm just wondering what the rom version has to do with the recovery partition, as they - from my understanding - are two separate things and shouldn't interfere with each other.
My problem is solved though so thank you for your help!

lspflr said:
Ok, I ended up dirty flashing 3.5.3 via booted TWRP and then it worked! I'm just wondering what the rom version has to do with the recovery partition, as they - from my understanding - are two separate things and shouldn't interfere with each other.
My problem is solved though so thank you for your help!
Click to expand...
Click to collapse
Cool!! enjoy your new op3t and im glad that i helped you

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

Can not get back to Stock from LineageOS Android 11

I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:

Format data after flashing Ozip thats important . try that with twrp

Anask3444 said:
Format data after flashing Ozip thats important . try that with twrp
Click to expand...
Click to collapse
Already tried bro.. no luck

ImperoDroider said:
Already tried bro.. no luck
Click to expand...
Click to collapse
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107

ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
If it says "boot/recovery damaged" and you're still able to use your phone, you should consider yourself lucky. I had to send mine in warranty for repair. I too am trying to go back to stock ROM after installing LOS 18.

Schumanzuar said:
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
Click to expand...
Click to collapse
These images have bricked my phone! Error message:
The current image(boot/recovery) have been destroyed and can not boot.
Please flash the correct image or contact customer service to fix it.
Tried flashing TWRP, no luck. Cannot boot.

do you have flash again the vbmeta.bin
I do that and after the rom start again for me

rpfe26 said:
do you have flash again the vbmeta.bin
I do that and after the rom start again for me
Click to expand...
Click to collapse
I didn't try that, however I did manage to get my phone up and working again after having destroyed the boot/recovery
I used Realme Flash Tool in combination with TWRP to get the phone up and running.

ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
I managed to get my phone up and running. Did you manage to get yours?

Milan-XDA said:
I managed to get my phone up and running. Did you manage to get yours?
Click to expand...
Click to collapse
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?

adimegarocker said:
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?
Click to expand...
Click to collapse
Yes, that is correct.