Develop Bugs

Bricked after flashing MM (Detected for 5 seconds as Moorefield and disappears)

Hello guys, i'm trying to unbrick my phone, i'm following this guide http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840 but when i get to the end of te install of intelSoC my device is detected as Moorefield for like 4-5 seconds and then it disappears. I've been trying to solve this for like 4 hours now, a little help would be much appreciated.

Fede2797 said:
Hello guys, i'm trying to unbrick my phone, i'm following this guide http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840 but when i get to the end of te install of intelSoC my device is detected as Moorefield for like 4-5 seconds and then it disappears. I've been trying to solve this for like 4 hours now, a little help would be much appreciated.
Click to expand...
Click to collapse
in xFSTK option menu in gp flag override value put 0x80000807 instead of 0x800000807
tick enable gp flag override
change device detection time out to 120
click okay, and press power button for 20 second make sure it powers down now click power button and volume down button. as phone vibrates or computer makes detection sound. release power button but keep holding volume down button. begin download and do nothing untill it gives ok
if you are unable to flash raw firmware after geting fastboot do following steps after 2nd step, don't use asus flash tool
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
in xFSTK option menu in gp flag override value put 0x80000807 instead of 0x800000807
tick enable gp flag override
change device detection time out to 120
click okay, and press power button for 20 second make sure it powers down now click power button and volume down button. as phone vibrates or computer makes detection sound. release power button but keep holding volume down button. begin download and do nothing untill it gives ok
if you are unable to flash raw firmware after geting fastboot do following steps after 2nd step, don't use asus flash tool
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thanks man, i solved it. I was trying to use flash tool but it doesn't work, i'm gonna try with your solution.
-------------------------------------------
I finally did it! Thank you so much. One last question, do you know how can i flash a recovery? Because when i go to the recovery it appears "error" and that android guy.. if possible a stock recovery so i can upgrade to 6.0

Fede2797 said:
Thanks man, i solved it. I was trying to use flash tool but it doesn't work, i'm gonna try with your solution.
-------------------------------------------
I finally did it! Thank you so much. One last question, do you know how can i flash a recovery? Because when i go to the recovery it appears "error" and that android guy.. if possible a stock recovery so i can upgrade to 6.0
Click to expand...
Click to collapse
You already have stock recovery
Whenever the Android guy with ERROR shows, press and hold the power button for 1 sec and then while holding it, press the volume up button. It will bring out all the recovery options. Cheers...

Thanks, worked for me too ! (just i used volume up + power instead of volume down).

[help] ZE551ML crashes, TWRP freezes, no connection in xfstk downloader

Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!

The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.

Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.

audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?

- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?

timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)

@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you

timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help

j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )

@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:

j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware

Thanks for your quick anwer. Will try to get through it haha :good:

DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse

Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins

Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help

@j4y_ha
Goodluck

timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step

timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin

Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw

Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse

ZE551ML keeps vibrating, won't start.

Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.
The phone keeps vibrating every minute as if it was booting, but the screen doesn't light up, nor the led while charging.
I've read a lot of thread with similar problems, which were solved by replugging the battery, but this solution won't work for me.
Here is what i've tried so far:
-Changing the charger/cable
-Replugging the battery
-Leaving the battery unplugged over night, then replug
-Leaving the phone rest for 8 hours
-Pressed every possible combination of button for 20 sec
None of the above solutions changed anything.
I don't think that it could be a battery problem, the phone shut down at arround 40% and my multimeter still indicates a voltage of 4.20V at the battery.
Hope you guys will be able to help me !
Thanks

4.2 means battery more than 80 percent. you seems bricked. use the following guide step by step read everything carefully. any question post there in the thread. please search around before starting new thread.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

@Solasmeryl
Was you in M when you bricked ?
If you was and are getting 'continuing to os ' error in xFSTK .
Try this > in xFSTK
1) fwr dnx = your normal file you used before
2)Ifwi = try this >
http://www.mediafire.com/file/xjhv9gfiv5sn7xx/tmp_17491-ifwi_ann_a0-mofd_v1-ze551ml1929259488.bin
3) is skipped = per usual
4) OS = your usual posignbin you used before
If you get bootloader now , it will be 0094.0183 for M , flash M raw file.
Then you flash M raw file (twice) in AFTools, raw M = 4.21.40.184
First flash for approx 3 to 4 mins, where on-screen cmds pauses on "RESULT=OK" on phone.
Close flashtools , force close.
Open flashtools again , input raw , press vol+ (once) and serial now is corrected , flash till it boots into system.approx 8 mins
Notes..
If serial number is correct after xFSTK flash , you only flash raw once only. Flash Twice if serial is 0123456789ABCDEF
.
.
When connecting to xFSTK. Connect data lead.
Press power and vol-, press download , connect phone, release vol- and power
If fail , press vol + and power till first of two vibes , release buttons , hit download button in xFSTK at the same time you release buttons on phone , tricky but you can do it .
There's AFT and links to needed files in my unbrick thread in my signature , even a video showing flashing procedure

