Related
Hey people, can anyone get me a MTK droid backup of UMI ZERO? I need it to see if i can recover my bricked UMI
pleaaasseee.....
Also, it seems my scatter file backup from MTK does not have all t info?? and SP flashtools does not accept the ones included in the Ota-updates... so if anyone please can also get me a good scatter file ... i would be much apreciated.
Hello, you can get the rom including scatter file from Needrom! Just flash trough sp tool and you will be fine.
Sent from my UMI ZERO using XDA Free mobile app
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway
reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway [/QUOTE
please tell me how did you make it work...as i am in the same boat..the pc wont recognise it
Click to expand...
Click to collapse
reisamm said:
I tried but SP tool does not accept the scatter from that file... but solved... as I connect it in META mode to the PC he booted again... Thx anyway
Click to expand...
Click to collapse
please tell mew how you did it . i am so upset that my phone is absoluteley dead
Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers
reisamm said:
Hi there raducux,
Well, this was about another situation, but mixing with ROM's cooking I was able to brick it again it was mrsim who help me (mod at china-devices.com, credit where is due). But I will tell you how I did it.
You need to have the adb android drivers installed and flashtool v5.1 or up (the one I used, but some people use the 3.1 version).
Download this ROM from needrom (scatter file compatible with FT).
Link: http://www.needrom.com/wp-content/uploads/2014/11/Y800_UMI_20141104_1907xx-s7yler.zip or
http://www.needrom.com/download/umi-zero/
Extract, and in flashtools select the scatter file inside the directory you extracted. Press flash, and (after pressing flash) connect the phone to the USB port holding the volume down key (so the phone connects in META mode), and the process should begin.
If all works well after flashing the phone should boot the new ROM, its version 3.01 so you have to upgrade it.
If that does not work, tell me a few things... I suppose the phone does not start or appear the 'Zero' logo, but tell me if when you connect it to the computer you ear the normal plugin USB sound?
FlashTools (all versions)
http://helpadude.com/sp-flash-tools/
Universal ADB Driver
http://www.needrom.com/download/universal-adb-driver/
Tell me if it worked, or if you need more help tell me what happened and how the phone responds. lot of people here also that can help. My 1st thing I check when buying a new phone (for many years now), is if it's 'XDA' Supported...
cheers
Click to expand...
Click to collapse
indeed. i too have been messing on xda a lot for a long time.
i managed to get into twrp again.
so that must be good...after. the battery died..;.butr mtk preloader doesnt instal;l
please tell me..first i need to hit download only...and after that.... ? the steps are a bit missleding .
---------- Post added at 03:10 PM ---------- Previous post was at 02:58 PM ----------
i managed to bioot the device in emui !!!! this morning..i could acces twrp. pressing volume down when connected to pc ..and the chinesse recovery pressing volume up ... rootjoy cant flash the device as it sais it is unsupported, now...i reeallly need to know the steps for going back to stock
---------- Post added at 03:29 PM ---------- Previous post was at 03:10 PM ----------
i am running antarct s emui . with twrp recovery... i need dto know the sp flash tools steps correctly to flash back to stock
preloader doesnt install correctly in pc because volume down...takes me to twrp...and volume up...to the chinesse recovery of huawei,
so preloader starts installing, but when in recovery..it gets dissconected
Could you tell how did you put it in meta mode? I have a Zero with no preloader and in windows it shows up as unknown device. No matter how I try to boot it up (vol- vol+). Other than showing in windows, it's dead. Is there a way to revive ti?
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Follow the steps:
http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528
Same happend to me, can't even unbrick it.
Z00A bricked
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
kazzot17 said:
Same happend to me, can't even unbrick it.
Click to expand...
Click to collapse
Did you and all others who are having trouble with the zenfone make sure to flash any custom kernel for your rom?? If one is available.. Just a suggestion.. Make sure you're trying to flash the right device and exact model, any follow any guides properly. Go back over and read each step thoroughly just to rule out any steps you may have missed along the way
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
Sent from Sony Xperia Z5 E6653
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Yeah, I got that far. I'm hoping for a way to unbrick it now.
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
kenbo111 said:
The problem is they are trying to flash official MM with twrp. Can't be done that way.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
I was on stock rom.
TheTecXpert said:
Ahh, yes.. In that case then you're spot on. To flash any stock firmware, the device needs to be set back to stock factory defaults. And thats because the stock kernel needs to be present so that the stock firmware (official) is able to be flashed properly without bootloops/bricking etc. Think of it as a safety feature
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
[email protected] said:
I was on stock rom.
Click to expand...
Click to collapse
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
That is what I'd like to do but I have not found a way to do that.
TheTecXpert said:
I understand that part, but since you have twrp installed, you're not actually considered as being on complete stock.. You're using a custom kernel right? Hence the whole reason why you cant flash stock MM rom via twrp
You need to flash it using a flash tool program for your specific device. (Sony = flashtool, Samsung = Odin. Etc etc).. If you dont need to back anything up orif you already have. Then just flash the stock rom via your devices flash tool using your pc or or via a method that is specific to your device..
There's really no way around it unless you wanna brick your device..
And another person has also mentioned the same thing. That you wont be able to flash stock rom via custom recovery. It ain't gonna happen..
You have to reset your device completely to stock.. And that includes STOCK kernel..
Sent from Sony Xperia Z5 E6653
Click to expand...
Click to collapse
same here
Ok ... first of all..
Do you have all the necessary files on your external SD CARD ready??
------------------If yes then continue on-------------------
1. Open up adb and fastboot with admin privileges..
2. connect your device to your PC in ADB mode
3. in ADB cmd type adb reboot bootloader
***If you have already completed step 4 below previously and you are sure you already have a custom recovery (TWRP) installed on your device, then skip straight to step 5***
4 fastboot flash recovery [nameofrecovery].img (Without the brackets and also Make sure The Recovery.img file is SPECIFICALLY for your MODEL.. ***ZE550ML***
5. While your device is still connected to your PC in either ADB or fastboot mode
in ADB just type the following command below
(if connected via adb) - adb reboot recovery or adb boot recovery
(If connected via fastboot) - fastboot reboot recovery or fastboot boot recovery
IF you device reboots in to TWRP successfully, then all you need to do from this point is...
1. wipe data/Factory reset
2. wipe cache partition
3. reboot now.
you should now be able to boot your device like normal
good luck
let the process complete.. after factory reset is complete proceed
QuietLion said:
I used twrp to update the MM zip. it hung for hours so I turned it off. now all I get is a black screen and 2 vibrations. sometimes I can get to fastboot but no matter what I select it restarts to a black screen with 2 vibrations or occasionally a group of color bars. ADB cannot see the device. I have installed intel SOCusb and tried updating the with xFSTK. device manager sees a moorefield device then it disappears, in and out. xFSTK gets through updating dnx_fwr.bin and ifwi.bin but it loses connection to the moorefield device and fails to continue on to update droidboot_dnx.img.POS_sign.bin. I have uninstalled and reinstalled intel SOCusb and xFSTK several times and tried installing them in different orders. same problem. Moorefield device loses connection. I also tried using Asus Flash Tool. sometimes it detects my device, other times not. when it does detect it and I select the raw file and it says it is flashing but nothing happens after hours. I'm not sure what else to try.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
t00lshed said:
same here
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
utsav.goswami1986 said:
Hello xda members.
I had updateted my asus zenfone 2 ze550 ml to marshmallow by using custome rom. First i installed TWRP recovery successfully. Then took update zip in sd card. Then i flashed phone using that rom. But after flashing is done phone rebooted and it only shows black screen with bright light. Somwhere if we touch on screen then at some specific points screen shows vibration.. but only black screen is there. And then i can only force restart it and forcely shut down it.
Then i thoght to do everything from begaining. Now conditions is that if i connect it to my pc and tried to find adb devices. Cmd window shows device connected in recovery mode. Now i have original rom of asus zenfone 2 but how to flash phone with it when there is no display on phone and computer shows device is connected but in recovery mode.
Please help. Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try the following guide if helps hit thanks button
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------
try the following guide if helps hit thanks button. any question post in that thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
t00lshed said:
Hi! yes, i did that, my phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
pd: excuse my english.
Click to expand...
Click to collapse
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
sukhwant717 said:
can you post a screenshot of your pc of xFSTK window. i mean in which columns you selected three files.
does it give you four color bar?
Click to expand...
Click to collapse
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
t00lshed said:
yes of course, is attached. The phone gives me four color bar (pink,yellow,other pink i think and green)
Click to expand...
Click to collapse
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
sukhwant717 said:
when you get 4 bar. just follow the steps given in following link. do not use asus flash tool. when you get 4 color bar go to adb and fastboot folder and see if fastboot recognize your device.and please post your question in the following thread it will help others too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
i will answer any quest after two hours gotta go somewhere
Click to expand...
Click to collapse
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
t00lshed said:
ok thanks! I did what you tell me but nothing happen, fastboot devices dont recognize my zf2 after xfstk and the 4 bar color.
Click to expand...
Click to collapse
can you please upload xFSTK log file
you are using windows 10 did you disabled driver signature enforcement before installing xFSTK and driver?
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Akshatpunj said:
please help me unbricking my device currently i am unable to boot into edl, fastboot or recovery. The phone keeps on vibrating and no display.
What i did wrong was that I tried flashing a custom boot logo as said in a thread and flashed splash.img and it resulted in this.
Please help me!!!
Click to expand...
Click to collapse
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
links :
drivers: https://mega.nz/#!FJRH2b6B!QlS9-7ppEiP9Nw_htWSMtYQWOk9KDxDxImtJZ66usaw
QPST: https://mega.nz/#!dcAQgSZT!C5JhNLnsOru6y_cX52yGzMkgfnriBY0am7nW45Bzsm0
rom: https://mega.nz/#!dFpn3BYb!Eq2i2ldpA8UJnlkjijCh4fM7EdLSaleWBRmW5rJNI84
Click to expand...
Click to collapse
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Akshatpunj said:
Thank you sooooooo muchh!!! I almost tried everything and lost hope! This method worked like a miracle, i wish i could hit the thanks button a 1000 times! Thanks again!
Click to expand...
Click to collapse
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Akshatpunj said:
Sure, thanks for the advice.
Btw were you able to change the splash.img/boot logo?
Click to expand...
Click to collapse
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
ADDICTED777 said:
This state isn't named as it is hard bricked ...if it was it won't even vibrate at all...that's we call it as a hard bricked device... it was soft bricked .... in a BOOOOOOOTLOOOOOOOOOOP...
There r various type of bootloops
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
Oh yeah two times...listen here the main thing for the devices is to choose the r8 image...should be less then 200kb & as much as less color... make sure to do it with 16bit(or less) for PNG
Click to expand...
Click to collapse
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Akshatpunj said:
Oh ok! I thought i hard bricked my device but luckily you helped me
Okay i will try to change boot logo tomorrow again. Thanks a lot!
Click to expand...
Click to collapse
Yo there is a button for that ...u know I'm kind of GREEDY...
ADDICTED777 said:
Yo there is a button for that ...u know I'm kind of GREEDY...
Click to expand...
Click to collapse
Already done...
ADDICTED777 said:
Always remember mate...
Computers & smartphones are such a thing u can't damage them until and unless u broke them... so do whatever u wanna try ... test them out... so be productive n believe in urself that u can..
Click to expand...
Click to collapse
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Sahaj Desai said:
I have the same problem. I went to flash a boot image and I messed up. QFIL does not detect my phone maybe beacuse Qualcomm drivers are not getting installed using the INF file.
I have shut the vibrations using the power button step. But as soon as I plug it in with volume up held down, it starts all over again.
---------- Post added at 12:26 PM ---------- Previous post was at 11:43 AM ----------
I have disabled the driver signature verification while rebooting using F8 key.
However, I still get the same error message while installing the INF file that The INF file you selected does not support this method of installation.
---------- Post added at 12:36 PM ---------- Previous post was at 12:26 PM ----------
Please help!!!!
Click to expand...
Click to collapse
u need a video tutorial that shows how to install .inf file
here is the one:
https://www.youtube.com/watch?v=lJ7WTRW7psA
Now before u proceed make sure u have disabled the driver signature verification.
ADDICTED777 said:
u need a video tutorial that shows how to install .inf file
here is the one:
Now before u proceed make sure u have disabled the driver signature verification.
Click to expand...
Click to collapse
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Sahaj Desai said:
I did it using Qualcomm drivers in .exe format.
Now the phone is working fine.
Click to expand...
Click to collapse
:good::good::good:
Hei!!! You are the best. I followed your instructions and it seems it works 100%. You saved my day. I cant thank you enough.
ADDICTED777 said:
ok here what u do:
1. I know the device isn't getting charged, no logo.no recovery,no flash-boot,even won't get detected on windows but,don't panic... first thing is to believe in urself that u can fix that device...
2.. second powering of ur device, so to do that observe the vibrate pattern carefully... very carefully... you'll notice while holding up the power after some vibrations(for me 12) it'll skip one vibration.that's the moment my friend release the power button.
3. so now u have to flash the ROM with QFIL & the cyanogen QFIL file ...
4. now before get into the process make sure u download all the drivers(ZUK drivers & Qualcomm Drivers)
5. installing drivers:
boot ur system into the state that ensures driver signature verification is disabled install zuk drivers if u haven't.
now install Qualcomm Drivers depending upon ur system
6. install Qpst
7. now unzip the ROM.
8. run Qpst as admin
9. select the flat build mode on Qpst and browse the extracted rom folder...u'll get to see the ".mbn " file, select it , load XML
10. now the most important thing press the vol+ button and plug the device (it won't get detected),now after 1sec of pluging it press power button it''ll get detected and press the download button ....
11. wait for the flash....get a cup of coffee..
12. u'll get a messege like download success... u r done mate..
Click to expand...
Click to collapse
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Walter Black said:
hey bro I just accidentally rebooted my zuk z1 in edl mode via all in one tool, but after rebooting in edl mode, screen went off and it didn't boot up again and now pc is not recognizing my device nor does the qfil detects it, its power button does not work so tried it while holding the volume up button but it's not working. I have got qpst file and zuk drivers are also installed. now please someone help me out bro. ;(
Click to expand...
Click to collapse
keep it charged overnight... fix the power button...then try the mentioned method...
ZUK Z1 Hard Bricked
Greetings, everyone. I've got a hard bricked zuk z1 which just went into the state all of a sudden.
I was using lineage o.s pie roms, and had faced some Random Reboots also. Not sure what happened, but here's what i did:
Installed zuk drivers
installed qualcomm drivers
installed adb and fastboot(minimal abd and fastboot)
installed qfil, which comes with QPST v2.7.0.460
--------------------------------------------------------------------------------
Downloaded the zuk stock firmware files
pressed vol+ and plugged the usb
Got detected in 9008 mode
QFIL also detected it and chose the correct files and started downloading in FLAT build
mode
now, QFIL shows this error at the end:-
Code:
10:17:52: INFO: Looking for file 'gpt_main0.bin'
10:17:52: INFO: Looking for file 'gpt_backup0.bin'
10:17:52: INFO:
Total to be tansferd with <program> or <read> is 78.85 MB
10:17:52: INFO: Sending <configure>
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
10:18:17: {ERROR: Could not write to '\\.\COM3', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times}
Writing log to 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt', might take a minute
Log is 'C:\Users\HARRY\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Fail:Process fail
Finish Download
Hope someone can help me . Oh, by the way, the bricking is like "fully-dead" bricking. No vibrations, display, led, nothing.
I feel i haven't done anything wrong in the steps also. SO, How to decode this situation??
i am face same problem "help please expert" my zuk z1 show logo and blew light after 10se not display on screen when touch with pc via usb many partition opening with error how to solve it
Hard partition damaged
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
naseera422 said:
helo expert zuk z1 vibrate and show blue light black screen no display after firmware via qfil completed on PC many partition apeared not writeable only show a partition with "image" folder in witch all firmware file stored who write via qfil
Click to expand...
Click to collapse
Hello there!. As far as i know, from what you've said,
The phone still vibrates and shows led, which is a good thing.
About the qfil:
Check whether you are using the latest version of QFIL. Many errors did arise while using the earlier ones.
Make sure you haven't messed up any QFIL configuration settings, and check whether the selected build type is "FLAT".
If you are having trouble with the current firmware files, then download another one for the zuk z1, and check if it works. This is because errors can come from wrong/bad programmer files.
::::: This is all assuming that there are no driver issues & that you know well, how to work with QFIL :::::
Hope this helps....
Hey guys, need some help here. I have M1 pro European version and just kind of bricked it:
-The screen stays black, I think system is booting because I can hear unlock click if I press the power button. Also notification led indicates charging when connected.
-in fastboot mode the screen is black too, but fastboot sees the device, though the name is different than before the brick.
-In recovery all I can see is black screen.
Now, here's how this happened:
-I got the phone, updated firmware to 323
-Unlocked successfuly with unofficial unlock
-Tried installing TWRP to no avail - The process seemed to go through fine, but no TWRP, just stock Asus recovery. Tried multiple times, tried rebooting straight to recovery from fastboot, tried on different computers. Weird thing I noticed was that write time in fastboot during the process was like 0.001s, which led me to believe it thought it was writing TWRP, but really wasn't for some reason.
-Then I decided to flash fastboot firmware using this guide: https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
-It started flashing, but during the process I noticed again that all the write times
were super low like 0.001s, which made me expect the worst, and well, here I am now.
It's the first time I have so many problems with rooting a phone. Any help is greatly appreciated, I hope I can fix this considering it kinda works in fastboot mode.
Thanks in advance and have a great day.
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
Not sure whether this will work (it does in some cases), try full ADB instead of minimal ADB + ASUS drivers installed from the website.
By what name does the fastboot see the device?
Hye, did you solve the problem?
Don't worry, it’s only soft bricked. All you need to do is to flash a stock service rom. Something like: WW_ZB602KL_15.2016.1805.318_20180712 or WW_ZB601KL(ZB602KL)-15.2016.1805.311-20180623. The reason it is "bricked" is because you flashed the incorrect rom for your device, actual model is important, M1 has many variants.
Try flash stock recovery through fastboot, relock ur device, then place whatever version of stock rom into microsd,
And last flash it via stock recovery
Hi sorry but how can i flash it through fastboot? I have same problem...
kothy said:
Hi sorry but how can i flash it through fastboot? I have same problem...
Click to expand...
Click to collapse
Flash stock recovery? Enter fastboot, connect Ur device to PC
Open cmd command in folder where U place the recovery.img file. Then, type "fastboot devices" to make sure Ur device detected
Then type "fastboot flash recovery (filename)"
Done
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
RAMBO29 said:
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
Click to expand...
Click to collapse
Yep, if it shows 'blablabla device' It could be dead screen
Then you can go to next step
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Vico100 said:
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Click to expand...
Click to collapse
i am facing the same issue but cant gent into stock recovery and cant enable usb debugging as well
any solutions.
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Vico100 said:
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Click to expand...
Click to collapse
i did that works but screen is blank or dead after flashing fastboot rom
What is your phone model and what rom did you flash?
tried this it did not work
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
can you please help me... i have ZB601KL model... can do fast boot i do not know what to do next.... im stuck on the black screen... i can hear the phone booting up and starting up but its just black screen blinking... please help
---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------
ASUS_X00TDB is the name of the phone when it boots up
same problem with my device. share if you find any solution.
------------------------------------------------------------------------------
fixed my device following this
i shut down my device by tapping power off. then removed sim card and sd card after screen went black. but when i tried to power on, it doesnt respond.. i tried holding the power button for 10s, it gives me a black screen and vibrates and instantly closes again.. so i cant boot into recovery, i cant boot to fastboot, and its unreadable on pc, it doesnt charge, no bootlogo, nothing. just bricked..
.
i dont know why, but it just bricked by itself.. i've been using mokee 9 date of 1/1/2020 thats the last update i installed, with add on su and everything was working perfectly and even if i reboot multiple times..
bootloader was unlocked so xiaomi centers wont help me..
how is it possible to make it boot again? i mean like wtf even happened? i did nothing.. i didnt flash anything and system was READ ONLY before powering off.. all i did was remove sim and sd cards... even after flashing mokee updates yesterday, it booted normally and idk what's going on..
any help?
EDIT: the phone's hard disk IC was damaged. I went to a tech guy and he changed it but then the motherboard broke entirely after flashing the qcn file for imei. Device out of warranty of course because of the damn bootloader. Thank you xiaomi for the great phone that only lasted one month before dying completely.
attempt 2
in attempt 1 i tried force reboot as mentioned, didnt work
attempt 2 : i tried force reboot while plugged to pc, this showed up
attempt 3
i tried to flash a new firmware, but device unreadable. must be on fastboot mode for mi flasher to be able to read it. im starting to lose hope.. the device is new though it makes me sad
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything, because it didnt actually boot into EDL mode, had to open my device physically and use test points. so attempt 4 failed
does this mean fastboot works?
after attempt 4, it said successful so if fastboot works like that then i can flash stock boot.img or something.. right? which image should i start with
forum
boody shaban said:
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything. so attempt 4 failed
Click to expand...
Click to collapse
this is the forum of the bricked phone similar to mine, except that i didnt try any flash like him it just happened randomly
https://c.mi.com/thread-2334646-1-0.html
attempt 5
attempt 5 failed, i tried flashing whole firmware one by one, i started with vbmeta, then recovery but it failed. idk what to do
notice
i have noticed that it only flashes small img files, if its 100kb or more it will fail. maybe due to device restart because the only way to make it read in fastboot mode is to force restart multiple times until it flashes. what to do now?
attempt 6
so according to this video
https://www.youtube.com/watch?v=yJoIiLE_w3w
he installed a driver (name in attachment) then refreshed on mi flash so his device became readable on mi flasher
i tried that but it didnt work.
final attempt.. out of hope
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
boody shaban said:
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
Click to expand...
Click to collapse
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Reason for brick
cg730620 said:
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Click to expand...
Click to collapse
Yes, I hate tearing up my device so I took it to a professional. He failed to open ADL but he did the 9008. Now he waits some kind of credit. Not sure if for the app to work or for the bootloader to unlock, although it was already unlocked but maybe somehow got locked..
Any way, expected reason for brick is either latest magisk module, or kernel tweaks..
I gave the device to a professional, but he also failed to flash it even with test point. He said he was searching for a file.. I dont remember its name, something like IMOH..
Now I need to know any possible reason that might brick my phone again to avoid it
cg730620
Click to expand...
Click to collapse
cg730620 said:
.
Click to expand...
Click to collapse
The app he used was called ultimate multi tools
test point attempt failed
i did the test point, booted to 9008 mode but still nothing.
i think i know why the phone got bricked by itself, it got ARB stands for AUTOROLLBACK
read more about it here https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
bootloader got automatically locked again.
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
boody shaban said:
i did the test point, booted to 9008 mode but still nothing.
Click to expand...
Click to collapse
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
cg730620 said:
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
Click to expand...
Click to collapse
but im sure i have all drivers installed in fact i used mi flash more than once and it worked perfectly fine, and i swear i didnt try to lock it or anything, what happened is, mokee auto updates installed add on magisk and it was the latest version so i think this might have bricked it. idk..
ok i downloed all the drivers and reinstalled them, same error : "library not registered"