Hey guys, I do not think this is a re-post of the other TWRP problems on Blackview 6000s. I have tried to install TWRP on my device many times. When I reboot into the custom recovery, a android with a danger sign appears. Instead of the TWRP screen. So what is the problem? (Android Noob here, please don't throw big developer words ).
Have tried
1. Changing USB ports / Using different computers
2. Flash_tool.exe
3. Flashing though adb/fastboot (is it the same?)
4. Different versions of TWRP.
5. Enabled USB debugging, OEM unlock & Install from Unknown Sources
Error Messages:
1. Running this -> adb reboot bootloader
error :no devices/emulators found (device was detected in "fastboot devices")
2. Running this -> fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9318 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.142s
(However, TWRP is not installed?)
Problem is solved, if u need help pm me
Hi,
Its good phone? Worth to buy it?
off160 said:
Hi,
Its good phone? Worth to buy it?
Click to expand...
Click to collapse
Yes, it is. It is a damm good phone. Pm me for more details.
Managed to solve issue. flashed wrong TWRP file lol
ROM for the bv6000s MT6737T?
DoctStrange said:
Managed to solve issue. flashed wrong TWRP file lol
Click to expand...
Click to collapse
Hi did you manage to find a ROM for the phone?
Hello
Might I know what ROM you are using, and where you got the TWRP? I managed to flash TWRP once on the device, and then install SuperSU when it had a previous ROM.
But I flashed it with blackview's latest ROM I found on their website. Since then, when I flash TWRP, the phone won't boot anymore
I'm using TWRP3.0.0, which is the latest one I found with a scatter file.
Related
Hello all, hopefully someone here can help me. I've wasted the past 2 days trying to install the xiaomi.eu ROM file. I am currently running MIUI 7.0 Stable.
After downloading the hermes file moved it onto the phone and attempted to use the updater app to install. I receive the error message "update.zip signature verification failed" after trying this. Doing some searching it seems that I need to install TWRP and SuperUser to enable me to do this.
So attempting to install TWRP. I followed the instructions to the letter yet TWRP is not there. The phone still goes into the default MIUI recovery. Here is the log from the cmd prompt:
target reported max download size of 134217728 bytes
sending 'recovery' (13370 KB)...
OKAY [ 0.674s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.912s
I have also tried to flash using the MI PC Suite but I cannot use the recovery option as I need to make a back up. However, the software won't let me create a back up.
I have also installed Flashify on the phone but it always crashes when I select Recovery Image > Choose file.
Can anyone offer any advise? I am at my wits end here and don't know how to proceed.
(Can't post links as I am new but I used the intructions on miui and xiaomi.eu)
Thanks in advance.
Michael92 said:
Hello all, hopefully someone here can help me. I've wasted the past 2 days trying to install the xiaomi.eu ROM file. I am currently running MIUI 7.0 Stable.
After downloading the hermes file moved it onto the phone and attempted to use the updater app to install. I receive the error message "update.zip signature verification failed" after trying this. Doing some searching it seems that I need to install TWRP and SuperUser to enable me to do this.
So attempting to install TWRP. I followed the instructions to the letter yet TWRP is not there. The phone still goes into the default MIUI recovery. Here is the log from the cmd prompt:
target reported max download size of 134217728 bytes
sending 'recovery' (13370 KB)...
OKAY [ 0.674s]
writing 'recovery'...
OKAY [ 0.231s]
finished. total time: 0.912s
I have also tried to flash using the MI PC Suite but I cannot use the recovery option as I need to make a back up. However, the software won't let me create a back up.
I have also installed Flashify on the phone but it always crashes when I select Recovery Image > Choose file.
Can anyone offer any advise? I am at my wits end here and don't know how to proceed.
(Can't post links as I am new but I used the intructions on miui and xiaomi.eu)
Thanks in advance.
Click to expand...
Click to collapse
I read somewhere, and have saved to a text file: "You obviously didn't read the thread. The instructions works only for those on developer ROM which has root access. If you are on stable ROM you need to do the following:
1) Download supersu.zip and transfer the file to your phone's internal memory
https://download.chainfire.eu/696/SuperSU
2) Download the twrp287.zip from this thread. Rename it to update.zip, transfer it to your phone and install through the updater app.
3) The updater app will reboot your phone automatically when the installation is complete. Once the screen turned off, quickly hold the volume-up button to enter recoevery. You will see TWRP recovery.
4) While in TWRP, flash the supersu.zip to get root access. Reboot your phone once done.
5) Once your phone rebooted into android again, use any file explore with root access to delete recovery-from-boot.p or renamed it to recovery-from-boot.bak from system folder.
6) Your TWRP should work from now on and persist through reboots.
Hope you managed to get it working. The material interface rocks!"
Sent from my Redmi Note 2 using Tapatalk
Ok I've got my opx, unlocked the bootloader and installed twrp, don't know how I forgot to make a backup before flashing supersu and now my phone can only enter twrp, nothing else. Can someone please make a nandroid backup and share it with me, I'm trying to restore it that way. Or can I do anything else? Any help will be appreciated, thanks!
Sent from my XT1033 using Tapatalk
demolatorul said:
Ok I've got my opx, unlocked the bootloader and installed twrp, don't know how I forgot to make a backup before flashing supersu and now my phone can only enter twrp, nothing else. Can someone please make a nandroid backup and share it with me, I'm trying to restore it that way. Or can I do anything else? Any help will be appreciated, thanks!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Stock rom link:
http://forum.xda-developers.com/onep...-dump-t3244996
Stock recovery:-https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
2. Now boot into twrp recovery
3. Mount you storage in twrp mount option.
4. Copy the rom and stock recovery...unmount.
5.. Boot into TWRP. Install -> Select Images -> Select the recovery.img -> Proceed. Scrn shts added
6.Now Do not reboot from TWRP, your oneplus would freeze instantly. Do a "adb reboot recovery" from terminal/command-prompt instead. This will reboot to stock recovery.(if you havr installed new 2.8.7.0 there is no bug like freeze)
7. After having boot into Stock recovery, Flash full system Dump
Hit thanks if helped
Thanks, all I needed was the stock rom to flash it, thanks man!
Sent from my XT1033 using Tapatalk
i have a big problem
C:\adb\cm11s>fastboot flash recovery stock_recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
when i type fastboot oem unlock my oneplus x boot end`s in Bootloop
sorry for bad english i am German :crying:
bj82xx said:
i have a big problem
C:\adb\cm11s>fastboot flash recovery stock_recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
when i type fastboot oem unlock my oneplus x boot end`s in Bootloop
sorry for bad english i am German :crying:
Click to expand...
Click to collapse
Same here! Bit stuck on what to do? Any ideas?
Solved IT
dagstar said:
Same here! Bit stuck on what to do? Any ideas?
Click to expand...
Click to collapse
- Unbrick it http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
- Update the Bootloader with the latest one : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
-Thats it
THANKS
mohammedtabish said:
Stock rom link:
http://forum.xda-developers.com/onep...-dump-t3244996
Stock recovery:-https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
2. Now boot into twrp recovery
3. Mount you storage in twrp mount option.
4. Copy the rom and stock recovery...unmount.
5.. Boot into TWRP. Install -> Select Images -> Select the recovery.img -> Proceed. Scrn shts added
6.Now Do not reboot from TWRP, your oneplus would freeze instantly. Do a "adb reboot recovery" from terminal/command-prompt instead. This will reboot to stock recovery.(if you havr installed new 2.8.7.0 there is no bug like freeze)
7. After having boot into Stock recovery, Flash full system Dump
Hit thanks if helped
Click to expand...
Click to collapse
Onyx was soft bricked, when booting, the bottom text disappeared, so boot loop. This method help me to restore everything as default, and worked perfectly! Thanks so much!!!!
After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
DankMemz said:
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
Click to expand...
Click to collapse
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
benkiller47 said:
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
Click to expand...
Click to collapse
Try reinstalling stock firmware trough download mode...
Try reinstalling the twrp image. Helped me once
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.
Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1
I only have a linux laptop, so the rescue and smart assistant appears to be off the table
Here's what I did:
Downloaded the boot.img from lolinet
patched it using magisk
flashed it using fastboot
How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.376s]
writing 'boot_b'...
OKAY [ 0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [ 0.350s]
writing 'boot_a'...
OKAY [ 0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.370s]
writing 'boot_b'...
OKAY [ 0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.908s]
writing 'boot_a'...
OKAY [ 0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.949s]
writing 'boot_b'...
OKAY [ 0.525s]
finished. total time: 2.474s
once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo
Any idea what I've done wrong? Would really appreciate some help with this.
Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.
Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
check the forums for the g7 play, I've found topics about that kind of issue.
There's a few touchscreen vendors used for the same device, and they use different drivers basically.
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.
Any idea how to figure out which set is right for my phone?
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
mingkee said:
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
Click to expand...
Click to collapse
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
cnoevl21 said:
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
Click to expand...
Click to collapse
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
mingkee said:
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
Click to expand...
Click to collapse
when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
PamelaGirl said:
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
Click to expand...
Click to collapse
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
PamelaGirl said:
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
Click to expand...
Click to collapse
sadly the phone i tried to root is the only phone that i have
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
PamelaGirl said:
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
Click to expand...
Click to collapse
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
klninja said:
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
Click to expand...
Click to collapse
That’s a good find. Please report back with your success so I stand corrected.
PamelaGirl said:
That’s a good find. Please report back with your success so I stand corrected.
Click to expand...
Click to collapse
a person already did this
That’s good news!
Now its your turn.
PamelaGirl said:
That’s good news!
Now its your turn.
Click to expand...
Click to collapse
i would like to ask a question, when ur g8 wasnt working did the phone charge or not? cus mine dont show how much battery i have
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.