Question Oneplus Nord N20 GN2200_11_C.10 Android 12 Boot .IMG Help!! - OnePlus Nord N20 5G

I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!

Where? I couldn't find it

ScarletWizard said:
Did u find it
Click to expand...
Click to collapse
No I still can't find this specific one?! Stinks!

termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
I appreciate your help though. Thank you for taking the time to respond back.

termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
Thank you for taking your time to respond though.

I'm looking for a specific boot.img. it's in the title.. you need to use the msm download tool to revert back to stock. Sounds like your partitions are messed up and I assume they weren't backed up. I was hard bricked at one point and the msm tool was the only way for me to fix it all and revert back to stock. Make sure it's the correct msm tool for your phone though.

ScarletWizard said:
Try
Or this
Wipe data after flashy
Wipe data
Too large I got several but too large to attach
Click to expand...
Click to collapse
Can you send me the link for the specific boot.img I'm looking for by chance? It's the 11_C.10 version.

ScarletWizard said:
I locked my Boot loader and now device is ****ed
Click to expand...
Click to collapse
Why you can't just unlock it again? Do you have the the T-Mobile version?

The bootloader is encrypted and OnePlus's token just gives you the private to match the public encryption that keeps the bootloader from being edited. In theory if you can discover what file type one plus's token is in and eextract that and somehow dump your bootloader you could possibly manually decrypt it.

Do you have access to a Personal Computer? I could offer some links to a few programs that may be worth trying. I doubt it could hurt trying.

I could use teamviewer to try to use my tools to force your bootloader to unlock also if you happen to not find a solution.

termux4life said:
Thank you for taking your time to respond though.
Click to expand...
Click to collapse
i have the exact one

termux4life said:
I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!
Click to expand...
Click to collapse
Pretooted, that's funny as can be. A pretooted sideload so he can pull his own.

Ok so 2 things..
1st: Jayram1408, for being a senior member I'm really surprised you'd laugh at me for asking a question or not knowing something. Usually this is a safe place to learn, ask questions, and receive feedback that's positive and informative. I don't know if you think others will laugh at me with you but I doubt it
2nd: I don't know what is funny in the first place, pre-rooted GSI for DSU Sideloading purposes do exist and that's a fact. It makes it so you can use Partitions Backup & Restore properly when the GSI is loaded. Please read https://forum.xda-developers.com/t/...g-boot-image-and-making-your-backups.4499447/
Hopefully that catches you up with the rest of us and hopefully in the future you are but more helpful then hurtful to members within the community.

Hey All,
I am trying to root my Nord N20, but am getting a bootloop when trying to boot boot_a after flashing a magisk25210canary patched boot_b image over boot_a. I am flashing a patched boot_b image over boot_a because I am too scared to flash magisk patched boot_b over boot_b (which contains the working OS). My version information is:
android 12
Build: GN2200_11_C.11 Kernel:5.4.147-qgki-ga9e7460afd8c

Related

Boot Logos!

Just flash the zip in TWRP to change your boot logo. These should work for any model of the G6 Play. All backgrounds are white with the exception of the original boot logo. This was done to cover up that annoying bad key or N/A message. Enjoy!
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
the-her0 said:
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
Click to expand...
Click to collapse
Yep, check back in like 10-15min and I'll make that a logo.
Edit: Done!
Motorola Moon
This took me a few hours. Hope you folks like it. I'll probably make a few more over the next several days.
Is there a tutorial anywhere on how make these?
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Motorocker said:
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Click to expand...
Click to collapse
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
madbat99 said:
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
Click to expand...
Click to collapse
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Motorocker said:
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Click to expand...
Click to collapse
That's because TWRP can't read encrypted storage. Has to on your SD card.
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
flash713 said:
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...-boot-logo-maker-source-t2848667/post54841085
Can someone make boot.logo in HavocOs style?
Who can make logo.bin for havoc-os? I’m attaching a picture, and below it should be moto g6 play

