I have the Pixel 3 with unlocked bootloader
but the product revision is :crosshatch MP1.0(ROW) instead of blueline. Fastboot is in blueline though.
Tried to magisk boot.img -> boot loop
Tried to flash-all -> touchscreen not working
Tried lineage OS -> working
Tried google Flash Tool -> touchscreen not working (detected Pixel 3 at first but then suddenly it automatic detect Pixel 3XL instead at later part)
Tried to wipe and reflash blueline on a/b -> touchscreen not working
Im not sure what to do anymore, hopely anyone here can help
Related
Hi guys! I am very sad with all this. I had bought a xiaomi rerdmi note 3 snapdragon and I wanted to flash Miui 8 thinking that I had kenzo versión. It flash succesfully and the cellphone boots just I lost signal (not imei) and any sensor works. I had finally discovered that I have kate version after a few days. Now cellphone works fine but I couldn't solve mi ril problem. It recognize muy sin card but It says "no service" I really need your help :crying: :crying: :crying:
Restore efs partition of kenzo mobile
yogesh1970 said:
Restore efs partition of kenzo mobile
Click to expand...
Click to collapse
IT WORKS!!! Thank you bro
Unable to flash any twrp or rom in KATE
My redmi note 3 KATE unlock story so far:
- Tried to unlock the official way -> no success
- Tried to unlock the unofficial way (KATE fastboot) -> success
- Figured out that there were new section in oem info which told "critical unlock" was false
- Unlocked the critical unlock to true
- Flashed *alka twrp -> got errors when trying the advanced wipe as pumpino's guide suggested
- Tried to flash many different twrps but no success to boot them -> only fastboot mode worked
- Tried to flash the latest KATE fastboot with mi flash tool -> error: product name mismatch (or something like that)
- Tried to flash the latest KENZO fastboot with mi flash tool -> success but sim card failure (imei lost?)
- Unlocked the unofficial way and flashed coffice twrp -> no success, only fastboot mode working
- Removed the getvar name check from KATE fastboot and flashed it -> error while flashing the system img
- Flashed KENZO fastboot without the name check
Now I can boot to adb mode with vol- & power, and to fastboot mode with vol+ & power. Normal boot starts the phone but ends into chinese screen where is only one button to press and then it boots again to the same chinese screen.
Any suggestions?
pokspaks said:
My redmi note 3 KATE unlock story so far:
- Tried to unlock the official way -> no success
- Tried to unlock the unofficial way (KATE fastboot) -> success
- Figured out that there were new section in oem info which told "critical unlock" was false
- Unlocked the critical unlock to true
- Flashed *alka twrp -> got errors when trying the advanced wipe as pumpino's guide suggested
- Tried to flash many different twrps but no success to boot them -> only fastboot mode worked
- Tried to flash the latest KATE fastboot with mi flash tool -> error: product name mismatch (or something like that)
- Tried to flash the latest KENZO fastboot with mi flash tool -> success but sim card failure (imei lost?)
- Unlocked the unofficial way and flashed coffice twrp -> no success, only fastboot mode working
- Removed the getvar name check from KATE fastboot and flashed it -> error while flashing the system img
- Flashed KENZO fastboot without the name check
Now I can boot to adb mode with vol- & power, and to fastboot mode with vol+ & power. Normal boot starts the phone but ends into chinese screen where is only one button to press and then it boots again to the same chinese screen.
Any suggestions?
Click to expand...
Click to collapse
Answer to myself:
As long as you can boot to fastboot, you are pretty much safe. You can boot to edl-mode and flash the (kate) fastboot rom using the mi flash tool.
nachonv said:
Hi guys! I am very sad with all this. I had bought a xiaomi rerdmi note 3 snapdragon and I wanted to flash Miui 8 thinking that I had kenzo versión. It flash succesfully and the cellphone boots just I lost signal (not imei) and any sensor works. I had finally discovered that I have kate version after a few days. Now cellphone works fine but I couldn't solve mi ril problem. It recognize muy sin card but It says "no service" I really need your help :crying: :crying: :crying:
Click to expand...
Click to collapse
i'm in the same condition, didn't know that i have kate device and i flashed kenzo rom. I didn't understand how to solve. Help me please! i have locked bootloader
solved today, flashed keto global and worked
petrov.eduard90 said:
i'm in the same condition, didn't know that i have kate device and i flashed kenzo rom. I didn't understand how to solve. Help me please! i have locked bootloader
Click to expand...
Click to collapse
i have same problems, do you have been solved your problem ?
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
DOWNLOAD
TWRP 3.2.3.0
Flashing Instructions
Make sure you have fastboot drivers installed and your bootloader is unlocked
Download the file
In fastboot open the directory of downloaded file and type
fastboot flash recovery recovery.img, after that type
fastboot oem reboot-recovery, You'll have a black screen on your display wait for 5-10s you'll be greeted with TWRP screen if you still didn't get the screen then press power button 2-3 times
BUGS
Data decryption ( For this you need to select Wipe -> format data (You'll lose all your data in this process) )
No Battery% ( I purposefully disabled it as the battery% always stays at 50% so I'll find the battery% path and fix this in the next build)
Flash force encrypt disabler in recovery to fix magisk module installation and other data partition related issues.
Source Code: TWRP source, Device Tree and Kernel Source
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
pankajyadav_18 said:
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
Click to expand...
Click to collapse
By reboot problem if you mean, the phone getting restarted randomly in loop then the only way to fix it is to go to the service center.
Can twrp latest version used to flash color os 5.2 on realme 1..
Or maybe use color os 5.2 boot image and recovery and then use that recovery to flash 5.2 ozip..
JUst asking if this can actually work or not..
Also one wierd thing i noticed with my device is that it doesn't matter on whichever rom i am unable to use most of magisk modules except for few like viper or debloater other than few like those most of the mods flash fine and once i reboot i am always stuck at realme logo..So is that just me or everyone faces same like i tried jsp audio magisk mod or dolby one but none of those booted back once i press reboot.
Downgrade guide
Ezio553 said:
Can twrp latest version used to flash color os 5.2 on realme 1..
Or maybe use color os 5.2 boot image and recovery and then use that recovery to flash 5.2 ozip..
JUst asking if this can actually work or not..
Also one wierd thing i noticed with my device is that it doesn't matter on whichever rom i am unable to use most of magisk modules except for few like viper or debloater other than few like those most of the mods flash fine and once i reboot i am always stuck at realme logo..So is that just me or everyone faces same like i tried jsp audio magisk mod or dolby one but none of those booted back once i press reboot.
Click to expand...
Click to collapse
~ DOWNLOAD REALME 1 DRIVERS (https://drive.google.com/file/d/1en...N8phbKnjLxHH69TJoN_4lXl3U_ZaaBZ0dp_kb50YEDd94)
~DOWNLOAD THE STOCK RECOVERY (https://www.mediafire.com/file/25i9ubkq1qt9vb0/ColorOS_5.0_recovery.zip/file) OF COLOR OS 5:
~DOWNLOAD THE OZIP (https://download.c.realme.com/osupdate/CPH1861EX_11_OTA_0290_all_hKCRId6dsKkB.ozip) TO BRICK INTENTIONALLY TO FLASH
~Download Miracle Box (https://mega.nz/#!lVsQGSaC!6TTJopMyntMQA0IKYdC_5BlsxIjV_Ibhx2qWL_ZqDyI)
(NOTE: TURN OFF YOUR INTERNET AND ANTIVIRUS IN PC) And Set time on ur pc to year 2005
~Download the Firmware To Flash
Link1 (https://drive.google.com/file/d/1DRn19yilLcZS-w1hMZTnC9YmOBsVhz40/view?usp=drivesdk)
Or
Link2 (https://drive.google.com/file/d/1psVSI11wJnSJk25UaJQmc4h_7SEUpcjO/view?usp=sharing)
~Open TWRP AND goto wipe ,FORMAT DATA:type yes then ok,now factory reset and swipe and now advance wipe and select all the partitions except micro sd card
(DO NOT SELECT AT ANY COST)and wipe
~Now Flash The Stock Recovery Given above via fastboot or recovery.After Flashing The Stock Recovery Flash The Ozip I Given.After This Your Phone Will Brick ? Dont Worry You Can Fix.
~Now Open Up Your Phone's Backcover you will see like this (https://t.me/Realme1Community/168661)
~After that open the screws you will see like this (https://t.me/Realme1Community/168663)
~After this open miracle box
go to MTK > click services > select Write from the available options > select 8th boot(MT65XX & MT67XX) from boot options > then fron second option select OPPO realme 1 > then load mtk 6771 scatter file
(from the folder where you downloaded stock rom)
~Then disconnect the battery connector and reconnect it.Hit start in miracle box and connect usb
~Then a dialog box will appear make sure to tick all the boxes and then flash.
(DO NOT TICK ON SKIP PRELOADER make sure it's unticked)
(ONLY IF ITS STUCK AT DOWNLOADING BOOT8,PRESS VOLUME Down BUTTONS AND THEN CONNECT USB)nly one guy faced this issue?
~The Flashing Will Take Nearly 6 minutes After That Dissconnect The Usb Cable And dissconnect and reconnect the battery connector and try to boot your device will boot perfectly now.
~IF IT SHOWS INTERNAL STORAGE IS DAMAGED THEN
Switch Off Press volume down and power button to goto recovery and format data and reboot.?️
NOTE:IF YOU WANNA UPDATE JUST UPDATE VIA OTA
Ezio553 said:
Can twrp latest version used to flash color os 5.2 on realme 1..
Or maybe use color os 5.2 boot image and recovery and then use that recovery to flash 5.2 ozip..
JUst asking if this can actually work or not..
Also one wierd thing i noticed with my device is that it doesn't matter on whichever rom i am unable to use most of magisk modules except for few like viper or debloater other than few like those most of the mods flash fine and once i reboot i am always stuck at realme logo..So is that just me or everyone faces same like i tried jsp audio magisk mod or dolby one but none of those booted back once i press reboot.
Click to expand...
Click to collapse
Are those magisk modules working in ColorOS?
If not, then they, most probably won't work in Custom ROMs too
i was using pixel experience 12 with pixel recovery. i decided to update to new lineage os so i went pixel recovery and accidently wiped system partition and i forgot to enable usb debugging. now i cannot change recovery from bootloader menu. it doesn't show device from bootloader. but it shows from recovery. i tried installing recovery and rom from the pixel experience recover sideload mode but it doesnt install it shows error
error: protocol fault (no status)
I'd try using EDL point to flash the custom recovery, not sure if it works on F1 though. I've done it on Redmi 5A before.
Hi, I am currently on Stock android 12 and there is nothing I can do to reboot to Bootloader.
I tried all combinations of keys and adb reboot bootloader with differents drivers, usb ports, and adb versions.
Every time it boot into something with tiny letters for 1 sec and then instanly boot the system.
Any ideas ?
This is the tiny message I have
serial doesn't match
fastboot verify fail
Try searching. You're not the first one :]
Serial is not match fastboot unlock verify fail??
I am not able to open fastboot mode there is no fastboot mode available and showing this error in OnePlus Nord 2 5g
forum.xda-developers.com
Hey found THE solution to have fastboot and BROM. There is a rollback package to OOS 11 here. It works for all versions after C.05
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
follow instructions from this video but use package from oneplus community
you need to have enabled developer options to see the local update button