I try the ROM this thread https://forum.xda-developers.com/zenfone2/development/rom-cleanstock-mm-z00aww-4-21-40-144-t3492278 by By GuilhermeXtreme
README file MM bootloader folder I downloaded from his website:
" * Connect your phone to computer
* Execute upgrade.bat (win), upgrade_linux.sh (linux) or upgrade_mac.sh (mac)
* Script will flash new bootloader bits, reboot to new bootloader and flash new TWRP recovery
* Enjoy ! "
I upgraded to MM bootloader but didn't do "reboot to new bootloader and flash new TWRP recovery" part because I see the version of TWRP in the folder is same as my current TWRP. Then I flash the ROM and reboot but the phone didn't boot to the ROM, logo not show up and stuck at "Your device have failed verification .... " screen for few minutes and keep reboot to it. I tried the key combination to boot to fastboot mode but only see a black screen (phone still vibrate) and no logo.
I attempted to fix the phone and somehow it boot TWRP (thanks God) then I flashed LineageOS successfully.
Still logo lost and meet black screen when try to go fastboot mode.
.
What problem do I have beside losing logo? Lost bootloader? And what do I need to do to fix it?
Thanks so much in advance And sorry for my English.
Tu Dam said:
I try the ROM this thread https://forum.xda-developers.com/zenfone2/development/rom-cleanstock-mm-z00aww-4-21-40-144-t3492278 by By GuilhermeXtreme
README file MM bootloader folder I downloaded from his website:
" * Connect your phone to computer
* Execute upgrade.bat (win), upgrade_linux.sh (linux) or upgrade_mac.sh (mac)
* Script will flash new bootloader bits, reboot to new bootloader and flash new TWRP recovery
* Enjoy ! "
I upgraded to MM bootloader but didn't do "reboot to new bootloader and flash new TWRP recovery" part because I see the version of TWRP in the folder is same as my current TWRP. Then I flash the ROM and reboot but the phone didn't boot to the ROM, logo not show up and stuck at "Your device have failed verification .... " screen for few minutes and keep reboot to it. I tried the key combination to boot to fastboot mode but only see a black screen (phone still vibrate) and no logo.
I attempted to fix the phone and somehow it boot TWRP (thanks God) then I flashed LineageOS successfully.
Still logo lost and meet black screen when try to go fastboot mode.
.
What problem do I have beside losing logo? Lost bootloader? And what do I need to do to fix it?
Thanks so much in advance And sorry for my English.
Click to expand...
Click to collapse
from recovery dd latest mm fastboot image on mmcblk0p3. and splashscreen image on mmcblk0p4
how to do it!
copy fastboot image (droidboot.img) and splashscreen image on internal storage
reboot your device in twrp recovery. now from terminal run following commands
dd if=/sdcard/droidboot.img of=/dev/block/mmcblkop3
dd if=/sdcard/splashscreen.img of=/dev/block/mmcblk0p4
you can do it from pc as well
adb shell
su
then same above dd commands
you can also do from terminal emulator from mobile
su
and then above dd commands
Related
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076
Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers
Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance
Hello everyone,
i think my OP3 is bricked, cuz after i wanted to install new custom ROM with TWRP it went south. When I swiped to install the ROM it showed, it´s corrupt so i wanted so i wanted to push some other .zip to the phone through adb, but no device showed after adb devices or fastboot devices in fastboot. So I tried restore phone from backup i had via TWRP and the phone just wouldnt boot. Oneplus logo showed for a few seconds then it disappears and phone goes dark. Have to hold start button for 10 sec for hard restart phone and then i can go only to fastboot (now it will show fastboot devices in command line). Recovery won´t boot. Tried flashing stock recovery, some versions of TWRP and still just OP logo and dark.
Thanks for every help.
I think for:
fastboot -w
fastboot flash recovery recovery_of_ur_choice.img
on flashboot mode obviously ^^
With that, u must have access to twrp
Hi guys,
I've just updated to newest OOS firmware wich is 5.1.2 and I'm facing a weird problem.
Every time I flash codeworks TWRP and reboot to system, the next time i try to boot to recovery it boots to the original recovery.
It's like when I flash TWRP it doesn't remain persistent. When i flash it through fastboot and straightly boot from fastboot to recoverry I succeed to get in TWRP but as soon as I reboot to system and try to boot to recovery I reach the original OnePlus recovery.
Is anyone facing the same problem ?
And also do you have any idea about what i could do to solve this problem ?
Thanks in advance for your answers !
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Adnan008 said:
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Click to expand...
Click to collapse
Indeed, I just needed to flash magisk to get it persistent. I'll try blu spark's one as you suggested.
Thank you very much for your answer !
Cheers !
Nothing to do with recoveries or kernel. After you do the fastboot flash recovery TWRP in fastboot, do this: "fastboot boot TWRP". I believe that's the right command. Basically after you flash it, manually boot to recovery through fastboot one time. After that it'll work from inside the phone or with the button combination with the phone off.
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
pinnekeshaar said:
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
Click to expand...
Click to collapse
Actually not that lazy because I used to do what you mentionned.
The thing is that a flash of Magik is needed to patch twrp. That's the step I forgot in the procedure and explained here.
So before being unpleasant, please know what you're talking about...
Cheers !
Previously I was using Ressurection Remix treble rom which is based on android 9 pie. I went to TWRP and wiped the OS. Then I tried to install a new rom called Dot OS. But it showed error 7. So I flashed Vendortofactory zip within twrp and without rebooting again into TWRP I flashed a new TWRP image within TWRP by selecting Recovery mode. After that I cant boot into TWRP and as already my OS is gone I also cannot boot into any system. Moreover my device is not getting detected in my PC. I cannot install TWRP by writing commands in cmd, while the phone is in fastboot mode as the device is not getting detected in my pc. Really it is urgent. I will be glad if someone helps me. Thanks in advance.
What is the present booted state of your device? Are you in twrp, or bootloader. Most of the time you can keep on pressing the power button. When it boots into a message about unlocked bootloader, press volume button to select recovery and it will boot into twrp
You should be able to boot in fastboot mode without recovery nor os, maybe your drivers are not working on windows? Try different usb ports, check if the display says "bootloader" or something. If nothing works try the usb shunt, this device is literally 'unbrickable' if it's working properly.
Watch this video(https://www.youtube.com/watch?v=DexLELi04XY) and then you will be able to detect your phone in your pc in qcom 9008 mode , then use qfil to flash ZUI firmware ,there are plenty of tutorials on the internet for that ,then follow the proper procedure mentioned in DotOs thread for flashing the new rom .
Hope it helped .
If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method
yashpatel1221 said:
If you don't want to flash the firmware and all long process just follow the following steps
Enter in to the boot loader make sure you installed all the drivers in to pc then open cmd windows in adb fastboot folder and enters the following cmd into the cmd
Fastboot -i 0x2b4c devices this will detect your device
After that enter
Fastboot -i0x2b4c flash recovery recovery name.img
And boom you are good to go flash the rom of your choice and enjoy
For this process you need following files
Adb and fastboot devices
Drivers of zuk z2
Latest recovery and place revovery image file into the adb and fastboot folder if you are confused about anything pm me i am not the expert but i faced simillar problem and solved by this method
Click to expand...
Click to collapse
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.
sanjay.2704 said:
This assumes u have upgraded bootloader to 4.4 kernal.
U can still boot into twrp.. When the phone is booting up press vol up key and select recovery.. From there boot into twrp. There select f2v or v2f .. Then flash twrp which u want to flash.. Reboot to recovery.. U will get promp no os installed.. Ignore and reboot to recovery . Then again d9 f2v or v2f depending on what rom to install.. Again reboot to recovery... Then flash rom of ur choice.
This procedure is needed when changing from vendor to factory and vice versa.
Click to expand...
Click to collapse
I don't understand what you are talking about as i say i am not some kind of technical expert i am here help regarding this i faced similar situation where i am not able to enter into recovery and also not able to enter into the os and when i restart the phone it automatically boot into fast boot mode what ever option i select and i solved my problem by this method
Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.