So I screwed up, apparently more so than I thought.
I got a new, fancy Pixel 4a 5G and wanted to install Magisk on it. I didn't do any rooting/flashing since I got my OnePlus One a couple of years back, been running vanilla since then, now I wanted to try something else, and I screwed up. I unlocked the bootloader, installed Magisk Manager, patched a boot.img and flashed that patched boot.img on my phone. Only issue is, I used the wrong boot.img, I had accidentally downloaded a Pixel 5 image (missclicked in frustration after several failed downloads), not Pixel 4a 5G. Upon discovering my mistake, I flashed a clean boot.img, this time from a Pixel 4a 5G image, thinking it would make everything return to factory image. But I'm still stuck on the white "Google" boot screen, no joy here. I can still access fastboot, recovery and rescue modes, but trying to flash a factory image fails, returning a "failed to load image [image name] not enough space". I don't buy that the phone doesn't actually have enough space for the image, as it's literally brand new and I already wiped user data before.
Does anyone have any ideas what more I could do? I can try to provide logs if required. Sadly, I do not have any nandroid backups, as TWRP isn't available for the 4a 5G yet.
Is there any way to force a wipe and reinstall a clean factory image?
UPDATE: Solved the issue. After updating my platform tools (had an older version set up system-wide without noticing), I attempted to reinstall the factory image as provided by google again and it actually worked, without any "not enough space" errors.
Related
So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.
Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)
I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.
Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.
So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.
I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
@chrcol ..., but you've issues
chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.
One of my slots/partitions does not work anymore. Both should have the same OOS with blue_spark kernel and his TWRP mod - but slot A doesn't boot (stuck on the "bootloader unlocked" warning screen, doesn't reboot as far as I can tell) and when I have it active, the recovery doesn't prompt me for my PIN - and all user data is still encrypted. Slot B works flawless though.
(It's been like that for a few months already, I just forgot about it since I haven't rebooted my phone in a while.)
What course of action should I take?
I've looked before and found this thread - https://forum.xda-developers.com/oneplus-6/help/bootloop-one-partitions-t3809859
But honestly, I'm not sure if it's the same issue. I can't tell if it's bootlooping and I assume it isn't, since it's stuck on the warning.
Not very sure how I managed to do this exactly but I think it's because I forgot to remove my fingerprint lock etc. before flashing a new custom rom (or because I removed it directly after and switched partitions unintentionally? I have no clue anymore)
I've back most of my important data up, so I'd be open to basically reset everything, if that's the only way.
Would the appropriate way about this be to just go into recovery and tell it to wipe everything?
Use the MSM tool to flash a fresh image onto your phone. Then, once you're booted, flash an ota image (this will be flashed onto the other slot) via the oneplus local system update option.
This should work as I have faced your issue a couple of times while changing roms.
Personally I would just start fresh and use the MSM tool. Read a post somewhere on Reddit yesterday when I was in the same boat and some guy said you could clone slot A with B and vice versa using TWRP or some Motorola based tool, but seeing as it would have been quicker and cleaner to just do it the MSM route, I went for that.
It sounds like a security patch incompatibility. I don't think there's any way to fix it besides reformatting that slot. You will of course lose all your data.
I downloaded a Magisk module to test out that purported to bypass DRM of netflix, Amazon, and a couple others and it put my phone into a boot loop. I installed a recovery magisk module zip for recovery that allowed me to disable the module from TWRP but it didn't matter because it just stopped the module and didn't replace the changed DRM file. After that I just gave up and fully formatted my phone with the All in One tool using "Decrypt phone / erase all data" and then installed a fresh stock ROM image via fastboot. The problem is, even after doing all of this, the DRM file that this module changed is still changed and I can't use streaming services and my phone is incredibly unstable. When I open Netflix for instance, it says I need an update and when I go to the play store it tells me "Netflix is not compatible with your device". Also, even after a full wipe, Nova launcher is still installed, and it's not supposed to be, I have no clue how these files are persisting through a full wipe. I've been tinkering with my phone for over a year now and this is the first problem I've found that not even fastboot can seem to fix. I'm on Tmobile and originally was able to unlock my bootloader by flashing Android 10 Developer preview 3, which they accidentally allowed you to unlock the bootloader with. I did that to unlock my bootloader then rooted and I've been using international ROM's ever since. I'm worried if I have to go back to Stock tmobile ROM I won't be able to get my bootloader locked again, and I still have no clue if this will even fix the issue. Does anyone have any clue how to fix this? If you search "drm" on magisk modules you'll find two things, one that removes all drm, and one from 2019 that attempts to bypass it. (I figured I'd test this out to see if I could watch Netflix in 1440p with my bootloader unlocked and didn't expect it to work, just didn't expect it to find a way to soft brick my phone) I'm using the 2019 one. Is it possible if I re-root my phone to somehow aquire the original DRM files this thing changed and replace them? Are these not included as part of a stock ROM? I don't understand how I can't fix this. My last plan is to reinstall TWRP and wipe literally every option on there then flash a ROM via fastboot, but I doubt it's going to work if formatting the entire phone doesn't work
Edit: Installed TWRP, wiped literally every option so I didn't even have an OS anymore, used fastboot to decrypt / erase all data then when installing stock ROM I chose again to wipe all data. If nova launcher and the changed DRM persists through this I'm going to be completely stumped. The only thing I can conclude is that somehow my phone is not actually fully wiping itself even though I'm using 3 different methods to do it
Edit 2: This still didn't work. I think I'm gonna have to use the MSM tool and go back to tmobile stock. If I flash far back enough I should in theory still be able to flash Android 10 DP3 and unlock my bootloader again, it's just gonna be an unexpected pain in the ass task to deal with today
Edit 3: Thank god for modified msm tool, I didn't know they were able to modify it to convert your tmobile phone to international and unlock the bootloader. This is going to be much easier than anticipated as long as doing this actually fixes my drm files and really wipes everything
Edit 4: Even using MSM tool to install a factory international ROM fixed the Netflix issue but somehow Nova Launcher is persisting through every single kind of wipe I've done lol. Despite the bootloader being locked (wasn't supposed to be) after this update, Netflix still wouldn't play in HD which is kind of odd. I'm now going through the process of installing Android 10 DP3 and unlocking my bootloader then downgrading back to pie to root and install TWRP again. I'm just going to have to accept that Nova Launcher is a part of my phone now lol
Maybe I'm wrong but didnt op7 pro have an irreversible e-fuse that once triggered with root it wiped out the ability to see HD forever ? Something to do with downgrading widevine drm levels if I remember correctly... The nova thingy I cant explain but hey it could be worse you could be stuck with Microsoft's launcher [emoji1787]
Sent from my GM1913 using Tapatalk
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Just a thought that crossed my mind, could it be that Nova is surviving as a system app in A or B slot? Are you sure you are wiping system in both slots?
Sent from my GM1913 using Tapatalk
Hello there, I need help :/
My Poco F2 Pro is stuck on a Boot loop, without any obvious reason.
The device became really laggy and painfully slow. Because of that, I wanted to restart it. But now it is stuck in a boot loop
I rooted the device using Magisk Canary 1 week ago. Yesterday, I installed the custom recovery "TWRP".
And with Titanium backup I froze a few system apps... which didn't seem to be so important (I googled them beforehand)
Today, I tinkered a little bit with AF+wall (which still doesn't really work), but except of this, nothing else.
I tried (using TWRP) to wipe the Data and Cache, but it fails "unable to mount /data/media/TWRP/.twrps
Also tried to change file system to ext2 and then back to ext4, but it again says "unable to mount"
What can I do now, resp. how can I get my device? I made a backup using Titanium, but it still is in the internal storage xD
OK.. I will give up the backup, I have all the important files backed up earlier anyways...
My plan is now to use MiFlash to flash the newest MIUI version [V13.0.2.0.SJKEUXM] onto my device.
Only fear is.. I have TWRP installed, and as far as I know, it does not support android 12... what will happen if I do this nervertheless?
And I want to get rid off TWRP nevertheless, so it would be perfect if it just gets replaced with the stock recovery...
sounds like a plan. still any question?
Nope, thank you, everything worked out as planned
I just got a 6a. I have an older Pixel 3A XL that I am trying to trade in. The phone was rooted (but I just uninstalled Magisk) and I never took most updates so the phone is still on Android 10. I am wondering which stock firmware I should download to get this back to factory settings so I can lock the boot loader?
Do I need to download the newest Android 12 OTA update and then flash a stock rom or should I just download an Android 10 stock from and flash that?
Android 10 has less "surprises" in it... scoped storage will be fully enforced in 12.
dr0832 said:
I just got a 6a. I have an older Pixel 3A XL that I am trying to trade in. The phone was rooted (but I just uninstalled Magisk) and I never took most updates so the phone is still on Android 10. I am wondering which stock firmware I should download to get this back to factory settings so I can lock the boot loader?
Do I need to download the newest Android 12 OTA update and then flash a stock rom or should I just download an Android 10 stock from and flash that?
Click to expand...
Click to collapse
If you are trading it in, just back up anything you want from it, factory reset it and flash a factory image to it. Then run the OEM bootloader lock command. You can also go into Developer Options and turn off bootloader unlock and reset it again. Doesn't matter which factory image because you are not keeping the phone or selling it. When they get the phone, they will likely reflash the latest factory image to it anyway.
To reiterate, flash the factory image, not the OTA image. Factory images contain everything, including the modem/bootloader/etc. That way everything is likely to work together properly. Mismatched firmware/modem/bootloader from flashing an OTA can be a bad day.
So if I had my 4a rooted a couple years ago, but went back to stock, I should be able to just factory reset, right? No flashing needed? Does it matter if you send it back with bootloader unlocked?
tcat007 said:
So if I had my 4a rooted a couple years ago, but went back to stock, I should be able to just factory reset, right? No flashing needed? Does it matter if you send it back with bootloader unlocked?
Click to expand...
Click to collapse
I think you should re-lock the bootloader, just to be on the safe side; it's an easy thing to do. I had to do a warranty replacement for my Pixel 4 XL a few years ago and the google technician told me to relock the bootloader when returning the 'defective' device.
Google is not going to deny your trade in due to being rooted. This is not a warranty replacement! The only requirements are that the screen turns on and is not cracked.
Just go into settings and do a "factory reset" and turn the phone in. Doing anything more is simply a waste of time.
sic0048 said:
Google is not going to deny your trade in due to being rooted. This is not a warranty replacement! The only requirements are that the screen turns on and is not cracked.
Just go into settings and do a "factory reset" and turn the phone in. Doing anything more is simply a waste of time.
Click to expand...
Click to collapse
Yep, Im sure all our old devices are just promptly going in the trash or possibly to a donation project so theyre not going to care.
The best way to return your device to bone stock is with the Android Flash Tool. Ensure you check the "Force flash all partitions" and "Wipe device" boxes, as well as "Lock bootloader' if desired.