Google Fi - Moto G Power firmware question.

My Moto G Power on Google Fi is using QPMS30.80-51-3. Which looks like AMXLA even though there is a RETUS firmware also but it is QPM not QPMS. Was about to root this phone but didnt want to upgrade the firmware without something to reflash.
I can just use fastboot boot boot.img to make sure the kernel works unfortunately ill have to erase user data because i will be removing encryption to see if it works. It wont boot with the rooted kernel with an encrypted userdata.
I can test the kernel with fastboot boot and just reclear userdata and reboot the phone, which is just a pain because I have to set it up again, but was more interested in the rest of the firmware being correct. Any ideas?
I have a pretty good history of building stuff but was going to get a working twrp setup going first and wanted to make a backup of stock.
https://mirrors.lolinet.com/firmware/moto/sofia/official/AMXLA/
vs
https://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
Mine is on QPMS.
I got the correct boot.img from a nice person on reddit. Time to make TWRP work now.
CodyF86 said:
I got the correct boot.img from a nice person on reddit. Time to make TWRP work now.
Click to expand...
Click to collapse
Care to share the correct boot.img?
donluz said:
Care to share the correct boot.img?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1d1QAtDjOMXDGlPwamfBD09IJW-P7Bs0D/view?usp=sharing

Realme 7 RMX 2151 Wi-FI Bluetooth ISSUE

Hello everyone, I have recently flashed new custom ROM on my device - Realme 7 rmx 2151 and everything went as planned. I used unlocking and flashing guide new from XDA webpage... I flashed PixelPlus UI3.9 from here, XDA ... I was really loooking forward to try new things etc... and do not know where I messed up but can not turn ON Wi-Fi and BLUETOOTH. Please any advice ? Thank you in advance...
Could be a problem with the rom,try to flash evolution x to see if that works
Ok. thank you for advice, I will do that within a next two hours. lets try...
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Try restoring the persist partition.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Were you on a.87 before flashing the ROM?
SubwayChamp said:
Try restoring the persist partition.
Click to expand...
Click to collapse
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
OrthodoxOxygen said:
Were you on a.87 before flashing the ROM?
Click to expand...
Click to collapse
Not sure buddy, but honestly can say either 87 or 91....
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
OrthodoxOxygen said:
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
Click to expand...
Click to collapse
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
SubwayChamp said:
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
Click to expand...
Click to collapse
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
RobertoSt25 said:
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
Click to expand...
Click to collapse
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
RobertoSt25 said:
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
Click to expand...
Click to collapse
You don't need to uy a new one. You just need to reflash the correct firmware, and then reflash the ROM you're trying to use after that.
SubwayChamp said:
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
Click to expand...
Click to collapse
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
alright I will do that, what would you recon, how to flash it ? I mean the best and the easiest way to do that...? Thank you very much.
RobertoSt25 said:
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
Click to expand...
Click to collapse
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
SubwayChamp said:
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
Click to expand...
Click to collapse
lovely, you are No,1, I will do that exactly the way you described. Thank you very much for that.
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
RobertoSt25 said:
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
Click to expand...
Click to collapse
You just need to flash a.87 back onto your device. Did you need to follow an elaborate guide to unlock your phone's bootloader, or did you just submit an application via the DeepTest APK? I need to know this in order to link you the correct files to flash.

Retrieving and Patching Your Boot.img for LG Wing

