I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
I'm waiting for this as well
have you tried changing your active slot to the other one and see if you can boot?
use fastboot to see which slot you are on, then set it as the other and reboot
this will get your current slot
Code:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.034s
set your active slot opposite of what you are currently on (slot b)
Code:
fastboot set_active a
if you are on b, set it to a
if you are on a, set it to b
give that a try and see if you can boot. you can revert it back it it doesnt help. worth a shot though.
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
H4X0R46 said:
You didn't by chance flash a patched boot.img to your init_boot partition did you? That could very well cause a soft brick. For rooting, you would need to patch init_boot and flash to init_boot.
Init_boot isn't the same as boot.
Click to expand...
Click to collapse
I was very careful not to do that.
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Both slots need to be flashed the init_boot read my post
shootind5nukes said:
I was very careful not to do that.
Click to expand...
Click to collapse
Somehow you screwed up the boot partition that's why it won't boot
str8str said:
You flashed to boot not init_boot you need to reflash the boot.img to boot partition then boot your phone. Then you can go back and fastboot flash init_boot_a magisk_patched_init_boot.img
Then the same to init_boot_b do it to both slots you can extract the boot image with payload dumper and flash it to boot partition that should get you back running
Click to expand...
Click to collapse
I assure you I did not flash to boot. I am the type that reads instructions 100 times. I know I must have did something wrong but it wasn't that.
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
AkayamiShurui said:
https://www.droidwin.com/msm-download-tool-read-back-mode-create-oneplus-backup/
If you want to back up so you have all the bace files your phone will still connect to the MSM tool and you don't need to unlock the bootloader and you can extract every partition this way you can use the fast food tool to flash your phone this increases the recovery and boot image you don't need the payload.bin file
Click to expand...
Click to collapse
I forgot to mention this does work on bricked devices
Anybody with a corrupt boot.img that needs a factory one...
Does this one work ?
I would think it would work?
as it's a generic kernel image.
https://dl.google.com/android/gki/gki-certified-boot-android13-5.15-2023-02_r1.zip
shootind5nukes said:
I found on another page here the CPH2451 patched A07 boot. I followed all the directions to the letter. I have done this on my OP8Pro many times. After flashing init_boot (fastboot flash init_boot patched.boot.img) I'm now in a bootloop. I reset first the didn't setup anything after update to A07. Any help would be appreciated.
Anyone have another boot.img that's patched or maybe the stock boot?
Click to expand...
Click to collapse
Well if you trying to update to A.08 don't try flashing the boot.img I, I tried everything too and almost bricked my phone twice. if rooted you can't update with incremental updates in the USA ROM you only can do that with the EU ROM because they get a full ROM every time.
So I downloaded the EU ROM using oxygen updater App from play store then I used the OPLocalUpdate_For_Android12 App to force the update locally. The EU ROM looks the same to me so far but when we get a full ROM update in USA will switch back. Hope that helps
Related
So, I got the May OTA yesterday before I unlocked my bootloader this morning to begin the process of possibly switching to a custom ROM (or just rooting, not sure yet). I unlocked it and everything is fine, but I read that the new bootloader included in the OTA breaks root and that I should flash the April one, so I did and works fine but I noticed that fastboot says that it flashed the bootloader to slot a, as if there are multiple bootloader slots.
Is there multiple bootloader slots? Should I be concerned that if I flash a ROM and it switched to slot B that I will have no bootloader, or would the April one be there from the OTA I did when I got the phone? Also, is there a way to flash into the second slot manually with fastboot, if it exists?
admiralspeedy said:
So, I got the May OTA yesterday before I unlocked my bootloader this morning to begin the process of possibly switching to a custom ROM (or just rooting, not sure yet). I unlocked it and everything is fine, but I read that the new bootloader included in the OTA breaks root and that I should flash the April one, so I did and works fine but I noticed that fastboot says that it flashed the bootloader to slot a, as if there are multiple bootloader slots.
Is there multiple bootloader slots? Should I be concerned that if I flash a ROM and it switched to slot B that I will have no bootloader, or would the April one be there from the OTA I did when I got the phone? Also, is there a way to flash into the second slot manually with fastboot, if it exists?
Click to expand...
Click to collapse
Hello, there is a bootloader on both slots... This is the purpose of seamless update. And, in case one slot fails, it will boot the other one...
Check this: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
You can flash the same factory image to both slots...
Flash your current slot with flash-all method. After the phone reboot, reboot once again to bootloader and issue:
fastboot --set-active=b (if your current active slot is a)
fastboot --set-active=a (if your current slot is b)
fastboot reboot-bootloader
Flash-all on the second slot, done...
I don't really see the point though, if you don't have issues.
Flashing custom ROM on a Pixel is a little bit different than older Nexus devices.
Check this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I wrote a little guide for someone today who wanted to install Pure Nexus, SuperSU and TWRP: https://forum.xda-developers.com/showpost.php?p=72128419&postcount=2
You can use it as a base...
Good luck...
5.1 said:
Hello, there is a bootloader on both slots... This is the purpose of seamless update. And, in case one slot fails, it will boot the other one...
Check this: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
You can flash the same factory image to both slots...
Flash your current slot with flash-all method. After the phone reboot, reboot once again to bootloader and issue:
fastboot --set-active=b (if your current active slot is a)
fastboot --set-active=a (if your current slot is b)
fastboot reboot-bootloader
Flash-all on the second slot, done...
I don't really see the point though, if you don't have issues.
Flashing custom ROM on a Pixel is a little bit different than older Nexus devices.
Check this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I wrote a little guide for someone today who wanted to install Pure Nexus, SuperSU and TWRP: https://forum.xda-developers.com/showpost.php?p=72128419&postcount=2
You can use it as a base...
Good luck...
Click to expand...
Click to collapse
Ok, thanks for the info.
admiralspeedy said:
Ok, thanks for the info.
Click to expand...
Click to collapse
Just a question....wouldn't it be smart to have the same image on both slots in case one slot fails for some reason or another? And isn't there a way to flash to both slots simultaneously? @ admiralspeedy
canemaxx said:
Just a question....wouldn't it be smart to have the same image on both slots in case one slot fails for some reason or another? And isn't there a way to flash to both slots simultaneously? @ admiralspeedy
Click to expand...
Click to collapse
Hello,
I doubt you can flash simultaneously both...
Wait for confirmation, but I have seen people flashing boot img on slot a and b.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Guess this command can be used to flash bootloader as well...
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
I haven't tested it myself. You're on your own here...
Cheers...
Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
I just booted with an older one and flashed the latest magisk
Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t
ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.
SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !
hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.
smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.
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.