I was notified about the MM update it says part 1 cant really remember the exact notif, the phone restarted then the screen shows the updating progress and it restarted after then it just went to recovery mode.
I have root it using Kingroot but unroot it after some months. so basically, it is not rooted?
in recovery mode, here is the text below:
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
handle_cota_install: install cwpkg to /data/data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
write host_mode success
handle_cota_install: No CW files. Skip cw installation.
when i tried to restart, it just keeps on going in recovery mode.
I have tried some stuffs to get it back to lollipop but im not sure how to do it properly.
(by the way, I just swap this phone to my samsung A5) is there a way to flash the lollipop rom easily like odin for samsung?
Im not pretty sure what is S-on and off but in fastboot mode it says S-OFF
things that I have done:
- i first installed e8 drivers in my laptop
- i tried to use ADB and fastboot but my phone is not detected properly when I type "adb devices" in cmd it does not show anything
- I also installed the sdk which is most probably 90+mb, but still not detected
- in fastboot mode the phone is detected by the computer, where it can be seen in computer management
- in recovery mode it is not detected by the computer
- i have tried to update the drivers in computer management but still its not detected by adb devices
- but when I typed "fastboot reboot" the phone reboots (that means it is detected? but still cant flash the twrp recovery so I can install the rom from the ext drive)
Please give me some advice. . . on what I should do. Thank you in advance!
may someone please help me I havent use my phone 4 days from now. I dont really know what to do
UPDATE: i managed to install twrp recovery. but im trying to install the rom file but is failing. what should I do? help please
its just going to recovery mode everytime i restart.
Jon_Nel said:
UPDATE: i managed to install twrp recovery. but im trying to install the rom file but is failing. what should I do? help please
its just going to recovery mode everytime i restart.
Click to expand...
Click to collapse
Which recovery are you using ? TWRP?
Do you have a TWRP backup ? or you can download a TWRP backup for your region from here and flash from recovery
mafie said:
Which recovery are you using ? TWRP?
Do you have a TWRP backup ? or you can download a TWRP backup for your region from here and flash from recovery
Click to expand...
Click to collapse
Thank you so much for your reply. At first it was the default recovery but i managed to install the twrp recovery using fastboot. No i dont have any twrp backup. Alright ill try it and let you know what happens. Again thank you!
mafie said:
Which recovery are you using ? TWRP?
Do you have a TWRP backup ? or you can download a TWRP backup for your region from here and flash from recovery
Click to expand...
Click to collapse
Sir, Thank you sooo much!!! My phone is alive again just a question. the OS that was in my htc one e8 now has the logo of some chinese company when booting and unicom when shutting down (well definitley because it is the default OS of phone which is from china). but before the problem happened it is not like that and has an english languange as default. does that mean that the OS installed before I swapped the phone is a custom ROM? and Im having some problem with the notifications area and the on screen menu, its not showing even if i swipe from the lower part going up and vise versa. no wifi signal, no time and date on the status bar(not sure if thats what it is called)
Related
After trying to install CM10 Via TWRP my phone hung on the CM10 splash page.
I have tried to reinstall CM10 and I keep having the same problem.
I'm able to access TWRP but for some odd reason I can't mount my sd card properly. I'm not able to click "Mount sd card" on the "mount" page in TWRP. That being said I can't backup my phone from a previous backup.. Any help would be greatly appreciated.
Now my phone won't even turn on.. HELP
undergrad said:
Now my phone won't even turn on.. HELP
Click to expand...
Click to collapse
Have you tried holding down the power and volume down button for longer then 10 seconds or longer? this should force restart your phone, get into TWRP and try an other Rom for now, also did you try an international rom? international roms will not work.
UPDATE: I'm guessing your also can't recover your last back up because your on HBOOT 1.14 S-ON? 1.14 will not recover boot.img's
If you manage to get it to mount to your computer (Check your drivers are installed also, EG htc sync usb drivers) then look for a "one click boot img flash" unless you know how to flash them using fastboot commands, whenever you are to flash a room, extract the boot.img from the zip file, flash that in fastboot, THEN go to recovery and flash a rom. same goes for backups. S-off is a hassle.
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
undergrad said:
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
Click to expand...
Click to collapse
when in twrp recovery.
1. delete cache, dav. cache, and system restore.
2. reinstall the gapp files and the CM10 zip file.
3. reboot
The issue is that I can't get into TWRP
what did you do to it? phones don't just die and cm10 didn't kill it. are you sure you flashed cm10 for the evita?
also try flashing this version of twrp openrecovery-twrp-2.3.3.1-evita.img
also run "fastboot erase cache" after flashing then try going into recovery and wiping cache,dalvik, and external
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
undergrad said:
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
Click to expand...
Click to collapse
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Lemagex said:
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Click to expand...
Click to collapse
I managed to relock my bootloader, but installing the stock RUU is still another story..
I can only get my computer to recognize that the phone is connected to my computer if I'm in Fastboot mode.
If you can't mount from recovery the sd got corrupted happened to me they have a fix if you do a few searchs. If you locked the bootoader and the computer only recognizes in fastboot that is good now run a RUU like 1.85
Sent from my HTC One X using xda premium
Dear XDA community,
I installed Clockwork recovery and the USB drivers. The device is unlocked and when in fastboot mode it is correctly identified by my PC as falcon XT1302 with an USB connection. When in recovery mode, the device appears as "Android" in the devices menu in Windows 7 and there is a yellow "!" next to it. Unfortunately after formatting system and deleting the cache as per instructions the device won't boot up. I'm stuck at the bootloader unlock warning screen. I can access fastboot mode and recovery mode but that's it.
I want to place the cyanogenmod zip inside the internal SD card of the Moto G but adb doesn't work. I get the device not found error when inputting a command. adb devices returns a blank. I don't know which drivers to install or what to do. I've tried various fixes on forums but none work. Maybe USB debugging is the problem although I distinctly remember switching it on. In any case, I can't boot so I can't change the settings.
All I want is a way to place the cyano .zip in the phone /sdcard so that I can install it. I'm all out of ideas. USB mounting doesn't seem to work. Neither does sideloader (or maybe I messed it up?) I am at wit's end.
I didn't have anything important on my phone so I did not make a backup. In hindsight, this was a stupid mistake. I've certainly learned a lot during the install attempt.
If possible please give step by step instructions. I am not a very technical person. Any help would be greatly appreciated. pls halp
kind regards
Dont worry too much if you can acces Fast Boot just download STOCK Firmware for your version I can't post links cuz im beginer searc under help "Restore STOCK Firmware" and flash it. :fingers-crossed:
Reply here i will tell you how if you not fixed it alredy
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
hechadnebiphyh said:
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
Click to expand...
Click to collapse
As above said flash stock boot up copy cm11 and gapps reboot boot loader flash cwm or twrp reboot recovery wipe data,cache,dalvik flash ROM gapps reboot all done
Sent from my Nexus 7 using Tapatalk
Thanks to the users who replied. I've managed to solve the problem. :laugh:
Would have been faster though to get your device recognized while in recovery. You can install the driver manually and it should work. Just search for seperate driver files and ignore the Windows message that it is probably 'not compatible etc.'.
Then your device is connected properly and you can get ADB sideload to work from your recovery.
Mac Os X - adb tool and fastboot installed.
Xperia S lt26i
I had the 4.1.x Android version, and I wish to install the Lollipop 5.1.1 version.
For doing that I need to install a ROM.
To install a ROM It may be usefull to have a recovery tool.
I'm using TWRP 2.8.5.0 as a recovery tool.
Problem:
Each time I try to install the ROM uCyan-12.1-b05.zip or simpleAOSP.zip, I get the same error:
It hangs on
"detected filesystem ext4 for /dev/block/mmcb1k0p12"
Click to expand...
Click to collapse
, and, after a while, I get:
" ... Operation not supported on transport endpoint set_metadata_recursive: some changes failed ..."
Click to expand...
Click to collapse
After some research I found out that, this error may be related with this warning message that TWRP provides:
" Kernel does not have support for reading SELinux contexts"
After some other research, I found out that, in order to avoid the error, I should use a OLDER version of TWRP, for example: 2.8.0.1.
If this is true, and if this is my only way around, I don't know how to downgrade to the older version.
I tried:
Code:
"adb reboot bootloader"
But the device simply restarts, and get's loaded into TWRP again.
No blue light, nothing.
Without being able to enter on the bootloader mode, I don't know how can I re-install the older version of TWRP necessary to install Lollipop 5.1.1. as desired.
Can anyone please help me out.
I'm stuck.
If I remember right, you can flash TWRP from within TWRP itself.
Telyx said:
If I remember right, you can flash TWRP from within TWRP itself.
Click to expand...
Click to collapse
I tried to select the older version of Flash TWRP and flash it, but it just refreshes and returns to the current (2.8.5.0) version.
Perhaps I'm not doing it right?
(Clicking on "Install", and then: selected the old ROM version, finally, I swipe to flash.)
Doesn't work, the version stays the same as before (2.8.5.0)
oikram said:
Mac Os X - adb tool and fastboot installed.
Xperia S lt26i
I had the 4.1.x Android version, and I wish to install the Lollipop 5.1.1 version.
For doing that I need to install a ROM.
To install a ROM It may be usefull to have a recovery tool.
I'm using TWRP 2.8.5.0 as a recovery tool.
Problem:
Each time I try to install the ROM uCyan-12.1-b05.zip or simpleAOSP.zip, I get the same error:
It hangs on , and, after a while, I get:
After some research I found out that, this error may be related with this warning message that TWRP provides:
" Kernel does not have support for reading SELinux contexts"
After some other research, I found out that, in order to avoid the error, I should use a OLDER version of TWRP, for example: 2.8.0.1.
If this is true, and if this is my only way around, I don't know how to downgrade to the older version.
I tried:
Code:
"adb reboot bootloader"
But the device simply restarts, and get's loaded into TWRP again.
No blue light, nothing.
Without being able to enter on the bootloader mode, I don't know how can I re-install the older version of TWRP necessary to install Lollipop 5.1.1. as desired.
Can anyone please help me out.
I'm stuck.
Click to expand...
Click to collapse
Try using flashify app
Hit thanks if i helped you!
TWRP flashing
Hi, I once had this exact problem...
This worked for me:
Reboot into recovery, go to Install and install the version of TWRP that you need.
Go to Reboot and select Recovery.
The device should then reboot into the newly flashed version of TWRP.
rashr
xitimo said:
Hi, I once had this exact problem...
This worked for me:
Reboot into recovery, go to Install and install the version of TWRP that you need.
Go to Reboot and select Recovery.
The device should then reboot into the newly flashed version of TWRP.
Click to expand...
Click to collapse
if you cant using your bootloader, try to using rashr.apk. download twrp image based on your device, and then, flash it using that app. should be success for me. just try
Thank you all.
I solved by flashing something, just to enter the bootloader stage. Once there, I flash the older twrp.
.apk was not an option because I didn't had a OS.
I tried to flash twrp using twrp, but it did nothing.
Anyway, issue solved.
Thank you for your suggestions!
Hi all,
I've received my Xiaomi Mi4c today and tried to install CM 12.1 from here :
http://www.teamsuperluminal.org/mi4c-cyanogenmod-12-1/
I think I've bricked my device, because when I tried to install the new ROM it failed, with an error that there is no OS install, are you sure you want to reboot and now I've got a device that doesn't boot or start...
I think it can connect to the PC but I don't have drivers for it... even if I have is there a way I can restore it to MIUI default ROM?
Please help..
Edit: I've deleted the ROM I had on the SD, so I ahve access to TW Recovery but I don't have anything on the phone... is there a way I can copy a file over and flash it again?
In twrp, go to mount tab and then mount your storage while connected to your PC and transfer the ROM over
Hi ermacwins,
Thx for helping!
I couldn't mount my external SD card, however I've sideloaded a stock MIUI ROM on the device. When I try to flash it I receive the following error:
zip signature verification failed 1
When I untick the zip verification it just fails.
Any ideas what I'm doing wrong?
GeorgiUzunov1990 said:
Hi ermacwins,
Thx for helping!
I couldn't mount my external SD card, however I've sideloaded a stock MIUI ROM on the device. When I try to flash it I receive the following error:
zip signature verification failed 1
When I untick the zip verification it just fails.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
You have the following possibilties:
Download a fastboot rom and flash it with MiFlash tool through your PC.
Or download a Rom from Xiaomi.eu or sMIUI (you can also use CM12.1 or MoKee). Put it in your phones storage and flash it in TWRP. But before you flash it, wipe cache, dalvik, data and system. Then flash it. If you get an error, just reboot again to TWRP and flash it a second time, but this time without wipes.
You see, you can easily recover your phone
please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??
alexvv said:
please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??
Click to expand...
Click to collapse
Press volume down + power for 4-5 seconds it will force reboot to fastboot mode then u can flash chinese stable rom and try again you must have kept the fastboot package by side so that if anything goes wrong you can get back to working stock rom
alexvv said:
please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??
Click to expand...
Click to collapse
Power off your device, then press POWER + VOLUME DOWN button together until you see the fastboot logo
Connect the device to a pc with (fastboot/adb drivers installed)
Download a TWRP recovery for the device and boot it with the following command:
Code:
fastboot boot mi4c_recovery.img
Then you will be able to wipe/flash new roms using the recovery.
well after many hours, i found the only working solution to be by adb sideload (thanks god i had twrp recovery, otherwise my phone would be completely dead). i flashed a smiui rom and all is fine. thanks for the help anyway. btw miphone tool is useless, couldn't get it to work.
can you say step by step with the adb sideload? my phone is enter in fastboot mod but not in recovery, when i keep volum up and power is starting to flash mi.com over and over again. I tried to flash Version: 6.2.25 (MIUI7) please help
Hi folks. As the title suggest I'm having problems installing TWRP recovery on teclast M89 tablet. I've tried a few different tutorials with no success. When I do it with fastboot it says that its installed, after that when I try to reboot the device, I'm stuck in bootloop. I've tried to do it a few times and its always the same problem. Does anyone have a solution? Thanks.
Hello, the same for me with my M89, I'm going crazy.... Help us please!!!! Thanks!!!
Teclast M89 TWRP 3.3.1
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
My small Teclast M89 website: https://teclast-m89.neocities.org/
M89 TWRP Worked!
ValdikSS said:
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
Click to expand...
Click to collapse
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Jmlanner said:
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Click to expand...
Click to collapse
Make sure to backup nvram, nvdata, private partitions.
ValdikSS said:
Make sure to backup nvram, nvdata, private partitions.
Click to expand...
Click to collapse
Will do. I did bkk nvdata, will double check if I bkk privdata. again TK!
stuck
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
Hi
I think you are going to have to reflash the original Rom using SPFlahtool. Then you must install Magisk Manage on tabletr. Copy the boot image from the ROM files to Your phone. Then use Magisk Manager to Patch the copied boot image. Transfer modified boot image to PC. Use fastboot to flash modified boot image back onto the tablet. The long and the short of it is - you need to find a way to patch the boot image with Magisk before any TWRP will work.
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
voland34 said:
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
Click to expand...
Click to collapse
I am glad you got your tablet running again. I had originally started out with just Magisk as root also. I do like to have a working TWRP for backing up though. You should be able now to flash the above mentioned TWRP now via SpFlashtool or fastboot.
voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
ValdikSS said:
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
Click to expand...
Click to collapse
Ok, i'll try. Thanks!
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No, most probably it won't. PRO model has different SoC/CPU.
gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
w1nst0n sm1th said:
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Click to expand...
Click to collapse
The bootloop is not because you've unlocked the bootloader, but most probably because the firmware is designed to perform userdata partition setup in the recovery upon first boot, and you don't have stock recovery, that's why it can't finish formatting procedure.
This could be fixed by flashing stock recovery and booting once.
You can ask for a firmware from Teclast (I used to ask them on vkontakte because they didn't respond my mails), they will provide it.
OR you can write zeros to "para" partition using fastboot, it should do the trick too.
---------- Post added at 16:58 ---------- Previous post was at 16:56 ----------
Edgaralanmx said:
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
Click to expand...
Click to collapse
Try to unplug/plug again HDMI cable several times. It seems that the HDMI controller or drivers are buggy.
To change the resolution I use "SecondScreen" software (requires root).
Hi guys,
I´m looking for a working rooting method for my Teclast M89 Pro model ??
Any idea ?? What about the "One Click Root" Program ???
Thank´s a lot
The device was trying to root.
I get the following information when restarting:
orange state
the device has been unlocked and can't be trusted
your device will boot in 5 seconds
Click to expand...
Click to collapse
When I try TWRP via sideload or recovery menu I get the following:
Supported API:3
-- Install /sdcard/teclast_m89_twrp_311.zip ...
Finding update packacke ...
Opening update package ...
Verifying update package ...
Update package verification took 0.5 s (result 0).
Installing update ...
E:Failed to find META-INF/com/android/metadata in update package.
Installing Teclast M89 TWRP Recovery
script succeeded: result was [1.000000]
Install from SD Card complete.
Click to expand...
Click to collapse
But TWRP is not installed.
Where is the problem?
kumpi said:
But TWRP is not installed.
Where is the problem?
Click to expand...
Click to collapse
Are you trying to enter recovery right after flashing it, without booting the OS first? I think you need do enter TWRP right after flashing it.