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
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
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.
I have a Xiaomi Note 8 Pro initially came with China Stable Rom V11.0.3.0.PGGCNXM. It was also unlocked.
I accidentally flashed Global Stable ROMV11.0.6.0.PGGMIXM via MiFlashTool and while it was successful, it rebooted to Recovery Mode with the message "This MIUI version can't be installed on this device".
After that, I pressed "Wipe All Data", so now the device is also locked.
Since there is no OS installed, I cannot access the device and consiquently to use Mi Unlock Tool properly to Unlock it again.
The device is now locked, without OS installed. However I can access Fastboot menu and Recovery mode.
Is there anyway to unlock the device in this state and flash it's original Rom again?
Please if you have anything to suggest that might help me, answer my question. I'm desperate. :crying:
Hmmm. Can you still access fastboot mode? If yes I recommend using miflash pro and flashing the correct rom for your device, or manually flashing all images via fastboot.
You've likely selected Clean all and lock (default setting) which flashed MIUI and locked the bootloader afterwards which bricked the device because of cross-region ROM flashing. Since you can't flash it with locked bootloader your only option is to take it to the service center.
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
RenginaP said:
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
Click to expand...
Click to collapse
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
JuanM2020 said:
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
Click to expand...
Click to collapse
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
RenginaP said:
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
Click to expand...
Click to collapse
https://www.xiaomigeek.com/flash-miui-fastboot-rom-using-command.html
Could you fix it?
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.
If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.
blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19
Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!