Hello fellows.
I have some problems with my find 7a, which have been a stable friend the past 2 years. I updated to the latest ColorOS yesterday, 2.1.5i. I started rooting my phone using the OPPO tool in the forums, and it worked fine. I then experienced the "insufficient space" problem and solved that by changing the partition method in developer options. This is where everything went nuts. All programs does of cause not work anymore because of the partition change, but I am no longer able to boot in to recovery, only fastboot, no matter if i power + up / down. I can no longer roll back or update to a newer ROM, and everything is gone on my SD and internal storage besides the absolute needed files to ColorOS 2.1.5i, but very slow. I have tried everything which I can think of: installing stock ROM and recovery, new ROM and recovery. No matter how I try to recover, nothing works. Now I just have a slow find 7a.
What can I do?
Best Regards
Devial
I have fixed this problem myself with some research.
Install stock ColorOS 1.2.7i recovery using adb/fastboot:
Code:
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
Thanks to darrenpauli.
I was now able to boot in to the stock recovery, but still had problems with installing any ROM, any custom or stock ROM.
I then rebooted into fastboot again, to see the "smiley" thing is gone, and the only thing on the screen was "Fastboot..." - progress!
So far I haven't been able to install any custom ROM or recovery, but this time I was able to install GUMMY TWRP 2.7.1.0 using the recovery installer for oppo find 7. I was now past the "failed" in fastboot/adb.
Since i completely wiped the phone, I no longer had any ROM installed, but I was now able to install the newest rom from CM using TWRP.
My phone is now rocking with the newest CM!
Software used.
Recovory_installer from OPPO
AndroidSDKSlim
ColorOS 1.2.7i
Newest CM
Related
Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....
I tried rooting my Swift and I ended up being stuck in TWRP 2.8.7.1.
All I did was fastboot the TWRP 28.7.1 Image.
I then decided not to do it, so I tried to reboot device.
It keeps putting me into twrp.
Could someone tell me how i get rid of this.
Sorry if the answer is obvious I'm a noob to this.
Greets Louis
ztva said:
I tried rooting my Swift and I ended up being stuck in TWRP 2.8.7.1.
All I did was fastboot the TWRP 28.7.1 Image.
I then decided not to do it, so I tried to reboot device.
It keeps putting me into twrp.
Could someone tell me how i get rid of this.
Sorry if the answer is obvious I'm a noob to this.
Greets Louis
Click to expand...
Click to collapse
- on which firmware were you (COS12.1 or COS13.0)?
- how exactly did you flash twrp?
You can always revert back to stock by flashing from
cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip
or
cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip
as folows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Thanks for the response.
I flashed back to the original recovery and everything works fine.
I'm currently on COS 13.0.
Is there a safe way to root my Swift or get CM running safely.
I've tried a couple of methods on here, but they didn't seem to work.
I also reallly don't want to brick my phone since it's the first decent smartphone I have.
I know the basics like how to use adb and fastboot, but I'd really appreciate some advice on this.
Greets Louis
ztva said:
Thanks for the response.
I flashed back to the original recovery and everything works fine.
I'm currently on COS 13.0.
Is there a safe way to root my Swift or get CM running safely.
I've tried a couple of methods on here, but they didn't seem to work.
I also reallly don't want to brick my phone since it's the first decent smartphone I have.
I know the basics like how to use adb and fastboot, but I'd really appreciate some advice on this.
Greets Louis
Click to expand...
Click to collapse
There is a separate thread about preparing for and rooting.
Being on COS13 you may want to use TWRP_3.0.2 (to be found separate thread) and flash UPDATE-SuperSU-v2.76 ZIP (to be found in SuperSU trhead) from TWRP.
You can even boot TWRP without the need to flash it with e.g.:
Code:
fastboot boot twrp-3.0.2-0.img
Hi, I have the same problem. My Swift is blocked on TWRP and it doesn't go into bootloader. How I can to do?
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
So I've held off software updates and decided to upgrade to OOS 9, but I didn't realise that there were treble compatiability flags. I then tried to install a newer version of codeworkx's TWRP with the compatiability check disabled but then had a kernel panic. Since then, flashing the original recovery I had (codeworx TWRP universal) and even the stock OnePlus recovery failed to work. I also tried
Code:
fastboot erase recovery
hoping that it would wipe the partition to allow me to reset the recovery, but still does not work.
To make it clear, I can boot into the OS fine, and fastboot works perfectly fine as well. It's just that the recovery partition that's ****ed and seems to not load at all.
Is there any way that this could be fixed?
rysx said:
So I've held off software updates and decided to upgrade to OOS 9, but I didn't realise that...
Is there any way that this could be fixed?
Click to expand...
Click to collapse
Hi, have you tried to flash the recovery within fastboot mode?
fastboot flash recovery 'recovery.img'
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader