Question A little help for LineageOS 18 20211002-nio-156 image - Motorola Moto G100 / Edge S

Hi, I am looking for the boot.img for LineageOS 18 20211002-nio-156
I had damaged boot on my device, and it goes to fastboot mode every time. I have tried looking for the boot.img on LineageOS website, but there is only LineageOS 20 images.
If anyone have the image, version of LineageOS 18 20211002-nio-156, would you kindly share with me? Thanks a lot!

Just look for a tool to unzip the ROM and get the boot.img

Deivid Soltoski said:
Just look for a tool to unzip the ROM and get the boot.img
Click to expand...
Click to collapse
Thanks for your reply, unfortunately I do not have the ROM.

Oh :l

Deivid Soltoski said:
Oh :l
Click to expand...
Click to collapse
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?

There are couple of game save files I have not backup. Is that possible to use fasboot mode or recovery mode to get those files out? Then I can flash the device.

fuluel said:
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?
Click to expand...
Click to collapse
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases

Deivid Soltoski said:
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases
Click to expand...
Click to collapse
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?

fuluel said:
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?
Click to expand...
Click to collapse
Mount just mounts the cell phone partitions to access and modify them, and the G100 only works with TWRP on Android 11 only, and don't even try to install another type of ROM/recovery from another device because you can have your device blocked and then just throw it in the trash XD

When I am tring to flash Lineage-images-18-20211002-nio-156, I always got signature verification failed message. When I click YES, the process just stopped.
I had followed this guide https://wiki.lineageos.org/devices/nio/install/variant1 Is there anything I did wrong? Or is that possible to disable signature vericication in LOS revocery?

Related

Rooting for March Update?

Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now

Root + TWRP on Android 10 Post OTA?

I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?

how to reinstall Oxygen OS

HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/

Stuck at TWRP splash screen

I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.
Which magisk did you flash? 23 is not working for 9A
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.
Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard
Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.

Question How to unbrick One Plus Nord CE 2 Lite ?

I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
...reboot to fastboot, flash the original boot and vbmeta and you're done ...maybe you have to change back the slot, but it's almost impossible to brick the device
...don't mess around with "Recovery" ...this device has already the newest partitioning system and there is no recovery partition
best regards
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
... you're very welcome, Sir ...but really, don't mess around with "old school" recovery systems ...they are not needed anymore and furthermore they can't handle the "dynamic super partitioning" ...and again: nobody needs them after the year 2015 anymore
...best regards
NickR01 said:
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
Click to expand...
Click to collapse
Hey can you help me pls, I am in the exact same situation as you but I can't get the stock img files, whenever I use payload-dumper it just gives me system.img and nothing else, could you maybe share your img files ?
Edit: I manged to get some files but still not the boot.img, I don't undestand why it just refuses to give them to me, I redownloaded everything at least 3 times...
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Hey @NickR01 if possible can you send me an boot.img and vbmeta
I don’t have windows pc so can’t use Payload-Dumper
It will also help future users to unbrick device.
NickR01 said:
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Click to expand...
Click to collapse
@vikas_anakin What's your device version?
cph2381 cph2409
NickR01 said:
@vikas_anakin What's your device version?
cph2381 cph2409
Click to expand...
Click to collapse
cph2381
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
NickR01 said:
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
Click to expand...
Click to collapse
Extracting the payload.bin is not an issue, The issue is I don't have stock firmware.
I used https://www.getdroidtips.com/oneplus-nord-ce-2-lite-5g-firmware-flash-file/ but my wifi and Bluetooth are not working after installing it.
Do you have any suggestions on how can i resolve these issues?
@vikas_anakin Download authentic firmware from this app. Files are pulled from OnePlus servers.
Google Playstore: Oxygen Updater
Oxygen Updater Settings -> Enable Advanced Mode
Select device region.
Latest update for holi is CPH2381_11_A.13 as of now.
I extracted the images from the payload.bin found in the Oxygen Updater file (that I had actually successfully used to update my device) and flashed 2 partitions:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
I then rebooted and now it's stuck in a boot loop & I can't even access fastboot anymore. Can someone please help?
Thanks
EDIT:
I managed to access fastboot & flash the rest of the partitions to fix it.
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
lemonmuffs said:
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
Click to expand...
Click to collapse
Yes, that will work.
vikas_anakin said:
Yes, that will work.
Click to expand...
Click to collapse
Or else you can extract img files from the oneplus rom file.
and flash them using fastboot.
Okay thank you for the reply, would you be able to point me to a official img file ? Or maybe someone has one extracted I could use please? I have looked online, but the ones I have gotten don't seem to work. I have also looked on the oneplus website for an official img but I could not find one.
So after a little more research, I can use another android device with the app Oxygen updater, download the full img.... So I am currently doing that and then ill try use fastboot or twrp to flash. Just wanted to spread info incase anyone else is having issues getting latest official roms for this device.
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Jazzyjuis said:
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Click to expand...
Click to collapse
Hey man, I would suggest not going with msm tool or anything.
Just download the latest update file of your device using oneplus updater app, or you can ask for the file if some of your friends has the same device.
use this tool to extract payload files https://github.com/vm03/payload_dumper
Now you can follow the same procedure as here https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Categories

Resources