Related
So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....
I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183
joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)
https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!
well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.
Its not rocket science
timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.
i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!
Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8
Ok. I've got a Zenwatch 1 that's driving me nuts. It started off with issues on the latest os (crashing after any action, needing to go on the charger to reboot, etc). I found out how to get into the recovery partition and I performed a wipe to clear things up. Unfortunately the watch got stuck in a boot loop with the Asus logo. I can open either Fastboot or recovery so I know the hardware itself works. I've found a lot of information on this forum but I'm not seeing a clear path forward. Here's what I've pieced together.
1) Fastboot oem unlock: I can get into fastboot and get to the oem unlock screen. The problem is that the command just takes you to a screen that requires interaction with to continue. I need to access the power button to select a value and continue. The problem being is that if I take the watch off the cradle to hit the power button the phone shuts down. I've charged it so it's not an issue with charge. Is there a command that not only triggers "fastboot oem unlock" but also bypasses the onscreen confirmation? If not I've ordered a cheap charge cradle that I can drill an access hole through.
2) flash the recovery partition: I need to get fastboot oem unlock to work. Probably going with TWRP. Stock recovery works, but it's driving me nuts trying to upload firmware.
3) Find a stock firmware image: I've found images of the various updates, but no full stock roms in an img format. I've tried an adb sideload of some of the update zip files, but the recovery on the phone says they aren't valid. I need a full stock image to update to. I'd rather go back to factory stock, but I can't seem to find that image. All the roms on this page seem to be updates from a previous version, not a full self contained rom. https://forum.xda-developers.com/zenwatch/general/compilation-asus-zenwatch-anthias-ota-t3719367
I've contacted asus and they're telling me I could mail the watch in for a reflash for $60. I don't think the watch is worth $60 any more. Are there any base images available for this watch?
Hi,
I can provide you a TWRP backup of my ZenWatch, with stock firmware, if you still need it.
I'll create a new thread Tomorrow, in which I will insert a detailed guide on how to revert to stock configuration of the ZenWatch.
I need it!
EmilioDallaTorre said:
Hi,
I can provide you a TWRP backup of my ZenWatch, with stock firmware, if you still need it.
I'll create a new thread Tomorrow, in which I will insert a detailed guide on how to revert to stock configuration of the ZenWatch.
Click to expand...
Click to collapse
If you can, please share it... I have my Zenwatch softbricked and can`t find the stock image anywhere.
Grazie mille Emilio!
nereo said:
If you can, please share it... I have my Zenwatch softbricked and can`t find the stock image anywhere.
Grazie mille Emilio!
Click to expand...
Click to collapse
Hi,
you can find it here.
It's a backup of my personal asset of the watch, so please cleanse data and cache before booting it up.
To reset your device to stock, you need to download TWRP recovery for ZenWatch and use it to restore this backup (that you have to copy into the watch memory with MTP file transfer in TWRP),
then you can find your stock recovery here.
Remember: to flash a recovery, always use
Code:
fastboot flash recovery recoveryfile.img
Happy flashing!
Booyah!
EmilioDallaTorre said:
Hi,
you can find it here.
It's a backup of my personal asset of the watch, so please cleanse data and cache before booting it up.
To reset your device to stock, you need to download TWRP recovery for ZenWatch and use it to restore this backup,
then you can find your stock recovery here.
Remember: to flash a recovery, always use
Code:
fastboot flash recovery recoveryfile.img
Happy flashing!
Click to expand...
Click to collapse
That was exactly what my watched needed. It came right up and synched with my phone immediately. Aaaaaand then promptly powered off once it came off the charger.
I strongly suspected that the battery was shot, but without a working OS on the phone I couldn't be sure a new battery would be worth the expense. Now that I know the watch works I'll hunt down the battery.
Thank you so much!
Any chance one of you could do the same for me? Im stuck in the CSC fastboot loop
Asus Zenwatch 1 firmware
EmilioDallaTorre said:
Hi,
you can find it here.
It's a backup of my personal asset of the watch, so please cleanse data and cache before booting it up.
To reset your device to stock, you need to download TWRP recovery for ZenWatch and use it to restore this backup (that you have to copy into the watch memory with MTP file transfer in TWRP),
then you can find your stock recovery here.
Remember: to flash a recovery, always use
Code:
fastboot flash recovery recoveryfile.img
Happy flashing!
Click to expand...
Click to collapse
Hi
Your first link isn't available anymore, I'll be so appreciated if you put it up again?
Frank2406 said:
Hi
Your first link isn't available anymore, I'll be so appreciated if you put it up again?
Click to expand...
Click to collapse
Have you that image? I have AsteroidOS but I can't go back to android wear...
Frank2406 said:
Hi
Your first link isn't available anymore, I'll be so appreciated if you put it up again?
Click to expand...
Click to collapse
Hi,
I re-uploaded the backup and put a little guide on my blog.
You can find them here.
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
arnauete52 said:
Have you that image? I have AsteroidOS but I can't go back to android wear...
Click to expand...
Click to collapse
Hi,
I re-uploaded the backup and put a little guide on my blog.
You can find them here.
Stock image's link no longer works...
Please kindly re-upload!
TIA
while following these instructions in the youtube video named Moto G6 2018 Install Twrp & Root Easy Tutorial 757 or 12:44 at this part i must have downloaded the wrong file since my build model is XT1922-9 type M373B could someone help me resolve me issue so i can fix my phone and finish the root cause my phone refuses to boot
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Jleeblanch said:
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Click to expand...
Click to collapse
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
kc02141994 said:
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
Click to expand...
Click to collapse
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Jleeblanch said:
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Click to expand...
Click to collapse
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
kc02141994 said:
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
Click to expand...
Click to collapse
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
ok that problem solved now im stuck on an infinite bootloop after i do the parts where the guy says wipe then download those files from the sd card and when i reboot the phone it does says N/A on the top left and starts boot looping
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
i really need help on this i cant finish the root i dont know what im doing wrong im up to the part in the video i watched and after i finished doing that part it begins infinite rebooting and i dont know what to do i installed the right file did everything he did but instead of getting the message in the center i get N/A on the top left and then infinite reboots
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
kc02141994 said:
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
Click to expand...
Click to collapse
Ok, well we're getting somewhere at least. Sounds like you have the right boot.img at the very least. Now we need to find you the right stock firmware (or even at minimum a system.img and vendor.img from some else with the same device).
I'll look around to see what I can find.
Next thing I need from you is to connect your device to the computer and reboot to bootloader and get me the output of..
Code:
fastboot getvar all
and copy/paste it to https://hastebin.com or copy/paste it to a text file and upload the text file as an attachment here (or wherever you want and post the link) so I can review it. That should tell me what I need to know to help you a little better. Do NOT just copy/paste the output into a post please.
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]
Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
I am too facing this problem. In case you got any solutions please let me know too.
Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!
veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.
Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there
Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.
Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum
kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.
@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards
Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.
I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.
Hello, does anybody know when a recovery for the moto G7 play XT1952-4 might be released? I am eager to root my new phone.
I am also looking for the recovery of Moto G7 Play, I unlocked my BootlLoader to make Root and I do not think any Recovery
You don't need TWRP to root the phone. As long as the bootloader is unlocked, you can root with Magisk. Select the Link To Installation Instructions and follow the Boot Image Patching section. It requires using ABD commands, and although it looks/seems complicated, it is actually very easy. Plus, you will have learned something as well as root your phone.
If the G7 Play is actually code-named "Channel", then this link will give you stock firmware for you to download and extract the stock boot image.
Magisk boot.img
Ok I got the retail Canada ROM. Now I am going to extract boot img and patch it with Magisk manager. Once patched I am going to flash it to my phone using abd fastboot? At this point it will be rooted or do I use SuperSU to root? Under software channel on my phone it says "Bell" but the build number and model number matched up. XT1952-4 PPY29. 105-57 so it should be good hopefully.
Thanks
Error: cannot open 'magisk_patched.img'
Must be wrong Rom. Everything worked fine until I had to flash it. I put patched IMG right in adb directory and opened a command window from there but when I tried to flash it I got the error cannot open file. Oh well I think I will wait for a recovery it's the easy way for me.
Thanks
Code named 'channel'
There are 2 more versions of it in the list you provided. Not sure what the abbreviations are before CA for Canada but I will try them too. If I get the same error when flashing these patched boot.imgs I will have to wait for a recovery. Hopefully it won't by be too much longer. I just hope there will be a recovery.
Thanks
Continued error when flashing patched files.
I have tried 3 boot images from 3 different retail Canada firmwares. All 3 patched alright by magisk manager but when I try to fastboot flash boot magisk_patched.img I get the same error cannot open file. I must be doing something wrong. My phone's bootloader is unlocked so unless someone has a solution. I will definitely have to wait for a recovery. Hopefully soon!.
Thanks
Dumb question...when you are attempting to flash your patched boot image, is your phone in fastboot mode? Also, you may be able to extract your boot image via ADB. It's been a while since I've done it and am having trouble finding the proper commands, but you can try this:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Click to expand...
Click to collapse
It may or may not work. I hope it does but apologize if it does not.
Furthermore, you will likely have to wait quite a while for a custom recovery (TWRP). The G7 play has A/B partitions, which makes ROM building and recoveries very difficult. There is no separate "recovery" partition with A/B...the recovery is combined within the boot image. FYI - I have a Xiaomi A2 Lite that has A/B partitions. We still don't have a 100% working TWRP after 9 months. Custom ROMs have just been coming out slowly. I was able to root with Magisk using ABD commands though.
This link might provide clearer steps for installing Magisk.
Best of luck!
Yes, it was in fastboot mode. I will keep trying with your new intructions. Thanks for your help.
My mistake
I did not even have adb fastboot installed I was opening a command window out of the folder that was left over from uninstallation. I am about to try it again. It should work now. Stay tuned.
So far
Okay, so I installed adb fastboot and flashed the patched boot file from the RETCA firmware. I got this message " failed (boot a)" . So I tried the flashing the 2nd patched boot file that was from I think BWACA firmware. With this flash I got " not signed or corrupt" then the phone failed to start with bootloader log to confirm.
So I took the original unpatched boot.img from RETCA and flashed it. This fixed the phone so it would start fine making me believe that it's the right boot image but maybe the other firmware boot.img would have fixed the failing to start issue as well. So I think I need to pull the boot.img from the phone itself like you suggested. I am going to read some more and continue. I will figure it out. Any suggestions would be of great value.
Thanks.
Getting Closer
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
jwreidmoto said:
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
Click to expand...
Click to collapse
A few posts back you said you flashed the stock RETCA boot image. If that's the case, then if you successfully pull the boot image from the phone, you are simply pulling the RETCA boot image you already flashed. It seems that the RETCA boot image is the correct one for you phone. I would start completely from scratch with that. To verify which build number you have, go to Settings>About Phone or ( Settings > About Phone > Software channel) and scroll down to Build Number. Match it up to one from link with all the firmware images.
The only other thing I can say is that you should read and completely understand what to do prior to doing it. I am sorry you are having difficulties with this. It really should not be so hard. As I don't have the phone I cannot be of much more assistance. However, once you figure it out, perhaps you can write a quick guide to help others.
EDIT: You should be rooted. SEE POSTS 10-13. Did you check for root?
EDIT 2: I'm assuming that since you unlocked the bootloader, when you reboot the phone the screen goes black and says "Bad Key", correct? That is normal for Moto phones.
2nd, after you root, when you reboot the phone, the screen should go black and say "N/A". Again that is normal for Moto phones.
I understand what you are saying I would also expect the N/A on the black screen that's when I knew I successfully rooted my old phone. I must have the right boot image if flashing it fixed the startup failure. I am going to start all over again and see.
Have to give up.
Tried and tried it's just not going to work. I think it's the patching because the boot file starts out as 32mb and only 18mb after being patched. Flashing has no effect on my phone even though it says 'okay' when I flash. I never get the N/A on boot unless there is a startup failure. Oh well have to live with ads among other anoyyances. My Moto g4 play is rooted I can use than in case a solution comes up. Thanks for all your help.
jwreidmoto said:
Oh well have to live with ads among other anoyyances.
Click to expand...
Click to collapse
DNS66 is your friend! I have used it on other unrooted phones. It was decent from what I remember. Good luck!
Sorry that root wasn't working.
EDIT - If you are up for a little more testing...I just found this. I don't remember if it's what I had to do for my Xiaomi or not, but it makes sense. (Further research - No I did not have to do this). Scroll down to method #2 and look for the part about A/B partitions:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
Edit #2 - I don't give up easily LOL
After any of your attempts to flash the patched_boot image, did you ever boot the phone and open the Magisk Manager app? Doing so should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Neither do I
I have been trying everything since we last talked. Just so you know the link labelled as "this" in your last response is not working. I always opened the magisk app after flashing to see if it was either installed or gave me the option to do a direct install unfortunately, it did not. I have magisk manager installed on my rooted Moto G4 plus and it gives me that option to do a direct install. Will definitely try your new info. Thanks so much for more help. I will let you know.
Still no luck
Without the link I got the jist of what you were saying by the quote boot_a boot_b I tried both consequtively and then tried it for ever possible retail Canada image still no luck. Thanks for your help. I don't know why it's so hard for this phone. I will keep researching.
I'm at about the same place where jwreidmoto is. I purchased my unlocked g7play from Best Buy. First I tried the files in the channel/RETUS folder, these all caused a bootloop. I then tried in the RETAIL folder... still no joy. None of the version numbers quite matched up, and none worked to restore the phone. I finally found a matching file in the AMZ folder, which I was able to use to get the phone to boot up again. So I used that boot.img file with magisk and when I flashed, it gave no errors, no indication anything failed. Unfortunately though, I do not have root access. I started over from scratch and did the process over with the AMZ boot img again, and again no errors, but no root. I've never rooted before, so I don't know if there's another part somewhere I missed, but I do feel like I was able to follow the directions on the g7 thread by mingkee, and performed the steps accurately. I supposed it's just the wrong boot img. The about phone says the software channel is US Retail, and the build number is PPY29.105-36. The RETUS folder only has PPY29.105-43 and RETAIL folder has five different zip files, but none were PPY29.105-36.
You are doing it right
You have not missed any steps. If the boot.img fixed the boot loop then it should be the right one. I had the same issue with a startup failure and fixed it with the RETCA boot.img so I am also using the right one also. I think it's an issue with the model of phone, this method just does not work. We might have to wait a while until someone comes up with a solutuon. I know it sucks.