woops didn't put this in guides, sorry
This should work for any KDZ firmware of any LG Device, but figured I'd write this for the Wing, as so far, its the only LG phone I own and the one I'm most determined with
This is not a full Root Tutorial. This is a step in the correct direction though. These are the After-Steps, so bootloader unlock is still needed. Sorry
What You'll need
- KDZ Tools (see attachment -- virus total scan just because: https://www.virustotal.com/gui/file...zODc2ZTViOWQ1MTlmN2Q0NzFiMjI6MTYzNzgyMTYwNg==)
- Firmware KDZ file
- Magisk Manager installed on device that IS NOT your LG Wing (at least for me, explained below)
Instructions (video coming soon)
1.) Download KDZ Tools and extract them to a folder somewhere.
-- I usually make one on my external drive and drop stuff there, but desktop works too
2.) Download whatever firmware KDZ file you need
3.) Put that KDZ File in the same folder as the KDZ Tools
4.) Run "OneKeyExtraction.bat" and select Y if the KDZ is in the folder with this same file
5.) This takes A LONG WHILE and you need a good large bit of storage space available (50gb+) because the extraction goes raw format and some image files at first take up 20+GB as 1 file
6.) Once complete, you should have a folder named "F100X_usersigned_etc" ... open that to find your img firmware files. There's 31GB of IMG files here if its the Android 11 1020 KR FW
7.) Copy one of the boot.img to your device with Magisk Manager installed
-- The reason I stated on a different device, is that at least for me, Magisk Manager kept failing to patch on my LG Wing. When I put the boot.img on my OnePlus 7 Pro 5G, it patched just fine
8.) Open magisk manager, select Install, Select and Patch a File, select the Boot.img and patch it
9.) Once patched, that's a rooted boot.img, pull it off your device back to your computer and hold on to it for when we get a way to flash it and root the device!
root theory:
Interupting the LGUp flashing process of firmware when it gets to boot partitions to load custom boot.img's. How to do this exactly, not sure. If there's a way we can re-kdz these files from KDZ tool, that might work too
I can tell you right now, it wont work because the bootloader is locked. The hash of the patched boot.img on the phone won't match and you will get "Your device has failed a routine check, your phone is unbootable."
Sorry to debunk your theory. We need a firehose and a engineering bootloader.
Leronex_1 said:
I can tell you right now, it wont work because the bootloader is locked. The hash of the patched boot.img on the phone won't match and you will get "Your device has failed a routine check, your phone is unbootable."
Sorry to debunk your theory. We need a firehose and a engineering bootloader.
Click to expand...
Click to collapse
hey it was worth a shot
KaptinBoxxi said:
hey it was worth a shot
Click to expand...
Click to collapse
Sure need lg wing firehose , can help to find it??
Bahmale said:
Sure need lg wing firehose , can help to find it??
Click to expand...
Click to collapse
Don't even have a clue of where to look so I won't be looking for it
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
mercuris said:
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
Click to expand...
Click to collapse
you got a rare device then. I can't even load fastboot, just download mode for lgup.
mercuris said:
i've done it with
"adb reboot fastboot
adb flash boot_a boot_a.img
adb flash boot_b boot_b.img"
both boot img a & b patched with magisk and by the way the phone i bought come with unlocked bootloader
Click to expand...
Click to collapse
What model do you have? I.e. F100VM10i
Glad you got it working btw!
kaluna00 said:
What model do you have? I.e. F100VM10i
Glad you got it working btw!
Click to expand...
Click to collapse
screen shot in another section shows it was a verizon demo model by the looks of it. F100V
KaptinBoxxi said:
screen shot in another section shows it was a verizon demo model by the looks of it. F100V
Click to expand...
Click to collapse
This is from the Verizon model (non demo).
Also i accidentally added the software version earlier.
i accidentally delete some lg apps and the phone stuck in bootloop the other day so i restore the phone using lgup just selected the refurbished option, the phone restored still in unlocked bootloader mode
mercuris said:
i accidentally delete some lg apps and the phone stuck in bootloop the other day so i restore the phone using lgup just selected the refurbished option, the phone restored still in unlocked bootloader mode
Click to expand...
Click to collapse
Hi, are you willing to dump the bootloader from your phone? Because it looks like you have a development device, so it has an unlockable engineering bootloader that can be used to unlock other LG Wing and Velvet devices.
Wish39 said:
Hi, are you willing to dump the bootloader from your phone? Because it looks like you have a development device, so it has an unlockable engineering bootloader that can be used to unlock other LG Wing and Velvet devices.
Click to expand...
Click to collapse
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
mercuris said:
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
Click to expand...
Click to collapse
Others can help on our discord server, I'll admit I'm not well versed on dumping partitions through stuff like ADB.
https://discord.gg/Zw9Uk9DWE2
mercuris said:
i dun mind just i dunno how to do that, if you can guide me it would be nice, or you can show me the instructions
Click to expand...
Click to collapse
You can also contact @Leronex_1 he can help you with dumping the bootloader
will do what i can to contribute, no problem
mercuris said:
will do what i can to contribute, no problem
Click to expand...
Click to collapse
Thanks, I recommend to join the Discord server though since me and Leronex are not always online on XDA, we are more active on Discord since its a live chat platform, not a forum like XDA. If you dont have a Discord account you can just create one.
If anyone else is reading this you are welcome to join the server as well.
Wish39 said:
Thanks, I recommend to join the Discord server though since me and Leronex are not always online on XDA, we are more active on Discord since its a live chat platform, not a forum like XDA. If you dont have a Discord account you can just create one.
If anyone else is reading this you are welcome to join the server as well.
Click to expand...
Click to collapse
will do
kaluna00 said:
This is from the Verizon model (non demo).
Also i accidentally added the software version earlier.
Click to expand...
Click to collapse
Reason I guessed demo device is because of the 0'd IMEI, but I guess as a dev device, 0'd imei is gonna be there too
Any progress on this? Sounded like you guys were making some good ground and then the thread went a little bit cold. No pressure. Just checking in. Thanks and Merry Christmas!