Fixed LINK , added M .184 ifwi for xFSTK

@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.

Solasmeryl said:
@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.
Click to expand...
Click to collapse
Nothing to do with Motor i`m afraid
Battery dead , will be the main cause .
Leave connected to charger for a good few hrs :good:
Each flash in xFSTK uses approx 10% battery , more if you sit there watching it `continuing to os`
See my video in link -- the button process and connection -- i do it just the once , admittedly i have unbricked many zens and know exactly when to press dload in xFSTK :good:
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
ps cm13 was based on LP mainly , only the latter versions and cm 14 had bootloader upgrades.
So return to original flashing files

Solasmeryl said:
@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.
Click to expand...
Click to collapse
Just FYI, if you were on cm13 official then your base was LP not MM. Even though it's an MM rom
Sent from my ASUS_Z00A using Tapatalk

timbernot said:
Nothing to do with Motor i`m afraid
Battery dead , will be the main cause .
Leave connected to charger for a good few hrs :good:
Each flash in xFSTK uses approx 10% battery , more if you sit there watching it `continuing to os`
See my video in link -- the button process and connection -- i do it just the once , admittedly i have unbricked many zens and know exactly when to press dload in xFSTK :good:
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
ps cm13 was based on LP mainly , only the latter versions and cm 14 had bootloader upgrades.
So return to original flashing files
Click to expand...
Click to collapse
Ok, so i charged up the phone, went back to the original file as suggested. Vibrations are back, but i still can't figure out how to pass the "Continuing to OS" error :/
Here is how i seem to understand the steps:
1. I Click begin download (which start the 120sec timer)
2. I press Power and Vol - for 4 sec then release
3. I Connect the phone to the PC, hear the windows "device connect" sound
4.Messages show up in xFSTK, sometimes errors, sometimes the download begins, and back to the "Continuing to OS"
5.The phone vibrates, the software attemps 20 reconnect then aborts.
I've also tried a lot of different combinations such as pressing power after plugging, not pressing power at all, etc (The software indicates 41 tries).
It just seems that the phone is completely dead :/
Thans a lot for the help, i really hope that i doesn't bother you too much by making mistakes !

Do you usual flash , soon as you see continuing to os Press power and vol + , at first of of two vibes - release and hit download.
Note , if only one vibe , re press and keep pressed vol+ and power immediately.
Do press download first like in the video..but you have to double click it to stop and to begin again at the exact time of releasing at first of two vibes
Ps , depending on pc speeds etc etc , it is wise to come off the internet , disable anti virus , clean pc from junk, c cleaner free is good and do a reboot.
Also , some people report it just flashing after hrs of failures by just leaving phone connected after a failure with xFSTK still open, then restarting flash after a good break of half hr plus

@Solasmeryl
Hows it going ??

timbernot said:
@Solasmeryl
Hows it going ??
Click to expand...
Click to collapse
No change :/ even tho i've tried every button timing possible i guess.
I've noticed that pressing Power and Vol- before plugging in the phone always leads to an error. The only way to get to the continuing to os is by pressing these buttons while the phone is already connected, and then hit download.
Could there be any other software problem that could **** things up and that i forgot to mention ?

Solasmeryl said:
No change :/ even tho i've tried every button timing possible i guess.
I've noticed that pressing Power and Vol- before plugging in the phone always leads to an error. The only way to get to the continuing to os is by pressing these buttons while the phone is already connected, and then hit download.
Could there be any other software problem that could **** things up and that i forgot to mention ?
Click to expand...
Click to collapse
Can you ignore xFSTK for a moment
try this without being connected to pc either.
(A)Press and keep pressed power and vol+ . Does your phone vibrate (twice) ?

timbernot said:
Can you ignore xFSTK for a moment
try this without being connected to pc either.
(A)Press and keep pressed power and vol+ . Does your phone vibrate (twice) ?
Click to expand...
Click to collapse
Yes, the phone vibrates twice

Solasmeryl said:
Yes, the phone vibrates twice
Click to expand...
Click to collapse
Well , somehow you gotta release both buttons and hit download at the same time at first vibrations of the two .
Do what you need regarding pressing power and vol- to connect initially . Then go about trying to get the above two vibes process while downloading . Be fast to double click download at the first of two vibes --
Thats it !
That is all anyone has to do :good:
One other thing to try is - just try power , on its own(like power off), press and keep pressed after initial connection download process, once it vibrates - release and -- go for the power and vol+ 2 vibe process again. Get ready to hit download !
---------- Post added at 05:42 PM ---------- Previous post was at 05:25 PM ----------
If that doesnt work ^^^ i will begin to start asking questions about the settings you have applied
Double check this ->
(fast forward to 18:30 mins in of this video for settings to be modified in XFSTK re... changing GP over ride to 0x80000807 ) . Make sure you modified the correct CRC+ box at the bottom
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be

