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?
Related
hi guys.
i bricked my nexus 7 ...
tried to manually install kitkat.
i read a how to... erased cache etc etc.
after these steps, i tried to install the image. but it didnt work. i tried to flash the bootloader. didnt work.
after this, i dont know at which step, i lost the usb connection. i cant boot anything. no recovery mode etc.
after switching off my device, it says 'booting failed' ... i only can access to the bootloader at restart it.
using adb devices - no devices found.
who can help me... ?!
sorry for my bad english
come on guys need help
eight.zero said:
hi guys.
i bricked my nexus 7 ...
tried to manually install kitkat.
i read a how to... erased cache etc etc.
after these steps, i tried to install the image. but it didnt work. i tried to flash the bootloader. didnt work.
after this, i dont know at which step, i lost the usb connection. i cant boot anything. no recovery mode etc.
after switching off my device, it says 'booting failed' ... i only can access to the bootloader at restart it.
using adb devices - no devices found.
who can help me... ?!
sorry for my bad english
Click to expand...
Click to collapse
hmm that sounds bad dude, first don't try stuff you aren't sure of !
Second, you are lucky that you can access boot loader; most nexus become paper weight
here are steps to get it back to life.
1 ) download nexus root toolkit 1.80
2 ) select your device and ROM what was running on.
3 ) there are icon buttons first install drivers using first button.(Full driver installation guide etc)
4 ) then go to the button that is flash stock+unroot {make sure to check current status(soft bricked) }
5 ) then if you have a stock room saved, select that or choose auto( it will do all the steps it self )
6 ) it will download and install through boot loader mode
have fun
I had that similar problem, like mentioned before me.. Download thenexus toolkit aand either try to flash stock firmware or you might have to download the original firmware (which is easy to which) and then side load or manually push the image to your tablet
---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------
Anonymous777 said:
I had that similar problem, like mentioned before me.. Download thenexus toolkit aand either try to flash stock firmware or you might have to download the original firmware (which is easy to which) and then side load or manually push the image to your tablet
Click to expand...
Click to collapse
Sorry, that was the poorest grammar ever!
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
ecko no yaro said:
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
Click to expand...
Click to collapse
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Mati0807 said:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Click to expand...
Click to collapse
did you try to go from lollipop to kitkat?
heavy_metal_man said:
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
ecko no yaro said:
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Click to expand...
Click to collapse
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
---------- Post added at 06:20 PM ---------- Previous post was at 06:05 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Right, you need to follow this guide i think. Ensure your read it fully before you attempt anything. Now, the lollipop update apparently changed some partitions so I would flash the bumped twrp from the development section instead of the 2.6.3.2 version recommended. Then once you can boot into recovery flash the rom recommended in this post
heavy_metal_man said:
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
Click to expand...
Click to collapse
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
ecko no yaro said:
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
Click to expand...
Click to collapse
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
heavy_metal_man said:
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
Click to expand...
Click to collapse
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
ecko no yaro said:
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
Click to expand...
Click to collapse
Hmmm. im stumped. I think its a bit of a catch 22 here. What i think has happened is that the rom flash that was done has changed some of the partition layout, but the methods of fixing that issue is either with DD commands from a custom recovery (which you dont have and cannot flash) or with DD commands using ubuntu when the device is auto-mounting all of your partitions. Its worth a look if you have an ubuntu disk around, if not download here, burn to disk or mount it to a bootable usb and see if ubuntu has any luck with it. Either that or try installing any drivers you can on the pc to get download mode working.
there is also this as a last resort but i've never had to do this so i cannot vouch for it :-/ Good luck pal.
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
and install bumped recovery 2.8.5.1, then next with otg cabble flash these http://forum.xda-developers.com/showpost.php?p=59079665&postcount=536.
and now i install cloudyg2 and i feel great xD thank you!
Mati0807 said:
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
dear do you have above mentioned tool bcoz i can not download , this page do not open
Click to expand...
Click to collapse
new link http://www39.zippyshare.com/v/UphAeXOO/file.html
With all files for d802. i used these for my phone!
Only run these tool, and smile
Hi @xda Team,
couldn't find any threads releted to Sharp Z2, which would match to my issue, so that's why I'm trying it in this forum.
I have Sharp Z2 phone (https://www.gsmarena.com/sharp_z2-8410.php).
I tried to root it and to install/flash TWRP recovery on it. Because of realy less information for this phone it was difficult to find proper files.
So I tried with an official version of TWRP.... didn't worked.... after long time, I found on an chineese forum some instructions for flashing the TWRP through ADB/Fastboot.
Bacause I have successfully used this technology already several times on other phones, I was happy to have finaly found something AND forgot to check the skripts
The result is, that after unsuccessfully flashing the bootloader got blocked trough this script (OEM blocked). Now my phone is not booting. I have no access to FASTBOOT and to RECOVERY mode.
I have found an unbrick instruction for LeEco s3 (based on x620) using the SP Flashtool (I have used it successfully for my other phone LeEco S3).
Following this intruction on my Sharp I'm getting following message:
"BROM ERROR: STATUS_SEC_PL_VFV_FAIL......."
It looks to my, that I have not all permissions to flash the phone.
SO still NOT BOOTING, NO ACCESS to FASTBOOT AND TO RECOVERY MODE.
Also on XDA Forum I found this guide for an ASUS Phone (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785)
UPDATE:
SP Flashtool is not able to load the preloader file. Always stops with the same error: BROM ERROR: STATUS_SEC_PL_VFV_FAIL......."
In some forums I've read that flashing with wrong preloader can cause my issue and that in this case there is nothing there to save / recover the phone.
I still hope, that because of the Android OS there is still a chae to unbrick it.
Please HELP!!!
Thanks in advance.
mine is in a similar state but i still have access to the fastboot; i can reboot to bootloader or recovery but only to acccess fastboot. there is no recovery tool left on it and attempt to flash twrp - various versions of those have all been failed attempts. handset is still in the brick state with access to fastboot but no use.
please help to get this working again, given the fastboot is working, can i use any other recovery tool except for twrp to maybe get to having OS flashed?
Hi. On the forum 4pda have firmware under flashtool
can anybody provide correct preloader file for this phone (Sharp Z2 FS8002).?
taulu7 said:
Hi. On the forum 4pda have firmware under flashtool
Click to expand...
Click to collapse
Port Miui Hellas TEAM, my logo and splashlogo
HTML:
https://www.needrom.com/download/twrp-for-sharp-z2/
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
VanDragon said:
can anybody provide correct preloader file for this phone (Sharp Z2 FS8002).?
Click to expand...
Click to collapse
HTML:
https://4pda.ru/forum/index.php?s=&showtopic=870393&view=findpost&p=76931735
Anyone can port EUI/MIUI/Flyme or Nougat (lineage/CrDroid/RR) to Z2?
Both has same chipset Helio X20 (4/32)
LeEco Le2 X62x ROM [4pda.ru]
no changes
taras-fedora-syn said:
Port Miui Hellas TEAM, my logo and splashlogo
HTML:
https://www.needrom.com/download/twrp-for-sharp-z2/
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
HTML:
https://4pda.ru/forum/index.php?s=&showtopic=870393&view=findpost&p=76931735
Click to expand...
Click to collapse
-
-
So i follow every step but after flashing preloader there is only black screen again.
What should i do next?
zeronavigator said:
-
-
So i follow every step but after flashing preloader there is only black screen again.
What should i do next?
Click to expand...
Click to collapse
I don't understand why to flashing preloader
TWRP --- Install ROM or SuperSu.zip
firmware under flashtool
Click on the SP Flash Tool "Download" and connect the switched off phone with the Vol "-" key pressed as on the screen, the tick on the Preloader is not worth it! Release the key a few seconds after filling the 100% red bar. Wait for the end of the firmware and the appearance of a green tick. Disconnect the phone from the PC and try to turn it on
taras-fedora-syn said:
firmware under flashtool
Click on the SP Flash Tool "Download" and connect the switched off phone with the Vol "-" key pressed as on the screen, the tick on the Preloader is not worth it! Release the key a few seconds after filling the 100% red bar. Wait for the end of the firmware and the appearance of a green tick. Disconnect the phone from the PC and try to turn it on
Click to expand...
Click to collapse
So i did with a firmware i found on 4pda forum for sharp z2 using this guide http://4pda.ru/forum/index.php?showtopic=870393&st=100#entry76931735
I managed to flash using vol- with VCOM drivers.
Tried to boot the phone and nothing changed.
Black screen, short vibration on power button but no progress, no fastboot no recovery no nothing.
i also tried to find this firmware TSP-1360-0-00WW-A03-update.zip in case i was flashing wrong files but there is nowhere available for download except baidu server on witch it need an acount with a phone verification.
Still dont understand what i am doing wrong..
Any ideas?
zeronavigator said:
Any ideas?
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=870393&view=findpost&p=77195440
Spoiler - P.S.
If it doesn't work then yo need to flash the full backup,
I don't want to give my because my IMEI are there
So i managed to revive the phone.. but as expected no IMEI no Baseband blah blah blah..
..and of curse i have no backup of it.
Is there a tutorial \ guide on how to fix this problem on my sharp z2 ?
Thank you in advace
help me
can get the original rom from sharp-z2 and send the link to me download
I cannot go to baidu to download it because I am Brazilian and my number does not accept
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"