So I recently updated my op3 to 3.5.2 Community Build of oxygen OS. It was working well with a few changes from the official builds but a little time passed and the 3.5.3 Community Build was released. Of course I wanted to update so I downloaded it and tried to update but when it booted into the recovery it froze on the logo. So I downloaded the update on the computer and flashed twrp to the recovery and booted into the recovery and it froze again. Currently i have no Recovery and no access to adb.
*When trying to flash a recovery it says it was done successfully but freezes when trying to boot into it.
Normal OS booting is unaffected.
When executing the command "fastboot boot recovery.img", to boot into the recovery without flashing it i get "(remote dtb not found)"
When trying to manually update the OS through "fastboot zip Update.zip", I get "(remote: data too large)".
I also tried to do "fastboot erase recovery" before issuing the flash command.
*In trying to fix this i flashed the boot image of 3.5.3 onto the boot partition but nothing happened and now the phone reads as 3.5.3 on 3.5.2 firmware :crying:
I tried to use SkipSoft ToolKit,custom and official twrp, and recoveries such as CWM.
This would probably be better placed into the, ONEPLUS 3 ROMS, KERNELS, RECOVERIES, & OTHER DEVELOPMENT, section but I can not post there yet. If anyone can help me or find a mod that knows about this problem it would be much appreciated.
Found a Solution
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Related
So, I was attempting to root my phone(CanvasA1- 4GB) today running stock android marshmallow(6.0.1) , I successfully unlocked the boot loader in fastboot using adb, after which I flashed TWRP recovery, Which was successful but then, When I rebooted into recovery, I saw my old stock google's recovery running , I tried 2-3 more times flashing the recovery in fastboot but the probem was still the same :crying:. Then I came to know that we have to flash a special type of boot img of some 17.5mb approx, When I attempted to flash this "boot" image, I received an error saying file size too large, Hence I couldn't flash it, I am still running the stock recovery, With my bootloader unlocked, I need to root my phone, Please help someone, Thanks in advance .
http://forum.xda-developers.com/cro...-master-tool-unlock-bootloader-t2997696/page1 use this tool and flash custom recovery simple
You can search for Android One Toolkit. Iwas encountering the same problem but this app solved my Problem.
Sorry dont have Link for the Same.
Same here. I unlocked the bootloader successfully and flashed TWRP recovery. But it shows system/default recovery only. Now stuck in bootloop.
Tried clearing cache/date etc. nothing worked. Don't know what to do.
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
i had this problem the other day, fixed this by flashing the modified recovery from a post here turn it off the booted it up by holding vol down + power and somehow it worked i was able to go into twrp
innocentwoolf said:
I was on OOS community build 3.5.3 with modified twrp-3.0.2-19-oneplus3.
I wiped everything except internal storage after that I tried to flash official TWRP.
After installing official twrp via modified TWRP. Niether I can boot into my recovery nor able to install any recovery via fastboot.
it I use "fastboot flash recovery recovery.img"
after installing recovery with this command My bootloader get stuck then I have to again restart my bootloader.
please help
Click to expand...
Click to collapse
I have same issue it is called half-brick go to full brick post here (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
read whole post and prefer method 2 it will work like charm and i got when i am installing freedom os CE version and if it work then thank me
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Seagorilla2 said:
You're probably stil on 3.5.2 firmware which isnt compatible with official twrp. Try and get into fastboot and try flashing modified twrp again. Then reboot in recovery and flash 3.2.6 firmware (not the rom) from modified twrp. Then reboot and flash official twrp from recovery or in flashify app.
Click to expand...
Click to collapse
yes.. tried that only and it worked...
thanks
danxtian said:
are you stuck with a black screen when booting to recovery if yea then wits the same situation i was in.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56 that recovery helped me
Click to expand...
Click to collapse
that helped me to thanks
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
I'm desperate.
I've spent about 8 hours yesterday researching and fixing my phone which was stuck in a bootloop, I couldn't even get to TWRP.
In the end, what did it was the BLOD fix here in the forums. Flashed boot.img from stock 47Z, special TWRP from same thread and then from TWRP the EX kernel version 4.12 and then the latest OmniRom which I have used before. There it was again, working, even my 90 browser tabs were still there.
This is where I f***** up. My phone notified me at startup that I should flash vendor N2G47F (which is 7.1.2. - the latest OmniRom). Alright, phone is completely working, but still, couldn't hurt. Downloaded and flashed the wrong vendor (Factory Image 8.1.0) via TWRP because it was 3am and I didn't think anymore. And then... stuck at boot screen.
Alright, I discovered it was the wrong vendor image, so let's just flash the vendor again with the right version this time and it should work again, right?
Nope. Phone changed between bootloop-ing and just stuck on the Google loading screen with the open lock.
Okay, just start again from the beginning, you know what you did, so, easy. I thought.
This is what I did:
fastboot flash vendor vendorOPM7.1.2.-N2G47F.img
fastboot flash boot 47z…img [boot-img from BLOD-thread]
fastboot flash recovery twrp3_1_1_5X.img [also from BLOD-thread]
reboot-recovery
adb sideload 5xEX4…zip [also from BLOD-thread]
adb sideload omnirom_latest.zip [latest omnirom from official site]
reboot, should work because I fixed basically everything, right?
doesnt
remembered seeing boot.img getting flashed when sideloading omnirom (in the log that TWRP shows when sideloading)
flash boot.img again [from BLOD-thread]
still doesn't work.
cache was wiped either in twrp or fastboot after nearly every step.
I can't figure out anymore what the problem is. It worked before, and just because I flashed a false vendor it's not working at all anymore? I don't get it. Do you have any ideas for me? Many thanks in advance...
Hey all,
i had an older version of twrp recovery, and tried to flash the new one from here:
https://eu.dl.twrp.me/dumpling/
i opened poweshell from adb folder as usual while device is on fastboot mode, and used the command: fastboot flash recovery twrp-3.3.1-0-dumpling.img
It said "wrting...finished" in powshelll, but when entered recovery - nada, black screen of death.
then i tried flashing older version of twrp in the same way - and still go the same outcome =\
I currenly dont have ROM as well - so practically the phone is uselss. please guys, i need you're help!
Flash stock recovery and stock FW via ADB. If that doesn't work, try one of the dozen recovery tools on this forum.
Tried to flash OrangeFox and BluSpark recoveries, same issue =\
im running out of ideas here guys =(
Just managed to install stock recovery, and downloaded latest 9.0.10 OTA from here:
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
used LAA on adb.exe, and ran "adb sideload OOS.zip" while OTA zip is inside adb folder.
gives me "cannot read" error in powershell.
can someone tell me WTF is going on? how tf its even possible????