Long time flasher here, but I'm trying to do something I often don't do - go back to a stock rooted setup.
When I try to flash the factory images (flash-all.sh) it always errors-out saying it can't find the system.img. So I fastboot flash each img manually. The system boots fine.
But as soon as I flash TWRP into the recovery partition, there is an error message at boot that the system is corrupted and to wipe the data.
What's the trick to get this working? Do I need to flash an insecure boot img first?
Thanks for the info!
That system corruption message is normal when totally stock. You need to flash a modified boot image or custom kernel, which can be found in the forums. That will resolve the corruption message.
Related
Does anyone has been in this situation?
With ROM V30B, flashing custom recovery (CWM/TWRP), then reboot recovery.
Is it enter the recovery, or got Security Error?
What I want to say is if reboot recovery working, then I might thinking by flashing via recovery each binary of
gpt1
x-loader
u-boot
boot.img
divxkey
Can we do that?
Or might be it can be done without entering recovery? So I'm able to going back to v20 with custom recovery.
Thanks. :fingers-crossed:
Bring me news bro. Didn't succeed yet on V20?
I haven't tried CWM on stock so pardon my post. If it boots to CWM (when you reboot to recovery) but get Security Error upon booting the device. Making it clear cause people here might not understand.
If it did boot to recovery, you can flash all of those 5 items you mentioned as I did flashed them before with KU5900 build.
Nevermind
Not working.
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.
I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much
Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.
What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.
So I was restoring the stock boot image so I could flash magisk, and I ran into a bit of a problem. I tried booting it up after flashing, and it's stuck on the boot screen so I'm assuming I flashed a bad boot. This wouldn't normally be a problem, except that my volume up button doesnt work meaning I can't boot back into recovery mode/bootloader. Is there a way to get to the bootloader or recovery screen without using the volume up button?
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
frosted.efizzle said:
I think you might have accidentally flashed the stock boot image to your recovery. Have you checked the option to flash the boot image and not recovery?
Click to expand...
Click to collapse
I'm pretty sure I flashed to boot, I can turn it on and it just shows the blu logo. Before I had a custom boot image though and it's not showing that anymore though.
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
frosted.efizzle said:
I'm assuming that custom boot image came prerooted right? You might need to flash the rom that came with the custom image to boot. An easier way to get Magisk which I've done is to flash rom, then flash the unSU zip to remove traces of root then you can flash Magisk like normal.
Click to expand...
Click to collapse
I would do that, except with the volume up button broken I'm unable to get to recovery mode, and without being able to boot into the system I can't use adb
Hello,
So I did a mistake by flashing TWRP into the boot partition... Now whenever I reboot my phone it enters TWRP. How can I fix that or is it bricked? I can't find anywhere on the Internet stock boot images, only some modded kernels or something like that. Can anyone tell me how can I get stock boot.img and flash it so that I can use my phone again?
Aspect13 said:
Hello,
So I did a mistake by flashing TWRP into the boot partition... Now whenever I reboot my phone it enters TWRP. How can I fix that or is it bricked? I can't find anywhere on the Internet stock boot images, only some modded kernels or something like that. Can anyone tell me how can I get stock boot.img and flash it so that I can use my phone again?
Click to expand...
Click to collapse
Downllad zip or tgz file for your extract firmware, ectract boot img and then flash by fastboot to boot