Question Remember theisonews and isoleeted

BEWARE
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
DemonLoader said:
Has this changed, or is it still unsafe? I'm just getting back to checking on on rooting the GN2200 and I am on the C.11 update currently.
Click to expand...
Click to collapse
I tried rooting c11 and I ended up bricked.
Could you make a rom backup of your device so i can un brick un mine
If you can guide me in the current set of utilities, I certainly can. I just don't stay that current until I'm ready to utilize, is all.
Im learning now
You have to be rooted to backup the firmware
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
immortalwon said:
I would never try to root a newer phone if it didn't support custom recovery like TWRP in-case something goes south.
Click to expand...
Click to collapse
There is custom recovery for this device. Buts its tricky to get it installed. The guide was deleted when the forum police banned scarlet wizard who wrote the guide
Have you tried installing KernelSU, and simply booting from fastboot in order to get your backups? Then once you have them, you can play with rooting again? I just learned of KernelSU this year, and I think it's a remarkable tool for getting our backups before flashing anything.
bricklife4me said:
BEWARE
Click to expand...
Click to collapse
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
halloweenm925 said:
def works flash this magisk patched A12 boot!
A12 C.11 magisk patched boot (working ON (GN2200) ONLY!!!!)
Click to expand...
Click to collapse
Ya i got rooted too. I don't know what happen the first time
bricklife4me said:
Ya i got rooted too. I don't know what happen the first time
Click to expand...
Click to collapse
Do you just flash the boot img, or is there some thing else aso?
yacopsae said:
Do you just flash the boot img, or is there some thing else aso?
Click to expand...
Click to collapse
Fastboot flash boot <patches boot.img>
I dont need to disable dm-verity or anything? I just want to make sure before I try to flash a patched boot.img
Why remember them?
Damn they band Scarlet for real?
Use the script in the other thread
CoryBlaze said:
Damn they band Scarlet for real?
Click to expand...
Click to collapse
Yes they bannned my original account
mobile_sensei said:
Why remember them?
Click to expand...
Click to collapse
Cause that was a very fun forum
bricklife4me said:
Use the script in the other thread
Yes they bannned my original account
Click to expand...
Click to collapse
You still alive, how would I flash my IMEI back I lost it during the brick, but used your guide to restore my brick but IMEI is on back of the phone my carrier suspended my account because I didn't have the IMEI do you know how permanent add back

Categories

Resources