Related
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
**edit: what....? never had to use that command before, but thanks a lot Entropy512 **
So this means, every time you update ota from baidu now, you have to unlock bootloader, first, then fastboot twrp, then install gapps + super su, phyy :silly:
spoonymoon said:
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-1.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
Click to expand...
Click to collapse
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Entropy512 said:
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Click to expand...
Click to collapse
Oem unlock don't make any difference, still locked, wont flash twrp, even it claims both oem unlock and flashing twrp.img went ok....but still stock recovery!?
They must have made some partition changes in 35, because when flashing through twrp, it gives two errors can't wipe data , but it don't give any flashing fail error, then when booting up it fc setup and won't continue , then booting into recovery again it's stock! ! Then flashing 35 through stock recovery, there's no errors and system boots up!
As said don't flash 35 you'll regret it
Think 34 is also similar in what you described.
To Entropy512......
What do you think will happen if we delete the new ´recovery dir (just including install_recovery.sh file) completly and replaced boot image from older ota version´s ? eks. from 33 which is not locked, i know because i flashed it and all ok and then put in 35 ota??
would it work you think? i dont have the guts to try...hehe
thx in advance
Try this. Download tantrums recovery flasher, unpack the zip on your computer, then in the "rec" folder go to "oppo" and extract the one other than "stock"
Now copy the modded recovery into the folder which contains fastboot.exe
And then "fastboot boot recovery.img"
the modded recovery will boot and then via that recovery, flash the tantrums recovery flasher. Aroma installer will start, then select twrp and flash what ever you like!
Hi,
I'm trying to flash TWRP on my Zenfone 2 Z00A but it won't work. I cannot boot to TWRP.
My device is unlocked and rooted and I can flash boot.img, droidboot.img and stock recovery.img but TWRP IMG won't work.
After flashing TWRP using command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens phone restart and boot to bootloader asking me to choose "Normal boot", "Recovery mode" "Reboot bootloader" ect.. and when I select "Recovery mode" phone restart and boot again to Bootloader not TWRP.
I also tried to flash TWRP using "Rashr" same problem not booting to TWRP.
Tethered CWM is working and I was able to boot to it but not TWRP
On the other hand if I flash back stock recovery and boot to it boots just fine.
What's wrong? Any idea guys?
Thanks in advance..
So, you've unlocked the bootloader or did you skip that part?
ultramag69 said:
So, you've unlocked the bootloader or did you skip that part?
Click to expand...
Click to collapse
Yes it's unlocked.
When I flash TWRP via CMD using fastboot command it shows successful writing TWRP IMG file. Otherwise it will show permission denied if the bootloader is locked AFAIK.
The splashscreen is white which means the bootloader is unlocked. But I don't know why it's not working.
Device is CN version flashed with WW firmware.
TWRP App-based installation
I've also tried upgrading to twrp-2-8-7-2-Z00A.img from within the TWRP Manager app. It seems to download and gets to the "installing/verifying" screen, then dies after a minute or two. The phone is rooted and unlocked. But after about the 4th or 5th try, it worked.
Ok problem solved
It turns out there was a problem with the bootloader. I used the adb commands to unlock it and it was showing successful but some how it was not unlocked fully as it seems.
The splash screen turned to white after unlocking the bootloader so I thought it was unlocked. I even tried unlocking it many times and every time the adb results were showing bootloader unlocking success but it tuned out it wasn't unlocked fully.
Today I used the official bootloader unlocking App from ASUS and unlocked the bootloader. I flash TWRP again and rebooted to recovery and BAM ! it booted to TWRP
The_wolf88 said:
Ok problem solved
It turns out there was a problem with the bootloader. I used the adb commands to unlock it and it was showing successful but some how it was not unlocked fully as it seems.
The splash screen turned to white after unlocking the bootloader so I thought it was unlocked. I even tried unlocking it many times and every time the adb results were showing bootloader unlocking success but it tuned out it wasn't unlocked fully.
Today I used the official bootloader unlocking App from ASUS and unlocked the bootloader. I flash TWRP again and rebooted to recovery and BAM ! it booted to TWRP
Click to expand...
Click to collapse
Hello, I have similar problem with my Zenfone 2 Z00A. Bootloader seems to be unlocked because of white splash screen on start-up, but I cannot flash TWRP recovery via fastboot flash recovery ***.img. The process shows no problems/errors but despite that no TWRP after reboot.
Can you explain how you found out that bootloader was not unlocked fully?
lkananowicz said:
Hello, I have similar problem with my Zenfone 2 Z00A. Bootloader seems to be unlocked because of white splash screen on start-up, but I cannot flash TWRP recovery via fastboot flash recovery ***.img. The process shows no problems/errors but despite that no TWRP after reboot.
Can you explain how you found out that bootloader was not unlocked fully?
Click to expand...
Click to collapse
I don't know why but after 4-th or 5-th attempt TWRP finally loaded.
Hi, I have a similar problem with my zenfone 2 z00A. My device is not rooted. I tried to use the process described here.
Installation
Latest releases, tools and general information
groovyandroid.github.io
I tried bootloader unlock process with the app on my phone first, but after 4-5 times of use, it always came up with 'Network error'. I went with the 2nd part of unlocking bootloader to transfer TWRP imgae file. Now the phone is starting with a white splash screen and showing 4 options: Normal boot, Power off, Recovery mode and Restart bootloader. I have tried fastboot flash recovery twrp.img and fastboot boot 'twrp.img', but still can't get to TWRP recovery process.
hey,
I wanted to root my nexus 5x too, first I tried to do so with the nexus tool kit....
it was all working until it came to the root process:
it said in the log:
Rooting....
Waiting for your device....
and nothing else happened anymore.
So I tried it manually with a guide.
As the bootloader was already unlocked, I continued with flashing the recovery (twrp 2.8.7.2) in fastboot.
Then it rebooted into the recovery.
Then twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I allowed the system modification then... so then before rebooting, twrp wasn't asking me if I want to flash the SuperSu.
Since this I'm stuck in a bootloop.
I can boot into the bootloader and recovery, I also tried to do a factory wipe or also formating data. But none of them worked for me. I'm still stuck in the bootloop...
I have no idea what to do now....
I'm really thankfull for every kind of help!
sorry wrong subforum...
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Vulkaistos said:
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Click to expand...
Click to collapse
I have to add something which i forgot to mention.....after I flashed the recovery and booted into it for the first time, twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I'm not able boot my phone up anymore.... I can try to flash the recovery with fastboot again...if this is what you mean?
okay i pushed the supersu zip onto the phone, and just flashed it. And my phone is booting normally now
thank you very very much. you saved me and my phone
That's nice to hear.
Have Fun with your Phone!!!!!!!!!!!!!!
Hi so I was using resurrection remix but after finding my stock phone software NPP25.137-15 online I erased everything and flashed through fastboot it went perfectly and I re-locked my bootloader
but I decided to unlock my bootloader again so I could use magisk on stock firmware
my bootloader unlocked and phone still booted but my problem is with twrp
I powered off my phone
held power and volume down
connected my phone to pc while in bootloader
typed fastboot devices
typed fastboot flash recovery twrp.img
pressed power button on phone to reboot phone ( I didn't boot into recovery )
my Moto G5 XT1675 halts at phone can't be trusted ( bootloader is unlocked screen )
any idea why I can't flash twrp?
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Exanneon said:
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Click to expand...
Click to collapse
What exactly does this file do?
Also I flashed magisk which I knew modifies the boot image and the device booted perfectly with TWRP using the magisk modified boot image if that's anything interesting?
Pretty much I was working on a way to install stock firmware through twrp a few weeks ago so people would not have to use fastboot ( I know how to convert a phone backup to a flashable zip )
The flashable zip worked fine but it only booted using a modified boot file, could this be because it needs DM verity disabled?
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Exanneon said:
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Click to expand...
Click to collapse
it's not meant to be a substitute, and I know only fastboot can do OEM lock, flash partition files, modem files,etc, I've been testing my TWRP version for a while, the oem.img partition is not needed in the TWRP versionas the majority of custom roms for Moto G5 don't touch the oem partition and the oem.img file hasn't changed between the stock updates, the TWRP version is for people who want stock firmware but still want to keep twrp, flash magisk, etc, also because TWRP is a portable method and much faster flashing the system back than through fastboot flashing the system back, my twrp version is only meant to restore the system partition and a dm-verity disabled boot.img I wouldn't even think of flashing a bootloader through anything other than fastboot, I've tested a lot and have not bumped into any problems using TWRP that has caused me to use a computer, actually there has been no problems + I'm also testing on 3 other moto G5's all 3 which are also XT1675 models and same there no problems
Then your query has been resolved.
Exanneon said:
Then your query has been resolved.
Click to expand...
Click to collapse
yes, how do I go about closing this discussion well if you know how to?
Rename it to [closed], that's what many do.
After updating the MIUI, I found to my dismay that TWRP was gone.
But the phone status still says "unlocked".
I re-flashed TWRP but did not boot into it directly.
When I wanted to enter TWRP later (after having booted notmally once), TWRP was still gone. Just the stock bootloader.
Could it be that I have to flash and then boot into TWRP directly in order to make it persistent?
Yes. After flashing twrp boot to recovery or else the recovery restores to stock recovery.
Ok. Will do it this weekend.
a-dummy said:
After updating the MIUI, I found to my dismay that TWRP was gone.
But the phone status still says "unlocked".
I re-flashed TWRP but did not boot into it directly.
When I wanted to enter TWRP later (after having booted notmally once), TWRP was still gone. Just the stock bootloader.
Could it be that I have to flash and then boot into TWRP directly in order to make it persistent?
Click to expand...
Click to collapse
Rewrite vbmeta or flash universal dm_verity disabler and the twrp will not gone.
Ok. That solved it.