timbernot said:
Well , somehow you gotta release both buttons and hit download at the same time at first vibrations of the two .
Do what you need regarding pressing power and vol- to connect initially . Then go about trying to get the above two vibes process while downloading . Be fast to double click download at the first of two vibes --
Thats it !
That is all anyone has to do :good:
One other thing to try is - just try power , on its own(like power off), press and keep pressed after initial connection download process, once it vibrates - release and -- go for the power and vol+ 2 vibe process again. Get ready to hit download !
---------- Post added at 05:42 PM ---------- Previous post was at 05:25 PM ----------
If that doesnt work ^^^ i will begin to start asking questions about the settings you have applied
Double check this ->
(fast forward to 18:30 mins in of this video for settings to be modified in XFSTK re... changing GP over ride to 0x80000807 ) . Make sure you modified the correct CRC+ box at the bottom
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
Click to expand...
Click to collapse
Hi, sorry for the delay, i had a lot of work the past two days.
I've tried everything you said, double checked every parameter, and even tried the manipulation on another computer, but there is no change.
The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB.
Moreover, i don't really understand what you mean by " double click at the first 2 vibes", since the button gets "gray" after 1 press, and there is no way to double click it.
I'm sorry, you have put a lot of effort into helping me, but i really think that my phone may be more damaged than a simple brick :/

Solasmeryl said:
Hi, sorry for the delay, i had a lot of work the past two days.
I've tried everything you said, double checked every parameter, and even tried the manipulation on another computer, but there is no change.
The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB.
Moreover, i don't really understand what you mean by " double click at the first 2 vibes", since the button gets "gray" after 1 press, and there is no way to double click it.
I'm sorry, you have put a lot of effort into helping me, but i really think that my phone may be more damaged than a simple brick :/
Click to expand...
Click to collapse
Hi there ,
From first line of original post >
"..............Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.........................."
And last reply ..........
"..........................The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB..........................."
Suggests it will be USB board /port /cable :good:
Do the same again with data cable connected to phone but not connected to anything to rule out cable :good:

sukhwant717 said:
4.2 means battery more than 80 percent. you seems bricked. use the following guide step by step read everything carefully. any question post there in the thread. please search around before starting new thread.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
sukhwant717,
I registered (not only) but basically to say thank you.

kefalva said:
sukhwant717,
I registered (not only) but basically to say thank you.
Click to expand...
Click to collapse
Glad to know it helped

timbernot said:
Hi there ,
From first line of original post >
"..............Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.........................."
And last reply ..........
"..........................The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB..........................."
Suggests it will be USB board /port /cable :good:
Do the same again with data cable connected to phone but not connected to anything to rule out cable :good:
Click to expand...
Click to collapse
I'm not sure to really understand your last sentence ? Do you mean like removing the 2 power cables inside the USB ?
I've tried with different USB cables, and no change either :/

Solasmeryl said:
I'm not sure to really understand your last sentence ? Do you mean like removing the 2 power cables inside the USB ?
I've tried with different USB cables, and no change either :/
Click to expand...
Click to collapse
You can now only pray it is the USB board and not Mainboard , order a new USB board and a `new` Data cable, do not use old data cables with new board just incase your phones charge port has altered pins on either or both cables or data cable has changed pins on usb or vice versa :good:
ps , make sure it is a quality data cable you order too, some sell data when only a charge cable

How to "debrick/unbrick"an oppo find 7/7a

Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.​Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
1a)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
1b)goto Google and search for Qualcomm qd loader.download,install and restart your pc.
2)After restarting,Extract the file from OPPO UNBRICK TOOL and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry it isn't corrupted,just follow through↓
4)disconnect your device battery,then open the software and press start,after that connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button
5)please wait patiently as it is reflashing stock rom to your device.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
P/S:if your device is softbricked,you just should disconnect your battery,and then open the software and press start,then connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button.
If your device is hard bricked(like mine)only holding the power button could work as well
*UPDATE* 24/2/2019
-If you guys still have any concerns kindly contact me through twitter (0728mal)
*UPDATE* 4/7/2020
-yes it is still working guys,no worries kayy
-no you don't need internet for it to work,the software already has all the files needed to flash the device,which is why the file is pretty big.
best regards,
Akmal

Link updated :good:

