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
Related
This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?
<removed>
I think Moto Moto don't like us
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
gregory678 said:
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
Click to expand...
Click to collapse
Propably you patch wrong boot image, try to extract from your device stock
tys0n said:
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
Click to expand...
Click to collapse
It's not universal path so i BOLD the path to change
[email protected] said:
It's not universal path so i BOLD the path to change
Click to expand...
Click to collapse
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
tys0n said:
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
Click to expand...
Click to collapse
Edited
[email protected] said:
Propably you patch wrong boot image, try to extract from your device stock
Click to expand...
Click to collapse
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
It should work. I've patched boot after every update without problems.
XT1941-4
Sent from my moto one
[email protected] said:
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
Click to expand...
Click to collapse
I would like to, but is there some way of backing up stock ROM? I know that current version of TWRP has some issues with /data partition, that's why I ask .
And what about installing this ROM? Would I need to use that TWRP we have now? Is it safe?
tys0n said:
It should work. I've patched boot after every update without problems.
XT1941-4
Click to expand...
Click to collapse
Well, you have different software channel, I think that's the only reason why it works for you and it doesn't work for me . OPENEU seems to be bulletproof. (I have XT1941-4 too)
Someone correct me if I'm wrong, maybe for someone with OPENEU it does work.
I Request close due to failures
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Raygen said:
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Click to expand...
Click to collapse
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
pankspoo said:
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
Click to expand...
Click to collapse
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Raygen said:
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Click to expand...
Click to collapse
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
sakarya1980 said:
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
Click to expand...
Click to collapse
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Raygen said:
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Click to expand...
Click to collapse
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
@Raygen did you get through with your imei repair? i have a similar issue.
BusterCZ said:
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Click to expand...
Click to collapse
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
sakarya1980 said:
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
Click to expand...
Click to collapse
Tried two times already, no change.
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Send it back to OnePlus sadly.
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Tried two times already, no change.
Send it back to OnePlus sadly.
Click to expand...
Click to collapse
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Click to expand...
Click to collapse
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
pankspoo said:
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Click to expand...
Click to collapse
BusterCZ said:
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
Click to expand...
Click to collapse
I would like to use Sp flash but I don't know where I could find the files for the Nord 2 to use with it. Like the scatter file and the firmware in Raw format
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Might help ! Check,.
U need to get UMT dongle , Ultimate Multi tool software.
Hi friends. Bought my one on *site name*. China version. How to install Magisk root? I tried to boot patched boot.img... didn't help
have you unlock your phone?
AmbazidA said:
have you unlock your phone?
Click to expand...
Click to collapse
Yea
Rezinochka said:
Yea
Click to expand...
Click to collapse
okay, was the flashing of patch boot image not successful? or what error did you find?
AmbazidA said:
okay, was the flashing of patch boot image not successful? or what error did you find?
Click to expand...
Click to collapse
In adb it wrote "OKAY". But in magisk root haven't installed.
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
If for some reason it’s not already installed, install it.
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
Sorry, didn't understand wdym
Sirs. With your permission, we will continue tomorrow morning. I am forced to leave you for an indefinite period for the time being.
Ok. Good morning "Vietnam"
AmbazidA said:
may be you can try this; launch magisk app already installed in the phone and select direct install(recommended), wait for the process to complete and reboot. it might help
Click to expand...
Click to collapse
I didn't understand wdym
Is the magisk app currently on your device?
If so, enter it, and clcik on the install button. Then click on”direct install”
Arealhooman said:
Is the magisk app currently on your device?
Click to expand...
Click to collapse
Yes
Arealhooman said:
If so, enter it, and clcik on the install button. Then click on”direct install”
Click to expand...
Click to collapse
I patched boot.img earlier
this video will walk you through rooting the Redmi Note 12
-
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
Thx, i will try
Enddo said:
this video will walk you through rooting the Redmi Note 12
-
Click to expand...
Click to collapse
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Rezinochka said:
i tried with different versions of rom and magisk. So it doesnt work. And in video he flash patched file to the boot_a. I can flash it only to boot_b
Click to expand...
Click to collapse
it will flash to whatever your current partition is set to. some will be set to the _a partition and others will be set to the _b partition. it all depends on how many OTA updates you have installed (or if you've manually switched partitions for some reason)
the video does work, my Redmi Note 12 is rooted right now
IDK if it will work or not. But at least you could try. Someone suggested to patch init_boot.img on the Redmi note 12 4g forum.
Actual Post
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