Related
Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?
ViperX85 said:
Phone was on stock 7.1.1, July 1st patch with TWRP installed. I've wanted to remove TWRP in oreder to receive OTAs so I flashed stock 7.0 boot.img and recovery and now my phone is stuck in bootloader with bad key message when I try to start the phone. Flashing modified logo.bin didn't help. I'm guessing I need correct stock boot.img. Any ideas?
Click to expand...
Click to collapse
It should be this one, I just have DL it from Motorola 3 days ago
https://androidfilehost.com/?w=profile&uid=529152257862699209
@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip
shamu17 said:
@fablebreton
Hi, what is the difference between these files?
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_1.zip
ADDISON_NPNS26.118-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC_2.zip
Click to expand...
Click to collapse
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched
fablebreton said:
It is the same firmware, Second file + third = First file. Just smaller zips
because DL 1,8G sometimes can be difficult, and anyway we have to unzip to flash with fastboot.
But if you have a good internet connexion, just DL the first file, it is the original one, untouched
Click to expand...
Click to collapse
Thanks for sharing, regards
For whatever reason OnePlus removed the 10.5.8 update from their server. Therefore we can't patch to boot img.
The steps I took were
1. Patch 10.5.6 boot the img in fastboot
2. Reboot into system setup magisk
3. Reboot again in fastboot
4. Boot magisk patched img
5. Go into magisk and install and choose direct install
6. Profit with a 10.5.8 device without the wifi/gps/Bluetooth issues.
Thought I'd share my experience as I bought second hand and it had the latest update and couldn't find the download link to the full system update.
Might want to mention which Magisk, the known problem with Canary?
Also why patch 10.5.6 and not 8
dladz said:
Might want to mention which Magisk, the known problem with Canary?
Also why patch 10.5.6 and not 8
Click to expand...
Click to collapse
He dont have the 10.5.8.full rom to extract and patch the img
So he probably patch the 10.5.6 img , he just boot it temporary on fastboot , going to magisk ,installing magisk and when he's rebooting , he's on 10.5.8 rooted..
Here's stock boot for 10.5.8IN11BA if anyone needs it https://mega.nz/file/sb4WwSBS#jrCL7tek0SLbynTqbPU-s_j5g0cKFRsC4u7DR7S7sCI
cultofluna said:
He dont have the 10.5.8.full rom to extract and patch the img
So he probably patch the 10.5.6 img , he just boot it temporary on fastboot , going to magisk ,installing magisk and when he's rebooting , he's on 10.5.8 rooted..
Click to expand...
Click to collapse
Can't you get it from the updater?
dladz said:
Can't you get it from the updater?
Click to expand...
Click to collapse
Not if you have already updated via the OTA..
He probably got the OTA ( full zip) install it and then boot it..
If you've updated via local upgrade , then the full ROM zip has been saved on internal storage ...
But the easiest way to update and keep root is to just take the ota through the updater..dont reboot go to magisk manager , install magisk on inactive slot , ...done...
Patched img only needed to root after unlocking bootloader ..
Not anymore....
Bought the device updated already and can't find the 10.5.8AA build at all on OnePlus
facing the same issue... if anyone have the 5.8 aa it would be a great help <3
empreror said:
facing the same issue... if anyone have the 5.8 aa it would be a great help <3
Click to expand...
Click to collapse
Patch the 10.5.6 boot IMG and the fastboot boot <patchedmagisk.img>
Setup magisk and reboot into bootloader again to boot the patched image
Then go into magisk and do direct install and finally have working wifi etc.
10.5.8AA Oneplus Pro8 boot.img
https://sourceforge.net/projects/op8pro1058aa/files/10.5.8AA.img/download
bigjailerman said:
10.5.8AA Oneplus Pro8 boot.img
https://sourceforge.net/projects/op8pro1058aa/files/10.5.8AA.img/download
Click to expand...
Click to collapse
Is this the stock boot.img or rooted patched img?
Aporzio said:
Is this the stock boot.img or rooted patched img?
Click to expand...
Click to collapse
Tried it, it's patched.
Aporzio said:
Is this the stock boot.img or rooted patched img?
Click to expand...
Click to collapse
Yes it is patched...sorry for delay
bigjailerman said:
Yes it is patched...sorry for delay
Click to expand...
Click to collapse
Not a problem. I'm glad you didn't answer lol. I ended up teaching myself how to pull the img files from a payload.bin.
JKurtz87 said:
Patch the 10.5.6 boot IMG and the fastboot boot <patchedmagisk.img>
Setup magisk and reboot into bootloader again to boot the patched image
Then go into magisk and do direct install and finally have working wifi etc.
Click to expand...
Click to collapse
Can you be please more specific? I am new here and want to know what does it mean boot temporarily ? This command will boot your device temporray and after reboot it disappear ?
fastboot boot <patchedmagisk.img>
HI All,
I've got my G710EMW on EU firmware (G710EM30b_00_OPEN_EU_OP_0707.kdz), all looks good but not sure how to root it. I'm not sure how but by flashing a different firmware my bootloader is now unlocked - says unlocked in Developer Tools, so I don't need to do that.
I don't want to mess it up can someone tell me which files I need to root this phone?
rash.m2k said:
HI All,
I've got my G710EMW on EU firmware (G710EM30b_00_OPEN_EU_OP_0707.kdz), all looks good but not sure how to root it. I'm not sure how but by flashing a different firmware my bootloader is now unlocked - says unlocked in Developer Tools, so I don't need to do that.
I don't want to mess it up can someone tell me which files I need to root this phone?
Click to expand...
Click to collapse
Search in the guides or ROMs section. Someone might have put patched boot image for 30b.
To do yourself, you need to extract boot_a and boot_b using qfil, rename to .IMG, put it in your phone, install magisk manager and patch the boot images. Then put patched images in your PC and flash using fastboot. Check ROMs section to know how to do that.
This method always works for me.
lefttobleed said:
Search in the guides or ROMs section. Someone might have put patched boot image for 30b.
To do yourself, you need to extract boot_a and boot_b using qfil, rename to .IMG, put it in your phone, install magisk manager and patch the boot images. Then put patched images in your PC and flash using fastboot. Check ROMs section to know how to do that.
This method always works for me.
Click to expand...
Click to collapse
After much googling I have managed to do this! And rooted my phone, my question is do I need to flash both boot_a and boot_b? Or just one, at the moment I have flashed only boot_a and I have root
rash.m2k said:
After much googling I have managed to do this! And rooted my phone, my question is do I need to flash both boot_a and boot_b? Or just one, at the moment I have flashed only boot_a and I have root
Click to expand...
Click to collapse
Well you are supposed to flash both....
rash.m2k said:
After much googling I have managed to do this! And rooted my phone, my question is do I need to flash both boot_a and boot_b? Or just one, at the moment I have flashed only boot_a and I have root
Click to expand...
Click to collapse
could you tell me how you did it? or post a link ... thanks
Ricky Almonte said:
could you tell me how you did it? or post a link ... thanks
Click to expand...
Click to collapse
I followed this guide and downloaded everything I need from there:
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-unlock-bootloader-root-g7s-t-mo-t4077105
The biggest issue I had was getting the partition manager to work in QFIL, it kept failing with sahara error - but just keep trying, put the phone back into 9008 mode (hold vol Up and vol down and power) and restart the QFIL app, eventually it will work.
Once you have read the image in QFIL, copy it onto you phone and use magisk manager to patch the image and then write the boot images back (both boot a and boot b).
That's pretty much it.
rash.m2k said:
I followed this guide and downloaded everything I need from there:
https://forum.xda-developers.com/lg-g7-thinq/how-to/howto-unlock-bootloader-root-g7s-t-mo-t4077105
The biggest issue I had was getting the partition manager to work in QFIL, it kept failing with sahara error - but just keep trying, put the phone back into 9008 mode (hold vol Up and vol down and power) and restart the QFIL app, eventually it will work.
Once you have read the image in QFIL, copy it onto you phone and use magisk manager to patch the image and then write the boot images back (both boot a and boot b).
That's pretty much it.
Click to expand...
Click to collapse
Thanks so much
I think you could use 9008
I followed these links
I can't get into EDL
I got into a firmware download page, but the device doesn't show as
Qualcomm HS-USB QDLoader 9008
It says LGE Mobile USB Serial Port
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.
If you made a mistake like doing fastboot flash boot init_boot
You have a bad boot now or boot loop, the solution is
Flash Boot files of the exact running OS version from fastbootD
This will fix the issue
I have extracted this from the partition backup application hopefully it will work for you
Boot Files below
Can you access fastboot? If not, it's hard bricked. You need to goto service centre or Get it flashed remotely by paying someone.
surajpai524 said:
Can you access fastboot? If not, it's hard bricked. You need to goto service centre or Get it flashed remotely by paying someone.
Click to expand...
Click to collapse
I can access fastboot and recovery
I need A10 least fraimware boot.img and init Boot and I think flashing this Will work
ahasae said:
I can access fastboot and recovery
I need A10 least fraimware boot.img and init Boot and I think flashing this Will work
Click to expand...
Click to collapse
did you get a full zip rom by chance? idk why it's so hard to find one or why Oneplus doesn't offer downloads from their site anymore....
What i find funny is that by following that guide 100% would have you up and running with root. This tells me following directions is hard to since we can only give directions and hope you can following them. Reading the full guide before proceeding with it. Step 6: BOOT the kernel. DO NOT EVER FLASH THIS PHONE!
SourPower said:
did you get a full zip rom by chance? idk why it's so hard to find one or why Oneplus doesn't offer downloads from their site anymore....
Click to expand...
Click to collapse
https://oxygenos.oneplus.net/6160_sign_CPH2451_11_A_OTA_0090_all_FVA3Ps_10100001_2.zip
I think this one
I am using version 2451, but I can not update to 13.1. Can you give me an answer?
gunzpro21 said:
I am using version 2451, but I can not update to 13.1. Can you give me an answer?
Click to expand...
Click to collapse
Try with oxygen updater app