akmlfhm said:
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.​Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution which make my phone came to life again-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
-make sure to charge the phone first even if you do not know if it charging or not
1)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
2)Extract the file and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry its not corrupted,just follow through
4)Connect your phone to PC and press the power button until you heard some like mounted usb alert on windows.(its ok aslong windows does not detect it on device manager but its ok if you can hear the alert sound.
5)back to the software,no need to mess around with it.Click on start until its downloading a "new life" to your phone.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try to turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
best regards,
Akmal
Click to expand...
Click to collapse
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?

Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you

Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
On Mac's OS, you can always install Windows on its proprietary virtual machine and get the process going that way.

babyenchantress said:
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Click to expand...
Click to collapse
hello there!I'm really sorry for not checking this that often and really sorry if i let you down because im too busy with my schools work
btw before my computer can detect my phone i have to download a driver which detect qualcomm processor for my oppo then it can be detected by my pc therefore i can do the unbrick process:good:

Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
yeah you can try WINE also but i never have any experience with mac os before so i cant guarantee that it will work considering that you're configuring your drivers,which can go wrong if not done correctly

So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install

true_friend2004 said:
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
Click to expand...
Click to collapse
Hello there.have you tried downloading the "Qualcomm"
Driver software on your PC?

is it necessary to remove the battery? I don't have tools for opening my phone and it's battery is non-removable

Perhaps an important step is missing. The Qualcomm qd loader driver is may not signed. I had to boot into the extended start menu on Windows 10 and disable the driver signature check - point 7 - and could now successfully debrick my find7.

Question Oppo Reno 6 5G (PEQM00) bricked

Hello
I need help here I have tried everything to fix my oppo reno 6 5g chinese version and now I am at a dead end can anybody give any suggestion.?
My phone is on black screen and its showing only for 2 second on device manager as some other version which made mtkclient tool to failed handshake and sp flash tool to give error.
like attached screen shots.
In device manager it is showing as V_1632 which is idk what.
I tried all combination but phone is at black screen now.
Device is not going into BROM mode.
Any help will be much appreciated.

hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.

XDHx86 said:
hmmm, at least you didn't flash the wrong preloader, so we can save this pretty easily actually.
Just simply follow this guide:
Download VCOM drivers: Mega Link
Install LibUSB and filter your device driver after connecting it through USB while pressing on both vol + and vol - buttons.
Install Python and install it's requirements using the command `pip install pyusb pyserial json5` in CMD.
Extract MTK bypass util anywhere and run the command `python main.py` in the extracted folder through CMD while your device is connected (KEEP HOLDING VOL + AND VOL - DURING THE BYPASSING!!!).
Open SP and flash the scatter file of your stock ROM (PLEASE ONLY FLASH YOUR STOCK ROM) (ONLY USE DOWNLOAD MODE).
Then reboot your device and it should work.
If you face any issue or don't know how to do a step of those just reply to the thread. I'll try to attach some pictures, just be aware I'm only online at about this time.
Click to expand...
Click to collapse
I did everything like you described step by step first 3 steps were installations so that went ok but in step 4 I followed your instructions but nothing happend.
I pressed VOL up+VOL down buttons but nothing happend for long time.
Here is screen shot of CMD
I think preloader is damaged or something because not its not going in BROM mode at all only black screen.
If i press VOL up+VOL down+PWR buttons then in device manager phone is shown as I shared screenshot in post but only for like 2 seconds.
like this
Also in SP flash tool detects the phone but when I hit the downlad button it gives error STATUS_ERR instantly not even start the process.

Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install

XDHx86 said:
Most likely you didn't use LibUSB right, just open the app connect the device and when you see it in the list of devices highlight it and press install
Click to expand...
Click to collapse
I did exactly what you said but the problem is phone is like not responding to VOL+andVOL- buttons command, in LibUsb where it says waiting for devicec i pressed both volume buttons and connect and waited for 1 minute atleast but nothing attached screenshot for rfrence. its just empty.
But when i press all HW buttons then LibUsb shows a device then I select it and install and completes it but thats the problem it only shows for 2 second then gone.
like this
what should i do now?

I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.

XDHx86 said:
I think you fried the preloader mate, you need to do a test point connection and force the device to connect to the cpu directly.
If you're unsure how to do that please send your device to a professional instead.
Click to expand...
Click to collapse
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?

mamomia said:
yeah im not sure how to do that. I think too much flashing may have resulted in that.
Thank you for your help.
but in case if they didnt take it then im afraid im gonna have to try that is there any tool or process or help where i can learn more abt this test connection process?
Click to expand...
Click to collapse
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.

XDHx86 said:
It's device specific so I'll need to look into it and reply to you, but generally speaking you're going to connect a USB to the device through specific CPU pins on the motherboard.
Click to expand...
Click to collapse
Oh it means I need to open up the phone.
That will be the problem because I dont have the tools to do that.
I guess first I have to try and find some professional then.