Even with the latest firmware. I get the error where it says image interfering with another when I install the firmware with device flasher. Before I had no problem?
Looking at the CalyxOS website, their lastest build is December. Not january.
Install December firmware, then flash Calyx.
I figured out what the problem was. It was that I forgot to flash it with platform tools and adb.
Related
Hey, its been a while since I have updated my phone. Its v9.0.6 and I wanted to update it to the latest. I figured id run the command all.bat that will freshly reinstall the stock 9.0.6.
I downloaded the latest stock firmware from the website. After I update, what twrp and other instruction will I need to be able to access root and TWRP again? What Twrp image and I flashing to my phone?
Thanks, Brad
Hello, I do suggest the new update as many bugs has been fixed.
The rooting/twrp procedure is quite easy I suggest you to have a look at the guide
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
I've been using the "mauronofrio twrp" but I'm sure that the last twrp version on the official website will work properly.
I changed the recovery. Unfortunately I now have a boot loop and have already tried everything to get rid of it. E.g. dm verifi zip 6.0 and 6.1. I've also spoken to Samsung, but they don't want to send me the Stock Recovery. And much more. The stock recovery is now my last hope to get the J530F working again. Can you find them?
SM-J530FZDDDBT
First Update with Android 9
October 2019
Tschik said:
I changed the recovery. Unfortunately I now have a boot loop and have already tried everything to get rid of it. E.g. dm verifi zip 6.0 and 6.1. I've also spoken to Samsung, but they don't want to send me the Stock Recovery. And much more. The stock recovery is now my last hope to get the J530F working again. Can you find them?
SM-J530FZDDDBT
First Update with Android 9
October 2019
Click to expand...
Click to collapse
www.samfw.com
The model name is in the recovery. That means that every little descendant gets its own recovery. Unfortunately my model is not included and this website only seems to have firmware and no recovery. Does anyone have any ideas?
Unfortunately I have to be exactly the same recovery, otherwise the kernel won't work.
extract for you soon busy now
What you mean?
in the firmware version SM-J530FZDDDBT you provided, I can find the excact entire stock and extract the stock recovery.
Really? I have don't know it. I will try it. But the website have not this Modell.
oh then I will downlosd at some slow download sites, I recommend samfw only it is fast
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons
I have an unlocked boot loader and I know how to flash Graphene OS, Calyx OS, and unofficial Lineage build but have problems with flashing Evolution X(as it's only an OTA update), Satix OS and Stag os. Those others I'm having trouble with. I also put sdk platform tools as path. What am I doing wrong? And I could go back and install December and January stock firmware and still get errors.
UltimateGamer83 said:
I have an unlocked boot loader and I know how to flash Graphene OS, Calyx OS, and unofficial Lineage build but have problems with flashing Evolution X(as it's only an OTA update), Satix OS and Stag os. Those others I'm having trouble with. I also put sdk platform tools as path. What am I doing wrong? And I could go back and install December and January stock firmware and still get errors.
Click to expand...
Click to collapse
Assume you are installing EvoX via ADB sideload & not fastboot (per the instructions), so maybe try the previous platform tools prior to Feb.
Yes. Do I set them to path? As I already know how to do that.
UltimateGamer83 said:
Yes. Do I set them to path? As I already know how to do that.
Click to expand...
Click to collapse
Yes, If you are using Platform-tools 34.0.0 downgrade to V33.0.3. There is a bug on the latest platform-tools. There is a thread on this issue with information.
schmeggy929 said:
Yes, If you are using Platform-tools 34.0.0 downgrade to V33.0.3. There is a bug on the latest platform-tools. There is a thread on this issue with information.
Click to expand...
Click to collapse
Could you link the thread here please? I was about to update my platform-tools later today
xunholyx said:
Could you link the thread here please? I was about to update my platform-tools later today
Click to expand...
Click to collapse
June 13, 2023 TQ3A.230605.012 Global - Platform-Tools v34.0.3 has a different bug- Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Hello guys!
Something wrong happened with my blujay, I need ur help...
So here's the complete story:
1) since december I didn't have OTA update, I don't know why, and the system was telling me it was outdated everyday but up to date in the update menu. so I decided to download the latest OTA bluejay-ota-tq1a.230205.002-1ec64b58.zip and apply it.
2) that worked nice, it booted up updated to this version. But proposed me another security update to get me to march 2023 security update.
3) Allright, security update done, but without root. So I donwloaded the full image corresponding to the OTA i made, bluejay-tq1a.230205.002-factory-1b04ccc9.zip, extracted the boot.img, patched it with magisk 26.1, then flashed it through fastboot.
4) this is where things get naughty, I had bootloop. I imagine this boot.img was correponding to my OTA update, but then another update was done, and the boot.img was wrong for this one.
5) I tried to reflash the patched and original boot.img, same. I tried to reapply the OTA, same, still bootloop.
6) I just tried to patch the full image, removing the -w from the flash-all.bat to not wipe my data (the whole point is that I can't loose all that), and still the same, I have a screen from android recovery saying it cannot load the system and proposing me to wipe, which I don't want.
What should I do ? Save me please!!
You updated from the Feb 2023 patch to the March 2023 patch in step 2. You then downloaded and patched the Feb 2023 boot.img file and applied it, with the system being at the March 2023 update. This is where the issue is. You need to download the March 2023 image and flash the boot.img from this. It is possible though, that you are at the April 2023 patch if you did this very recently.