Related
Hi
I Tryed every solution and get a new one
Only Luck
First my Android folder i put this to c:
O.K i tried to flash ruu but only get the battery issue.
i charged over night nothing helped
i tried to flash via fastbood where i get an status error or 00000006
i download the last recovery.
Thanks a lot for this here you get it
After that i flashed it (unlocked bootloader)
tried adb but nothing happened.
one update is boot it. iam a noob i dont know what it mean so i tried.
i renamed the cwm to reco.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
load fastboot on your htc
go to cmd and go to your folder
write "fastboot boot reco.img"
the phone will boot recovery and KNOW YOU HAVE ADB working
you can load your favourite rom
i take this one rename it to update zip
after that put it in your folder with adb and fastboot
adb push update.zip /sdcard/update.zip
this will need some time
After that you have your rom at your sdcard where you can flash it with recovery
sorry for my very very bad english but maybe this will help other
Option
you can choose stock rom
i take this one rename it to update zip
adb push update.zip /sdcard/update.zip
Many thx for your big efforts. I have the new recovery 5.8.3.1 on my One X since the day it was released. Also i have had no problems with sd card - i have a running custom rom, so i could transfer the rom.zip with USB to my card. I also tried to flash it via HBoot and recovery, but it fails. I think, my device or the setup program is confused, because in the boot section is the regular provider o2 identified, but after the firmware flash from mikes thread, the device is also detected as an HTC original model, it shows me 1.28.40.... in the installation menu of the RUU. My actual rom is 1.29.... it must be a bug in the detection.
It seems too dangerous for me to try some things, which i don´t really understand without a good description, what i can do if this fails. Better to stay at the moment at my running custom rom and to forget the updates as to brick my device. Hope, we will get S-Off in the future, if earlier, it´s better.
i wiped my phone and wanne flash the new one. but the phone told me my zip is damaged. no way back.
so i write this tutorial because this was the only way which helped me.
updated flashing custom rom...
klarmacker said:
updated flashing custom rom...
Click to expand...
Click to collapse
I am trying every method out there including this one and the reco.img loads fine but I cannot push adb or fasboot the update.zip
---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------
Diamond777 said:
I am trying every method out there including this one and the reco.img loads fine but I cannot push adb or fasboot the update.zip
Click to expand...
Click to collapse
Is the stock image in the Android folder u posted the 1.26¿?
you can load every rom.
rename this file to update.zip place it in my folder,
it hase to be in the same folder like adb and fastboot...
after that
adb push "name from the rom.zip you choose" /sdcard/test1.zip
that can take up to 2 hours. You see nothing. no status you have to wait
but what happend that your phone doesnt boot???
When you have leedroid try flashing the boot.img from his post...
LeeDrOiD One Xtreme V5.1.0 boot.img (Self flash)
I follow ur steps and all went well to the CWM.
Cannot make it to push on ADB the ROM.
Any clues?
I finally found the issue.
the command update.zip /.... I didnt put a space before. Wow for the moment I am feeling more relieved.
Well since u have already warned me that it takes a long time and theres no progress status, I will just wait.
I´ll update but many thanks.
thanks
your post was the missing piece which safed me hours of time. you made it very klar to me and made my provider get around another overheating phone in bootloop
Cheers.
131313 said:
thanks
your post was the missing piece which safed me hours of time. you made it very klar to me and made my provider get around another overheating phone in bootloop
Cheers.
Click to expand...
Click to collapse
Amen to that! I was going CRAZY!
Now am back in the show and flashing away!
yes maybe its possible to make it a sticky till usb mode in recovery is supported...
for some german here a german tut
here the tut
good lession
bookmarked
Shame on me !
Hi,
I have a relocked device, usinf your method i unlock again, flash boot image from ARHD 5.xx...
i have already Superwipe on MY SD card but i can't push using ADB in CWMR v5.8.3.1...
i follow all instruction but i m still suck at adb push feature...
my HoX :
S-on
Hboot 0.43
Original ROM 1.26 buy today... no update !
if you have any tips...
OR
i will try to restore battery on CWMR... then relock, update boot wuth signed version and try to use RUU_**.exe
good info
original rom try update
you habe to boot the cwm not flash
So I recently flashed a self made ROM for my watch and it totally bricked it, it cannot boot into a system (just bootloops), Cannot access recovery mode (just turns off and bootloops) and last but not least PC Companion will not detect it. All I have now is fastboot mode so if someone can please help me flash each partition via fastboot that would amazing. I do how ever all of the correct drivers so I am guessing that it will not detect is due to the fact my device has no build.prop.
I really DON'T want to call sony support unless I really have to, so any help would be beyond amazing.
Screenshot from PC Companion:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need ANYTHING, Video's Pictures, etc feel free to ask as I will try my best to help.
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
lekofraggle said:
Grab the stock recovery (or the version of twrp) which is appropriate for your build.
Put the watch in fastboot and on your computer in a terminal window type
Code:
fastboot boot <recovery.img>
Then in recovery, install the Os you want.
You have two options. Use stock recovery and then factory reset. Or, use twrp and go all the way back to the 5.0.1 image. If nothing else works. The later will. Do not forget to factory reset after you roll back.
Click to expand...
Click to collapse
Tried it, just reboots
Then you are using the wrong recovery. What did you build?
lekofraggle said:
Then you are using the wrong recovery. What did you build?
Click to expand...
Click to collapse
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
1619415 said:
Well I think what happened is all of the partitions got messed up, does this watch use system.img? Because then I could flash that through FASTBOOT
UPDATE: I got twrp to boot but... It cannot mount any partitions
Click to expand...
Click to collapse
The closest thing I have seen to a system.img is the roll back zip file of 5.0.1 in this thread
http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
I also can't access my SDCard/Internal Storage
UPDATE: I just think I have no OS installed, nothing installed at all actually. So I think I just need to reinstall system and other important data
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
lekofraggle said:
Okay so that is my guide. Use the 5.0.1 image. I think the issue is precisely that you have no system. A normal flash does not usually touch the boot loader or partition map. So, do not jump to that conclusion yet. If twrp does not work for you, try using the fast boot flash of the 5.0.1 Recovery image.
Which version of twrp worked for you?
Click to expand...
Click to collapse
The 5.0.1 twrp would not boot but, the 5.1.1 one does just does not mount anything and the stock recovery does not boot either. I did however try to adb sideload stuff but could not find a system.img.
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
lekofraggle said:
So, what you should try to do is adb push the 5.01 file while booted in the 5.1.1 twrp.
Did you try the 5.1.1 stock recovery? I am not sure it will help even if you get it to boot.
Click to expand...
Click to collapse
I already tried twrp, it can't mount any partitions
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
lekofraggle said:
Did you try pushing from the computer?
Code:
adb push <originalsystem.zip> /sdcard
If so, what was the exact error you received?
Click to expand...
Click to collapse
Twrp can't mount anything at all, im guessing that it cannot create a folder on my internal storage. Adb sideload wont work either because it cannot mount
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
lekofraggle said:
Again, what is the specific error you receive trying adb push (not sideload) after you boot to the somewhat working twrp?
Click to expand...
Click to collapse
error: device not found
Okay, so try adb devices and see if it shows up. If it does, you are correct and need to repartition. That is neither easy nor unrisky. It is easy to brick your device.
If it does not show up, you need to install the drivers. Twrp uses different adb drivers than the watch Os for some reason.
I think this is my main problem...
@lekofraggle
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Do a format of the system, recovery, userdata and then reinstall from a custom rom online
****************
* SENT FROM *
* A *
* MOD KING *
* DEVICE *
****************
lekofraggle said:
Potentially. What happened when you ran adb devices? You need to do that on your computer.
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
Adb has different permissions than twrp.
Click to expand...
Click to collapse
Either it does not show up or... it just says "error: device not found"
Hello everyone. I was with Android 7 on my ZS570KL and returned to 6 for a tutorial found on the internet and worked, but all the sensors of the device were disabled (screen rotation, gyroscope, approximation, fingerprint [only registers up to 93% and gives error], and all the others). How do I reactivate? I came back to Android 7, formatted the device several times, and nothing solves!
What tutorial and why?
No information = no help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I do not remember where I found the tutorial and the files, but the process is this:
1. Download http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-4.12.40.1698-user.zip
2. Download https://mega.nz/#!tp9DSQ4b!3wdDLsh3BBtPju8G74xlDjLJ9QywFaoLs1T11mMt3QQ
3. Unzip FlashTools64_20161125.zip
4. Unzip UL-Z016-WW-4.12.40.1698-user.zip and move out files under firmware-update to FlashTools folder
5. Put downgrade.bat, boot.img, recovery.img to FlashTools folder
6. Reboot phone to bootloader and click downgrade.bat
The reason was to swap the conventional root SU through the Magisk. I tried to reinstall 7 just by replacing the original recovery available here in XDA, but the process was not going to restart, so I followed that one to try to return and reinstall everything. It worked, I got back to 6, but I did not know everything. It looks like a computer without the drivers installed.
I'd downgrade again, if it was me, this time I'd install a stock Rom (MM) from ASUS. Then test everything again. If everything is good to go then I'd root and upgrade.
Changing the OS in the middle doesn't help if you have a problem.
Especially if it just builds upon the foundations of the previous OS...
Did you flash a complete N rom or do an update?
The ROMs I try are exactly those of the Asus site. I tried the downgrade again to version 4.12.40.1698 and realized something when I flash in recovery mode. The following error messages appear:
Unmount of /firmware failed: no such volume
Mount: failed to mount /dev/block/bootdevice/by-name/mdtp at /firmware: No such file or directory
Unmount of /firmware failed, no such volume
What is it? How to solve?
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
AndreSantoro84 said:
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
Click to expand...
Click to collapse
These recovery images are from nenebear59, thanks to him !
Z016-WW-5.14.44.2212_recovery :
For 2.15GHz CPU
For 2.4GHz CPU
Thank you very much! Now I need the "persist.img" file, of the same rom, can you make it available? I thank you!
I downloaded the source code kernel from the Asus site, and the compressed file has a sensor folder. I downloaded the kernel zip file to my memory card and tried to install via recovery, however the following message appears: E: footer is wrong / E: signature verification failed. How do I get install by recovery or via flash in cmd?
I followed this tutorial (https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061) and managed to recover the fingerprint reader, but the others are still turned off. I really need the correct file! Somebody help me, please!
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Really??
Ryder. said:
Really??
Click to expand...
Click to collapse
sorry from nougat to marshmallow
There isn't android lollipop for the asus zenfone 3 series. They came out with marshmallow.
AndreSantoro84 said:
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Click to expand...
Click to collapse
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Come on. To downgrade, you need to download the official rom from the Asus website (version WW-4.12.40.1698 - do not forget to check if your device is 2.15 or 2.4 ghz). Downloaded, need to put the rom inside a micro sd card (can not be internal storage, need to be in sd). In addition, it must be with the original recovery (the version is indifferent), if it is in TWRP it will not work. Once you have done this, you will have access to recovery mode, go to the "install zip from sd card" option, locate the zip file of the rom and install it, and just wait. Having problems, report here.
cazadormoron said:
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
Click to expand...
Click to collapse
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Solved!
AndreSantoro84 said:
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Click to expand...
Click to collapse
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
cazadormoron said:
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
Click to expand...
Click to collapse
If you want to root, flash the twrp and then supersu zip from twrp
Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.
Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...
Also, lenovo vibe c2
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk
AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?
i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?
serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:
I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.
hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"
https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!
Thanks to VD171 for his post.
I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.
Learn more about it in this video
reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?
mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.
no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked
reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.
Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.
reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.
if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.